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
Solana4 articles in running a nodeHardware, sync and the parts that must never face the internet.
- Running a nodeEthereum
Running an Ethereum node
“What does it take to run an Ethereum node myself?”
Hardware quoted from ethereum.org, the JWT secret between the two halves, checkpoint sync, and which of the three port groups must be reachable and which must never be.
- 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 nodeSolana
Running a Solana RPC node
“Is a Solana RPC node the same as a validator?”
No — and sizing one from validator requirements is the mistake that produces a node permanently behind the cluster. Hardware quoted from Anza, why the accounts and ledger need separate devices, and what account indexes cost.
- 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.