| Name | Type | Description | Notes |
|---|---|---|---|
| code | string | Timestamp verification status code:<br> - VERIFIED: success: the proof receipt is verified<br> The receipt format is valid, the transaction is present in the Bitcoin blockchain and confirmed at least once, the receipt contains a valid Merkle proof linking its `targetHash` property to the transaction's `OP_RETURN` field.<br> The creation time and the number of confirmation of the block containing the transaction is returned in the `timestamp` and `confirmations` properties.<br> Any data whose SHA256 hash matches the proof receipt's `targetHash` is proven to exist at that time and has not been modified since.<br> - TX_NOT_SENT: warning: the transaction has not yet been sent to the blockchain (ie. the data or the signature has not yet been anchored)<br> - TX_NOT_CONFIRMED: warning: the transaction is not yet confirmed by the blockchain (ie. not yet included in a block)<br> - TX_NOT_FOUND: error: the receipt's `anchors` property does not include a valid Bitcoin transaction<br> - INVALID_PROOF: error: the receipt's `proof` property is not a valid Merkle proof<br> - TX_MISMATCH_RECEIPT: error: the receipt's `merkleRoot` property does not match the transaction's `OP_RETURN` field | [optional] |
| text | string | Timestamp verification status text giving more insight about verification errors. | [optional] |
| timestamp | int | Proven timestamp of the data (for a data anchor) or of the signature (for a signature anchor).<br> This is actually the time of the Bitcoin block into which the anchoring process occurred (in milliseconds since Unix epoch). | [optional] |
| confirmations | int | Number of confirmations of the Bitcoin block into which the anchoring process occurred. | [optional] |