Network Node API
This section describes the Network Node API, specifically the /v1/epochs/{epoch_id}/participants endpoint. This endpoint is used to retrieve:
- Merkle proofs
- Host data
- Validator signatures
Usage
Current Epoch Data
curl -X GET http://<your_api_node_url:public_port>/v1/epochs/current/participants
Specific Epoch Data
curl -X GET http://<your_api_node_url:public_port>/v1/epochs/<epoch_id>/participants
Example response breakdown
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 | |
active_participants
participants: List of active participants, including:
index: gonka addressvalidator_key: Public key (Base64)weight: Reward weight for this epochcap_weight: Trust weight for governance, BLS, and PoC validation. Present whencap_weight_appliedis true (epochs formed by v0.2.16 or later). On earlier epochs, voting power followsweightinference_url: Service endpointmodels: List of supported modelsseed: Signature seed with metadata
addresses: List of participant addresses (in uppercase hex format)
active_participants_bytes: Raw byte array (hex-encoded) that encodes the Hosts' data — suitable for Merkle proof verification or state synchronization.
proof_ops: List of ICS23-compatible proof operations for verification
validators: Validator set at the time of the epoch:
address: Validator addresspub_key: Public key (Base64)voting_power: Current voting powerproposer_priority: Consensus proposer priority
block: List of blocks surrounding the epoch event
- Includes full block header metadata, proposer address, commit signatures, etc.
- Useful for verifying the inclusion and commitment of Host data
Need help? Find answers on FAQ page, or join Discord server for assistance with general inquiries, technical issues, or security concerns.