Home

Welcome to Object Digital Passport 👋

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

Object Digital Passport (ODP) is an open standard for giving real things — artworks, limited-edition products, archival documents — a digital passport that anyone can verify, free, forever. No company in the middle, no subscription: just a public registry on the Polygon blockchain and open-source tools.

A passport proves three things:

1. When the object was registered (blockchain timestamp),
2. Who registered it (a public profile ID you can check on the issuer's own website),
3. That the description hasn't changed since (cryptographic fingerprints — hashes).

And with the Object ID-compatible profile, the same passport doubles as theft-recovery documentation for police, insurers, and registries.

Where to go next

Page	What's there
Quick Start	Verify an object in 2 minutes; register and mint your first passport
How Verification Works	Hashes, trust layers, and what each result means — in plain words
NFC Seals	Secure chips on physical objects: what they prove, iPhone/Android support
Object ID Profile	Documenting objects so they can be recovered if stolen
Publishing Your Profile ID	Where to publish your ID, the .well-known/odp.json file, and what a directory may claim
FAQ	Costs, lost wallets, privacy, common questions
Using the reference website	A separate wiki: this site's screens, wallet setup, what to do when something fails

Key links

• 🌐 Reference website — verify, register and issue in the browser
• 📄 Specification — the full protocol, rendered
• 💬 Discussions — questions and ideas welcome
• ⚠️ Alpha status: the contract may still change before v1 (target: January 2027). Don't rely on it for long-term records yet.

Which version this wiki describes

These pages describe v0.6, which is what is deployed on Polygon mainnet and what the website and apps talk to today. Everything here is accurate for it.

v0.7 exists as a pre-release and is deployed nowhere. It adds edition passports and per-unit activation keys; the contracts and tests are done, but no issuer tooling and no activation page exist yet, so nothing can be issued under it. It was published so the design can be argued with before it is set in a contract — see the release note.

Each v0.x is a separate on-chain registry generation, not an upgrade: passports do not migrate between them. This wiki gains v0.7 pages when v0.7 is deployed, not before.