oldBlockHeightand the ledger's current height. Trustees use this endpoint to get the latest relevant blocks, extract the data requests in them, and respond to the data requests accordingly.
oldBlockHeightis present in query parameter
oldBlockHeightis a non-negative number
oldBlockHeightis an integer
oldBlockHeightis valid - no larger than the current block height of the ledger
Encryption. After detecting a new data request, a trustee should use this endpoint to get its encrypted share from the corresponding
Encryption, decrypt it with its decryption key, then post the result with postTrusteeResponse.
TrusteeResponseis consistent with the PAD instance to which the API key is pointing
tokenin path and
signatureis consistent with the payload
*The ledger view of the trustee includes the ID/name of the PAD instance, the height of the ledger, the current block hash of the ledger and a timestamp when the trustee construct the attestation.
padNamein attestation is consistent with the PAD instance to which the API key is pointing
currentHashis the block hash at
previousHashfield in the schema refers to the hash of the previous block header, instead of the entire previous block. Thus, if the block data is irrelevant (for example not containing any data request when one is asking for them), it can be skipped.
previousHashfields are empty.
dataHashis computed with the same block's data. Refer to code samples on how to compute hash of a block header.
encryption. The decryptor posts it on the ledger at data request stage.
.) or dashes (
-). It must start with a lowercase letter.