Verifiable records and proofs

Create tamper-proof evidence that a document or piece of data is authentic and hasn't been changed since it was recorded on EBSI — and let anyone check it themselves, without having to trust or contact whoever produced it.

Timestamp

The on-chain Timestamp capability is used to anchor the hash of a piece of data on the current block of the EBSI Ledger.

Track and Trace

The on-chain Track and Trace capability binds data to a Track and Trace document and stores the Track and Trace document identifier and its metadata on the EBSI ledger.

Comparison

	Timestamp	Track and Trace
Anchors	One hash, once	A document identifier, plus every lifecycle event appended to it
When to use	Proving data existed at a specific moment	Tracing provenance, versions, and events over time
Guide	Create a Timestamp	Create a Track and Trace Document

Signing and submitting transactions

Both guides write to the EBSI ledger, and every write follows the same three-step pattern:

1. Sign the transaction locally with your legal entity's key.
2. Submit it with the eth_sendRawTransaction JSON-RPC method, which broadcasts it through the Ledger Service and returns a transaction hash.
3. Poll the Ledger Service's eth_getTransactionReceipt method until the receipt is available; transactions take a few seconds to be mined. Check the receipt's status field: 0x1 means success, 0x0 means the transaction failed (the revertReason field explains why).

Read operations (listing or fetching timestamps, records, documents, events, and accesses) are public REST calls: they need neither an access token nor a signature.