Guides
Running the infrastructure, not just calling it
11 articles on getting, choosing, running, scaling and watching a node — general where the problem is general, and per chain where it is not. Written for the decisions that come before picking a provider from the rankings, and the ones that come after deciding not to.
Ethereum
BSC
Solana7 articles for BSC · page 1 of 2
- Choosing· All three chains
Getting a dedicated node
“The free endpoint is not enough any more. What now?”
What a public endpoint actually gives you, what changes when you pay for a dedicated one, and how to tell which of the two your application needs — using the limits providers publish and the behaviour measured here.
- Clients· All three chains
Why the client mix matters
“Does it matter which client everybody else is running?”
What a supermajority client bug costs at 33% and at 66%, why the published diversity figures disagree with each other by more than they agree, and what any of it changes for an application rather than a validator.
- ClientsBSC
BNB Smart Chain clients
“What can I actually run on BNB Smart Chain?”
Two supported clients since Erigon was retired, why both answer to their parents' names, and what the version number in a BSC banner does and does not mean.
- Running a nodeBSC
Running a BNB Smart Chain node
“Why does a BSC node need four times the machine?”
Hardware quoted from BNB Chain's own best practices, why snapshots are effectively mandatory, how much memory to hand the cache, and the method the public endpoints will not serve you.
- Running a node· All three chains
Exposing RPC without giving it away
“Can I just open the port?”
No. An open JSON-RPC port is an unauthenticated public interface to your node with no rate limit and no accounting — what to bind, what to put in front of it, and which namespaces never belong on a listener anybody else can reach.
- Scale· All three chains
Serving RPC at scale
“One node works. How do I serve real traffic?”
Load balancing that understands RPC, routing methods to the node that can answer them, what is safe to cache and what is not, and why failover between two providers is a different exercise from failover between two of your own nodes.