Shared node is a remote server that multiple users or applications access simultaneously to interact with a blockchain. They handle requests like querying data or sending transactions. While convenient and cost-effective, shared nodes can experience slower response times and potential security risks due to shared resources among users

Shared vs dedicated nodes: What’s the difference?

Shared RPC nodes offer basic security but have vulnerabilities. Since multiple users access the same node, they can be prone to data leaks, slower performance, and potential exposure to attacks targeting shared infrastructure. For sensitive operations, dedicated or self-hosted nodes are generally more secure, providing better control and isolation from other users.

How to take shared crypto nodes?

To use shared RPC nodes by GetBlock, sign up on our platform, select your desired blockchain, and generate an API key. Then, integrate the provided RPC URL into your application's code, using the API key for authentication. This allows you to send requests, such as querying blockchain data or submitting transactions, via GetBlock's infrastructure.

GetBlock

RPC Service

Shared

Shared Nodes

Shared RPC nodes are basic-level offerings of GetBlock: they connect dApps to blockchains together with other users. While sending requests, you share the infrastructure with someone. Shared nodes are good for early-stage dApps and testing before scaling. GetBlock supports shared nodes of 100+ blockchains; you can get your shared node RPC endpoint in your account dashboard.

Supported protocols

FAQ

Frequently Asked Questions

What is shared node?
Shared node is a remote server that multiple users or applications access simultaneously to interact with a blockchain. They handle requests like querying data or sending transactions. While convenient and cost-effective, shared nodes can experience slower response times and potential security risks due to shared resources among users
Shared vs dedicated nodes: What’s the difference?
Shared RPC nodes offer basic security but have vulnerabilities. Since multiple users access the same node, they can be prone to data leaks, slower performance, and potential exposure to attacks targeting shared infrastructure. For sensitive operations, dedicated or self-hosted nodes are generally more secure, providing better control and isolation from other users.
How to take shared crypto nodes?
To use shared RPC nodes by GetBlock, sign up on our platform, select your desired blockchain, and generate an API key. Then, integrate the provided RPC URL into your application's code, using the API key for authentication. This allows you to send requests, such as querying blockchain data or submitting transactions, via GetBlock's infrastructure.

Web3 RPC APIs

Crypto Nodes List: Various Blockchains, Various Use Cases

Fast and cost-efficient RPC APIs

GetBlock maintains one of the largest toolkits of crypto nodes in Web3. We run blockchain nodes so our clients don’t have to. As a leading RPC APIs provider, we offer 99,99% uptime and competitive speed for all our services.

Blockchain Nodes: List of Advantages

Working with a Web3 RPC provider is more resource-efficient than running self-hosted ones. Instead of purchasing servers, customizing and maintaining them, teams can focus on development saving up to 70% in time and efforts.