Settla · Blockchain Infrastructure
RPC Node and Blockchain Endpoints
An RPC node handles application requests to a blockchain: blocks, balances, contract state and signed transaction broadcast. A blockchain endpoint is the URL used to call that node.
Settla provides shared and private endpoints for supported networks. Select the model based on methods, history depth, peak load and security requirements.
What is an RPC node?
RPC means remote procedure call. For example, an EVM client can call eth_getBalance, eth_call or eth_sendRawTransaction. Private keys should normally remain in a wallet or protected signer.
Public RPC vs private RPC
| Criterion | Public/shared RPC | Private RPC |
|---|---|---|
| Resources | Shared pool | Agreed project capacity |
| Limits | Plan defaults | Workload-specific |
| Configuration | Standard | Custom where supported |
| Cost | Lower entry cost | Higher dedicated cost |
Latency, rate limits and uptime
Measure p95/p99, error rate, head lag and heavy-method performance rather than relying on averages. Production clients need timeouts, bounded backoff and protection from duplicate transaction submission.
Availability is governed by published plan terms or a contract; no endpoint should be treated as infallible.
Where RPC nodes are used
- Wallet balances and transaction broadcast.
- Exchange deposits, confirmations and withdrawals.
- DeFi contract reads, logs and transactions.
- Explorer indexing and blockchain analytics.
- Background jobs and real-time subscriptions.
When to buy an RPC node or switch to private RPC
Measure traffic and compile a method matrix first. Clarify whether archive, tracing, debug API, WebSocket or gRPC is needed. Compare the cost of the required request profile and operational conditions, not an abstract endpoint price.
A standard blockchain endpoint is enough to start. If production load hits limits or requires isolation, buying an RPC node in a private configuration is possible without changing business logic, provided the API remains compatible.
Blockchain RPC and blockchain endpoints for wallets, exchanges and DeFi
Blockchain RPC is the technical integration layer for any product connecting to a public network. Wallets use RPC endpoints to fetch balances, estimate fees and broadcast signed transactions. Exchanges build deposit, confirmation and withdrawal logic on blockchain endpoints. DeFi protocols call smart contracts via eth_call and monitor events through subscriptions.
A private RPC node lets each application component use a dedicated request pool: user reads, background indexers and critical transaction broadcast do not compete for a shared quota. This reduces the risk of service degradation during peak periods.
RPC node FAQ
Is an RPC node a separate blockchain?
No. It is a node in an existing network with a programmatic interface.
How is an endpoint different from an API?
An endpoint is a concrete network address; an API defines methods and rules.
Why use private RPC?
For allocated capacity, agreed limits, access controls or special methods.
Can RPC broadcast transactions?
Yes, when supported; applications usually submit an already signed transaction.
Does every project need archive RPC?
No. Archive access is for specific historical-state queries.
