Skip to content

Issue a Passport

Andrei Chernikov edited this page Aug 22, 2026 · 1 revision

Issue a Passport

🇬🇧 English · 🇷🇺 Русский

About $0.01, and you need a registered profile first. The Passport page, with the same wallet you registered.

The part that cannot be undone

Five fields go on-chain in readable text and become the passport's card: title, author, short description, domain, object type.

After minting, the card is immutable. A typo in the title is not editable. Correcting it costs revoking the passport and issuing a new one — a second fee, and a revocation visible in the record forever. Read those five fields twice before you press mint.

Everything else — photos, measurements, materials, distinguishing features — goes on-chain only as fingerprints. The content itself stays in your .odpass file. Anyone can check that a file matches the fingerprint; nobody can reconstruct the file from it.

The minimum is enforced by the contract

For a physical object, the passport will not mint without all of:

  • at least one photograph
  • dimensions
  • materials
  • distinguishing features

This is not the website being strict — it is the contract refusing the transaction. A passport without identification anchors could not be matched to an object later, which would make it decorative.

For a digital object, the requirement is the file's exact hash instead.

A seal — a numbered tamper-evident sticker or an NFC chip — is optional and sits on top of the minimum. Worth it for high-value objects; see NFC Seals in the protocol wiki.

After minting

Download the .odpass bundle and keep it. The chain stores only its fingerprint. Lose the bundle and the record still proves when and by whom, but the photos and details are gone and nobody can restore them — not you, not the maintainers, not anyone.

Then decide where it lives:

  • Host it publicly — anyone who scans the object can verify it end to end, with no contact with you.
  • Keep it private — verification still works, but only for someone you hand the file to. The Verify page will say the record exists and that no hosted file is on record.

Put the Passport ID on the object: printed on the label, as a QR code, or written to an NFC tag.

Later changes

Sales, damage, restoration and attestations are recorded as append-only events. They are added; nothing is ever rewritten. The history of an object is the whole point, so it accumulates rather than being corrected.

One privacy rule worth knowing before you type

Do not put exact locations on-chain. Mutable state is public and permanent — "in the artist's studio at this address" is readable by everyone, forever, including people looking for something to steal. The specification's privacy rules cover this.

Reference website


🌐 Languages


The standard itself


Website · Verify

Clone this wiki locally