EPoSE RPC Reference

EPoSE RPC reference

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

Release: all rows except diagnostics are in v2.0.2.
Development: get_epose_diagnostics requires a71c0eb2 or a later build containing it.

Method	Transport	Restricted listener	Purpose
get_epose_info	path + JSON-RPC	yes	Epoch, canonical population/qualification and local producer flags
get_epose_diagnostics	path + JSON-RPC	no	Authenticated operator diagnostics; development only at baseline
get_service_nodes	path + JSON-RPC	yes	Bounded canonical descriptor list
get_service_node_status	path + JSON-RPC	yes	One public service-key lookup
get_service_node_registration_payload	path + JSON-RPC	yes	Deliberate retired-v1 status; not enrollment
get_epose_epoch	path + JSON-RPC	yes	Epoch boundaries and counts
get_epose_service_endpoint_v2	path	yes	Signed local endpoint descriptor
epose_service_challenge_v2	path	yes	Context-bound canonical-object response
get_service_rewards	path + JSON-RPC	yes	Height preview using prior closed set
get_epose_block_reward	path + JSON-RPC	yes	Verify/map one canonical historical block
submit_epose_envelope	path	no	Admit/relay one envelope; private operator path

Path calls POST JSON to /<method> without a JSON-RPC wrapper. JSON-RPC calls use /json_rpc. Exact fields and linked schemas are in RPC Inventory.

get_service_nodes is bounded and reports total/returned counts. Endpoint/challenge HTTP success is not consensus evidence. submit_epose_envelope local acceptance is not canonical inclusion. Reward attribution must use the verified mapping, never output position.

Development diagnostics additionally require configured RPC login and return no data otherwise; see Monitoring and Diagnostics.