⚠️ NOTICE: Deployment Testing in Progress We have recently deployed a major platform update and are currently performing post-deployment testing and validation. Please do not use this website or submit any transactions until testing is complete. Some features may be unavailable or behave unexpectedly. Thank you for your patience as we work to ensure everything is functioning correctly.
Help and support
Glossary
The words Proof uses, explained simply.
- Batch
- Several proofs saved to the chain in one transaction. Only their Merkle root goes on chain, and each proof keeps the short Merkle proof that ties it to that root.
- Block explorer
- A website that shows what is on a blockchain: transactions, blocks and addresses.
- Confirmation
- Each block added to the chain after the block that holds a transaction counts as one more confirmation. A fee payment counts at one confirmation; a stamp counts as permanent once its anchor transaction has the number of confirmations the site requires (six by default).
- Digi-ID
- A way to sign in with a DigiByte wallet instead of an email and password. You scan a code, and your wallet signs a one-time message with one of its addresses to prove it controls that address. Nothing is sent and no coins move. One Digi-ID account signs you in to every DigiStamp product.
- DigiByte (DGB)
- A public blockchain run by many computers around the world, and its currency, DGB. Proof writes fingerprints to it and charges its stamp fee in DGB.
- Draft and published
- A new proof is a draft: only you can see it. Publishing it gives it a public certificate page that anyone with the link can open. Only a published proof can be stamped.
- Fee address
- The DigiByte address the stamp fee is sent to. It is shown, with the amount, on your proof's page. It is not your signing address.
- Fingerprint (hash)
- A 64-character code worked out from the exact bytes of your text or file. The same content always gives the same fingerprint, and changing a single character gives a completely different one. You cannot rebuild the content from it.
- Level 1, 2 and 3
- How far a proof has gone. Level 1, Recorded: the fingerprint was saved with a date and time. Level 2, Signed: a DigiByte address signed it. Level 3, Stamped: its fingerprint is in a confirmed DigiByte transaction. Each level includes the ones before it.
- Merkle proof (inclusion path)
- The short list of other fingerprints needed to rebuild a batch's Merkle root from one proof's fingerprint. It is on the certificate and in the proof's data download, so anyone can show the proof is in the batch.
- Merkle root
- A single fingerprint built from the fingerprints of every proof in a batch, combined in pairs until one is left. If any proof in the batch were different, the root would be different.
- OP_RETURN
- A part of a DigiByte transaction that carries a small amount of data and no coins. Proof puts its marker and the batch's Merkle root there.
- Proof
- A record of a fingerprint of some text or a file, with the date and time it was made. Once published it has its own public certificate page and link. A proof can be signed with a DigiByte wallet and saved to the DigiByte blockchain.
- Revoked
- A proof its owner has taken down. Its certificate, badge, QR code and downloads stop working for everyone. Anything already written to the blockchain stays there.
- SHA-256
- The standard method Proof uses to make a fingerprint. Because it is standard, anyone can compute the same fingerprint with common tools, without DigiStamp.
- Signature
- A code your wallet produces from a message and the private key of one of its addresses. Anyone can check that it was made by that address for that exact message, without ever seeing the key.
- Signed message
- The exact text a signature covers. Proof keeps it with the proof and includes it on the certificate and in the downloads, so anyone can check the signature with DigiByte Core's verifymessage command.
- Signing address
- The DigiByte address recorded as the signer of a proof and shown on its certificate. Digi-ID wallets use a different address for each site, so it can differ from the address you signed in with.
- Stamp (save permanently)
- Writing a proof's fingerprint into the DigiByte blockchain, as part of a batch's Merkle root. The service that does it is DigiStamp.
- Transaction ID (txid)
- The unique 64-character code of a DigiByte transaction. You paste the txid of your fee payment on the proof page, and the certificate shows the txid of the anchor transaction. Paste one into a block explorer to see the transaction.
Related articles
- Getting startedWhat Proof does, the three levels a proof can reach, and what you need for each.
- Checking a proofHow anyone checks a proof against the original, what the downloads contain, and how to check every part without trusting DigiStamp.
- Saving a proof to the blockchainHow a published proof is stamped on DigiByte: paying the fee, the batch transaction, and confirmations.