API Overview

Verified against: Pinned source and release revisions, Qwertycoin mainnet where applicable, 2026-09-29.

Published release: Core/wallet RPC v2.0.2 (54308d84). Development: a71c0eb2; only get_epose_diagnostics differs in the route map at this baseline.

Qwertycoin exposes separate interfaces:

Interface	Process/path	Encoding	Trust boundary
Daemon path RPC	qwertycoind /method	JSON or portable binary archive	Restricted and unrestricted listeners differ per route
Daemon JSON-RPC	qwertycoind /json_rpc	JSON-RPC 2.0	Route-level restrictions plus handler checks
Wallet RPC	qwertycoin-wallet-rpc /json_rpc	JSON-RPC 2.0	Private, authenticated; holds wallet authority
EPoSE RPC	daemon path/JSON-RPC subset	JSON	Public probe subset vs private operator routes
ZMQ	qwertycoind 8199 example	ZMQ protocol	Not HTTP RPC; keep private unless separately engineered
C++ libraries	linked API	native ABI	Not a stable network contract

The generated RPC route inventory accounts for every registration at both pinned revisions: 107 daemon and 96 wallet registrations on development, versus 105/96 on release. Aliases remain separate rows but share one command schema. Each row links the exact route and request/response definition.

All money amounts are unsigned integer atomic units (10^8 per QWC) unless a schema explicitly says otherwise. Never use binary floating point for amounts.

Start with Wallet RPC Setup, then the Wallet RPC Reference and Integration Examples. Daemon users should distinguish JSON-RPC from path/binary RPC.