Blockchain RPC API

This page documents the RPC interface family for IXO Protocol. It does not document application service APIs such as Impact Hub Registry, IXO Blocksync, or IXO Matrix.

Overview

• Use this interface for protocol-level operations against chain nodes.
• Prefer this when you need direct interaction with IXO Protocol modules.
• For indexed or application-service workflows, use service APIs in this section instead.

Protocol boundary

• 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.

• Check /reference/authentication-matrix for active auth requirements.
• Check /reference/networks-and-endpoints for network-specific RPC endpoints.

Example message shapes

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;
}

Troubleshooting

• connection refused / TLS errors — Wrong host, port, or TLS termination. Confirm the literal in Networks and endpoints and your operator’s current RPC URL.
• invalid JSON-RPC / parse errors — Request body not valid JSON-RPC 2.0; include jsonrpc, id, method, and params as required by the method.
• Transaction broadcast failures — Inspect code, codespace, and rawLog. Common causes: insufficient fees, wrong chain-id, sequence mismatch, or missing signer permissions. See Error handling and Claims management.
• Auth on RPC — Many nodes allow unauthenticated read; writes require a valid signed tx, not an API key. Confirm policy in Authentication matrix.

Related references