Introducing GYNN — a magic RPC provider that takes your ball-ache with node management out 🧞
The most recent version of the internet, known as Web3, has been developing at an entirely unexpected tempo. It is obvious that blockchain technology has already had a wide range of apps and it is here to stay.
The biggest use case of blockchain technology so far is cryptocurrencies. However, blockchain does not end there — exchanges, finance, games, marketplaces, security, social, and wallets are the most widely developed ones.
As blockchain is one of the main components of dApp, here is where the problem hides.
To Build Any Dapp You Have to Deal With the Nodes. It’s Obvious.
After selecting the blockchain you want to build on, your next step is gaining access to its node. Nodes are the main instrument for communication with blockchain to conduct operations like checking a balance, initiating a transaction, or interacting with a smart contract.
But they are tricky and have their own lives. They can downtime, lag, and even stop. In most cases, nobody knows why it happens.
Whether you are an experienced coder in creating blockchain-related programs or a novice Web3 developer, you can’t get away from nodes. Moreover, you will deal with different types of nodes — RPC nodes, Archival nodes, and Archival nodes with an indexer. And there you two ways for you — manage your own node or use an outsourced one.
Running in-house nodes
The first strategy may sound more attractive in terms of security and reliability. However, it has several weak points:
- High-level expertise. For the setup and synchronization to go well, an expert touch is required. Due to a lack of knowledge, an error may occur, leading to blocks re-synchronize from the beginning.
- Time-consuming process. A node requires a lot of time to configure. After you succeed in it, you should always keep an eye on nodes maintenance. Chosen blockchain updates, nodes shutdown, and 100% availability fall on your shoulders.
- Heavy maintenance costs. Let’s have a look at NEAR nodes as an example. It can cost you $1000/month on average for an AWS server and from $4–5k/month to equip hardware at home. Don’t forget about archival nodes that need additional RAM, CPU, and disk space. Add to your costs approximately 1500$ to 7000$ depending on using the AWS server or home-made equipment.
- Scaling. A single node is enough for personal projects, but if you’re a company striving to keep up with customer requests, things might become problematic. Even if you built up two nodes with a load balancer, you’d be confronted by consistency problems. Furthermore, if you think to connect to numerous blockchains, you’d have to operate nodes for each one.
An undesirable combo.
Good news: there is always option two to make things simpler 👇
Connect Node Provider
Without the need to manage a node manually, RPC provider delivers easy-to-achieve access to blockchain data. It lets you avoid setting up your own in-house node and all the hassle and expenses that go with it.
Node provider offers an endpoint that you can use to communicate with constantly accessible, completely synchronized, and up-to-date nodes. You get all the benefits of using the blockchain without experiencing any problems related to engineering, maintenance, or management.
A right-chosen RPC provider can assist you in such cases as:
- You’re about to launch a new Web3 project;
- You’re searching for support in managing projects and development teams;
- You need of a partner to help you establish a scalable platform for your dApp.
Time for GYNN to come to hand
We are a part of INC4 — a development company that built more than 60 blockchain projects in the last 10 years. That’s why we have a deep understanding of node management pain.
We were looking for a provider that takes our ball-ache out and will keep pace with the official blockchain nodes or work even quicker. Additionally, we were surprised that many RPC providers are deafeningly quiet about the fact that they only operate with full nodes.
🪄 As a result, we found nothing better than to build an RPC provider on our own.
How does GYNN stack up against its competitors?
- We simplified the process for getting an endpoint — authorization can be achieved quickly and easily through a Google or GitHub account. Then our no-brainer interface will not create additional obstacles for setup.
- GYNN is a provider capable of ensuring consistent performance not just for full nodes but also for archive ones.
- Our software responds quickly to errors, manages all resources, and automatically adds extra nodes if the load is 80% or higher, ensuring the best possible experience.
- Using internal statistics, developers may verify all request parameters and receive detailed information.
- We have functionality that can limit endpoint requests to a specific domain. Even user’s token is taken over, hackers will not be able to use it on another domain.
- We do not intend to support a large number of blockchains. We prioritize the quality of our services and the promises we make.
We chose NEAR — a steadily upcoming and fast blockchain — as the first protocol to connect as we can maintain it backward and forward to provide reliable core infrastructure. We have plans to extend chains supported as we will be ready for that.
