Receipts
Receipts give you cryptographic proof of the exact time, accurate to the millisecond, that a transaction occurred.
Receipts & Timestamps
When you upload data to Irys, it is stamped with a millisecond-accurate timestamp before being passed to Arweave where it is stored permanently.
Blockchains rely on timestamps to sequence the order of transactions and blocks. Transaction sequencing plays a critical role in blockchain security as it ensures that all transactions are recorded in the correct order, and that order is never changed.
Receipts provide cryptographic proof of a timestamp. This creates a secure and tamper-proof sequence of all transactions, enabling proof of authenticity, permanence, and provenance.
Ordering & streaming
Ordering and streaming applications process and deliver data in real-time. They're commonly used for messaging, event processing, and data integration. They transfer high data volumes between independent applications while maintaining high performance and scalability. Popular examples include Apache Kafka and RabbitMQ.
Users could use Irys' receipts to:
- Build a category-based event streaming application by using Irys query package
Why use signed receipts?
Cryptographically signed receipts open up new development options for builders. For example:
- Sequential ordering of posts, likes and comments for a decentralized social protocol.
- Sequential ordering of data generated by a group messaging protocol.
- Automatically adjudicating music copyright claims.
- Preserving history, ensuring it's not manipulated over time.
- Preserving scientific research using Irys' pay-once, store-forever model.
Receipt permanence
Upon posting a transaction to Irys, a receipt is immediately returned to the user.
Irys maintains an internal registry of all receipts, which can be queried whenever a receipt is needed. These receipts are stored in a centralized fashion, which may be sufficient for users comfortable with the trust assumptions of centralized services.
Users also have the option to use Irys to store the receipt on Arweave. These receipts inherit Arweave’s permanence, meaning you can verify transaction sequencing at any time, even if Irys is no longer available.
Receipt format
Receipts are a JSON object with the following format:
{
id: '1Txlbl5NgEqUbIkDnnunHC0gFx0n8_Y92zAsoX54kI8',
timestamp: 1676891681110,
version: '1.0.0',
public: '...',
signature: '...',
deadlineHeight: ...,
block: ...,
validatorSignatures: [],
}| Field | Description |
|---|---|
| id | Transaction id (used to download the data) |
| timestamp | Timestamp (UNIX milliseconds) of when the transaction was created |
| version | The version of this JSON file, currently 1.0.0 |
| public | Public key of the bundler node used |
| signature | A signed deep hash of the JSON receipt |
| deadlineHeight | The block number by which the transaction must be finalized on Arweave |
| block | Deprecated |
| validatorSignatures | Deprecated |
Verifying receipts
You may need to verify a receipt at some point after it was issued. For example, if your application’s security depends on the order of transactions, you can then verify every receipt to ensure its order has not been tampered with.
The receipt contains a signature field, which is generated by creating a deep hash of information from the receipt, including transaction ID and timestamp. It is then signed it by Irys.
Using the Irys SDK you can verify the signature using the using the same values from the receipt along with the supplied public key.
Timestamp generation
Irys records the precise time of each transaction with a UNIX timestamp in milliseconds. This timestamp is generated by the node that first receives and verifies the transaction.