GYNN: magic RPC provider
The developer platform that takes the ball-ache with node management out.
GYNN is remote procedure calls (RPC) provider that delivers an easy way to access blockchain data without the hassle of manually managing a node. It eliminates the need for customers to set up and maintain their own in-house node, saving them time and money.
Build an unrivalled RPC provider that will be faster than existing solutions on the market and will support both full and archive nodes.
Provide superior flexibility through automatic nodes’ upscaling and downscaling.
Ensure monitoring of the platform and existing node providers on NEAR, BSC, and Ethereum networks.
Provide product development from scratch involving marketing support and migrating client’s existing projects to the created RPC provider.
Tech stack we used
After a kick-off meeting where the client shared his needs and ideas, we started a discovery phase. Competitor analysis, deep market research, and defined product-market fit before product development helped us understand end users’ requirements and create a detailed roadmap with required milestones. Also, we needed to track existing providers’ performance, so we quickly built a tool for monitoring crucial metrics.
High-level architecture design
Considering that the foremost part of the project depended on robust infrastructure, we started from the main scheme creation. The architecture design gave us a clear understanding of the required team members, appropriate tech stack, third-party integrations, and needed hardware for accurate platform functioning.
Nodes set up and infrastructure testing
As the development process started, we set up NEAR, Ethereum, and BSC nodes. NEAR protocol was chosen because our client has already been integrated into the NEAR community. Ethereum and Binance Smart Chain were great options as the most used and fast-growing blockchains on the Web3 market.
The next stop was load testing for each type of nodes, measuring latency and response time for different requests according to the complexity of its processing.
Load balancer & API
As the project means to be high-cost, the client needed to optimize infrastructure spending. That’s why we implemented a load balancer whose task was to respond quickly to errors, automatically add extra nodes if the load is 80%, and save costs by automatically collapsing nodes if they are loaded by less than 50 percent for an hour.
Moreover, the product is planned to work on a subscription model, so it was necessary to add API. It helps to track the quantity and types of nodes a specific customer uses.
Our front-end developer created a simple, no-brainer interface to simplify getting endpoint to a few clicks and easily manage nodes as well as monitor statistics.
Beta testing and further support
We were responsible for holding beta testing for GYNN from users’ attraction via marketing channels to gathering feedback. After the testing launch, we collected and added new features to the backlog for future product adjustments to meet the target audience’s needs.
More of what we did
We simplified the process for getting an endpoint — authorization can be achieved quickly and easily through a Google or GitHub account.
We implemented internal statistics, which developers may use to verify all request parameters and receive detailed information.
We added functionality that can limit endpoint requests to a specific domain. Even if a user’s token is taken over, hackers cannot use it on another domain.
Average performance increase in users’ projects
Developers in the beta stage