Introduction to Kadena RPCs and RPC Nodes

Kadena’s RPCs (Remote Procedure Calls) enable interaction with the Chainweb blockchain network by providing key API endpoints for both peer-to-peer (P2P) communication and service-based access.

Peer-to-Peer API

The P2P API is designed for communication between Chainweb nodes to facilitate blockchain consensus. It includes endpoints for:

• Cut endpoints: Distribute the current state of the network.
• Payload endpoints: Access raw block payload data.
• Mempool endpoints: Manage pending transactions.
• Peer endpoints: Handle peer connections.
• Config endpoint: Retrieve node configuration details.

Base URL Structure

P2P API requests are sent to nodes using the base URL format:

• Mainnet: <hostname>/chainweb/0.0/mainnet01
• Testnet: <hostname>/chainweb/0.0/testnet04
• Local Development: localhost:8080/chainweb/0.0/development

While P2P endpoints are efficient for node communication, most users should use service API endpoints for interacting with the blockchain.

Kadena RPC Node Providers

<aside> <img src="https://pbs.twimg.com/profile_images/1542498890292662272/Z3ZR_Ps8_400x400.jpg" alt="https://pbs.twimg.com/profile_images/1542498890292662272/Z3ZR_Ps8_400x400.jpg" width="40px" /> Tatum

</aside>

<aside> <img src="https://pbs.twimg.com/profile_images/1879130038651748352/-8-Zx7-g_400x400.jpg" alt="https://pbs.twimg.com/profile_images/1879130038651748352/-8-Zx7-g_400x400.jpg" width="40px" /> Unmarshal

</aside>