Skip to main content

Kyve RPC Scanner

Discover and filter public RPC nodes by features, location, and provider. Find the perfect endpoint for your application.

About RPC Nodes​

RPC (Remote Procedure Call) nodes are essential infrastructure components that allow applications and users to interact with blockchain networks. Different types of nodes serve different purposes:

Node Types​

Validator Nodes: These nodes participate in the consensus mechanism and validate transactions. Note that it's not recommended for validators to open RPC ports publicly for security reasons.

Archival Nodes: Store the complete blockchain history from genesis, making them ideal for applications that need historical data.

Transaction Indexing: Nodes with transaction indexing enabled allow you to query transaction history and search for specific transactions.

WebSocket Support: Enables real-time updates and streaming of blockchain events.

Choosing the Right Node​

When selecting an RPC endpoint, consider:

  • Purpose: Use archival nodes for historical queries
  • Geography: Choose nodes closer to you for better latency
  • Provider: Consider reliability and reputation of the infrastructure provider
  • Features: Ensure the node supports the specific features you need

Usage Examples​

# Check node status
curl -X POST https://your-rpc-endpoint.com \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"status","params":{}}'

# Get latest block
curl -X POST https://your-rpc-endpoint.com \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"block","params":{"height":null}}'

# Get specific block by height
curl -X POST https://your-rpc-endpoint.com \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"block","params":{"height":"12345"}}'

Integration Tips​

Most endpoints accept standard JSON-RPC calls. Always test endpoints before using them in production and consider implementing fallback mechanisms for high-availability applications.

For WebSocket endpoints, you can subscribe to real-time events:

const ws = new WebSocket('wss://your-websocket-endpoint.com/websocket');
ws.send(JSON.stringify({
  jsonrpc: '2.0',
  method: 'subscribe',
  id: 1,
  params: ["tm.event='NewBlock'"]
}));