Developer RPC

The developer RPC surface should explain how to create accounts, build transaction envelopes, submit signed transactions, inspect receipts, and query state. The wiki should document stable localnet and devnet behavior before describing public explorer guarantees.

First surfaces

• Submit a signed transaction envelope.
• Query transaction receipt and execution status.
• Read latest block metadata and checkpoints.
• Inspect validator set and protocol parameters.
• Fetch proofs only when the corresponding state and block proof rules are implemented.
• Inspect economics state through read-only operator endpoints.

Economics views

Economics v1 exposes committed state for operators and indexers:

GET /v0/economics/summary
GET /v0/economics/treasury
GET /v0/economics/treasury/spend/{spend_id_hex}
GET /v0/economics/validator/{validator_id_hex}
GET /v0/economics/validator/{validator_id_hex}/bond/{account_id_hex}
GET /v0/economics/unbonding/{completion_epoch}
GET /v0/economics/service-chain/{service_chain_id_hex}/bond
GET /v0/economics/service-chain/{service_chain_id_hex}/usage/{epoch}

These endpoints read canonical state rows or hot indexes that mirror canonical state. They do not accept peer-provided summaries, and they do not scan the full state database for missing indexes.

SDK relationship

The TypeScript SDK should own typed builders, canonical encoding helpers, and client wrappers. Wiki pages should link to SDK examples instead of duplicating large code samples once the examples stabilize.