Prototype docs. APIs may change while SDKs and verifier libraries harden.
Payloads + proofs
Each attestation commits to a merkleized key/value payload.
That lets a roll prove:
- which payload value an attestation endorsed,
- that the value is part of the signed attestation commitment, and
- that enough active stake endorsed the same outcome.
Data model
Conceptually:
- key: 32-byte domain hash,
- value: application-defined bytes,
- root: commitment included in the attestation body hash.
Inclusion proofs
A roll carries inclusion proof material for the payload entries it counts. During verification, the consumer checks that each proof reconstructs the payload root committed by the corresponding attestation.
Application payloads
Application payloads remain application-defined.
Sync
Payload values can be synced independently from attestation metadata. This keeps relay efficient when peers already have some leaves and only need the missing pieces.