EthersJS (Ethers.io) adds Pocket Network as a default infrastructure API
This means that many of the Ethereum dapps using EthersJS can interface with the Ethereum network through Pocket’s decentralized infrastructure, mitigating the risk of trusting centralized infras. DApp developers are increasingly worried about relying on centralized services for their infrastructure, especially after Infura went down on November 11th. Pocket can now provide EthersJS users with infrastructure that is decentralized, more reliable, and cost-effective. Some of the benefits of using Pocket provides are:
- Unparalleled redundancy and censorship-resistance due to a diversity of independently run full nodes from all over the world.
- Cost-effective at any scale — Because Pocket business’ model is not rent-seeking, it uses its economies of scale to lower the costs of infrastructure and pass the value directly to node operators, without sacrificing security.
- Emergent privacy through randomness — Unlike centralized infrastructures that log application metadata, Pocket pairs applications with 5 random nodes in the network every hour.
- Multi-chain interface — whether it’s Ethereum Testnets or Ethereum Mainnet(Archival and Full Nodes) developers can easily toggle between the Blockchain networks they need to use at any given time through a single interface.
Pocket has subsidized up to 10M requests per day by staking ~250k POKT on behalf of ethereum application developers using EthersJS.
DApp developers already utilizing the EthersJS SDK simply need to upgrade their dependencies to leverage Pocket Network. EthersJS automatically load-balances its requests across all default network providers’ free tiers, which includes Pocket. This ensures EthersJS apps will always be able to interface with Ethereum, even if centralized infrastructures go offline.
By including Pocket Network as a default network provider, EthersJS adds an extra layer of load-balancing and privacy. By default, the Pocket Protocol will assign applications random 5 nodes per session to ensure the application has a high level of redundancy.
Through the Pocket Gateway’s internal load-balancer, Pocket is able to map additional Application Authentication Tokens (AATs) to a single RPC endpoint. For EthersJS, Pocket has mapped 5 AATs to its endpoint so it will get served through multiple sessions, in this case, 5 sessions, each with 5 nodes. This distributes work more evenly and ensures a better quality of service, especially for high-traffic clients such as EthersJS.
In other words, developers using EthersJS would get served by 25 nodes per hour through the Pocket gateway, meaning every individual call from an EthersJS-powered application will receive the rational majority from 25 nodes. This level of redundancy is possible due to the 1,500+ nodes serving applications on the Pocket Network.
When the time comes to upgrade from free-tier infra offerings, then keep Pocket in mind. Pocket Network is looking for value-aligned projects to grow with. For icing on the cake, Pocket’s offering value-aligned projects 1M requests daily requests for free to get started. As long as developers continue to use it, they’ll never lose it.
The Pocket team would love to nerd out more with decentralists about all things infra, sustainable decentralization, node-economics, and DAO’s.
Pocket builds community and talks shop in our discord.