Returns a stream of proofs committed to the node's ledger.
NOTE: This endpoint may return different results on different nodes:
Proofs during an epoch can also be garbage collected by the node after the fact. Therefore proofs may disappear from this stream.
Some proofs (such as during genesis and protocol update enactment) are created on a node and don't include signatures.
This stream accepts four different options in the request:
The end-of-epoch proofs can be used to "trustlessly" verify the validator set for a given epoch. By tracking the fact that validators for epoch N sign the next validator set for epoch N + 1, this chain of proofs can be used to provide proof of the current validator set from a hardcoded start.
When a validator set is known for a given epoch, this can be used to verify the various transaction hash trees in the epoch, and to prove other data.
NOTE: This endpoint was built after agreeing the new Radix convention for paged APIs. Its models therefore follow the new convention, rather than attempting to align with existing loose Core API conventions.
The logical name of the network
"{{network}}"
If not provided, defaults to "Any".
If specified, the maximum number of proofs that will be returned.
A continuation token is returned if and only if there are further non-empty pages of items currently available. The token can be provided in a following request to fetch the next page of results. The filter and sort should not be changed when re-using the continuation token.
Stream proofs response
A page of ledger proofs stored by this node.
A continuation token is returned if and only if there are further non-empty pages of items currently available. The token can be provided in a following request to fetch the next page of results. The filter and sort should not be changed when re-using the continuation token.