Bundle | Bundlr | Data Provenance | Deep Hash | Gateways | Proof Of Provenance | Provenance Chain | Transaction | Transaction Receipt | Validator
The history of data. It can describe where data came from, how it was created, and who has handled it. Data provenance provides transparency into the lifecycle of data and is critical for building trust in the data.
Proof Of Provenance
The issuing of cryptographically signed receipts, including a timestamp accurate to the millisecond, that provide irrefutable proof of data provenance.
The chain of custody or the history and evolution of data.
A set of Bundlr transactions joined into a single Arweave transaction.
A bundler is a node on Bundlr that receives Bundlr transactions, handles payment channels and produces bundles.
A hash algorithm which takes a nested list of values as input and produces a 384 bit hash, where a change of any value or the structure will affect the hash.
Gateways are nodes that listen to both bundlers and the Arweave L1 with the purpose of aggregating and indexing transactions. This allows you to retrieve and lookup Bundlr transactions from clusters of bundlers without maintaining your own index.
A single item sent to a specific address, usually contains a data payload.
A financial proof that a Bundlr transaction gets on to Arweave by an expected block. The transaction receipt format is.
|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|
|validatorSignatures||Reserved for future use once we're decentralized|
|verify||An async function called to verify the receipt is valid|
A node on the network which aggregates transactions within a block period and validates that each item has reached the chain.