Proof ledger: sealed signatures and certificates
See how signatures and records are gathered in batches and anchored in Bitcoin, and issue credentials for past certificates.
Open the Proof ledger
The page counts the Signatures sealed and the Credentials, and lists each batch. A batch is Stamped, waiting for Bitcoin until a Bitcoin block confirms it, then it shows In Bitcoin with the block.
This page needs a free account.
Seal the waiting records
Every day the platform gathers the new records in one batch and stamps it. Press Seal the waiting records now to do it at once. If the page says the signing key is not set up on this server, nothing can be sealed: tell whoever deploys the platform.
Issue credentials for past certificates
Press Issue credentials for past certificates once, so that certificates delivered before the ledger existed also become verifiable credentials.
Publish the public key
Public key (DID document) is the key anyone can use to check a seal without asking NMD. It is published as the identity of the platform.
- A document stays valid on its own page even before Bitcoin confirms the batch. The anchor adds an independent date that nobody, NMD included, can change.