The Blockchain RPC API is the node-level interface to the IXO Protocol. Use it when your code needs to submit transactions or query chain state directly on a node, and talk to the IXO Protocol modules without a service in between.
This page covers the scope of the interface, how to reach it, the shape of two protocol messages, and the errors you are likely to meet. It does not document service APIs such as the Impact Hub Registry, IXO Blocksync or IXO Matrix. For indexed or application-service workflows, use the service APIs instead.
Scope
| In scope | Chain state queries and transaction submission patterns |
| Out of scope | Service-specific business endpoints and off-chain workflow APIs |
Authentication and endpoints
Authentication depends on node and deployment policy.
| What you need | Where to find it |
|---|---|
| Authentication requirements | Authentication matrix (/reference/authentication-matrix) |
| RPC endpoint for each network | Networks and endpoints (/reference/networks-and-endpoints) |
Build and test against testnet or devnet first.
Example message shapes
Illustrative example. These show the shape of two IXO Protocol messages, not their full definitions.
message MsgCreateEntity {
string creator = 1;
string entity_type = 2;
string entity_status = 3;
}message MsgSubmitClaim {
string creator = 1;
string collection_id = 2;
string claim_id = 3;
}The Claims module also has messages to dispute a claim and to decide a dispute. They are documented in Claim disputes.
Troubleshooting
| Problem | Cause and fix |
|---|---|
connection refused or TLS errors | Wrong host, port or TLS termination. Confirm the literal in Networks and endpoints and your operator's RPC URL. |
invalid JSON-RPC or parse errors | The request body is not valid JSON-RPC 2.0. Include jsonrpc, id, method and params as the method requires. |
| Transaction broadcast failures | Inspect code, codespace and rawLog. Common causes are insufficient fees, wrong chain-id, a sequence mismatch, or missing signer permissions. See Errors and Claims management. |
| Authentication on RPC | Many nodes allow unauthenticated reads. Writes require a valid signed tx, not an API key. Confirm the policy in the Authentication matrix. |