-
Notifications
You must be signed in to change notification settings - Fork 0
Quick Start
🇬🇧 English · 🇷🇺 Русский
This walks through the reference website as one worked example. Anything specific to that site — screens, buttons, wallet problems — is documented in its own wiki: Using the reference website. The rules below hold for any implementation.
- Open the Verify page.
- Enter the Passport ID from the object (looks like
ODP-2026-03-004829301), or scan its QR code. - Read the result: the page fetches the on-chain record, downloads the passport bundle (if the issuer hosts one), and compares cryptographic fingerprints.
-
Always do the human step too: find the issuer's profile ID (like
C-482-930-174-005) on their official website or social profile. The blockchain proves the record exists — the issuer's public reputation proves who stands behind it.
If you have the object's .odpass file (a ZIP the creator gives you), you can drop it into the Verify page and check it offline-style — no hosting needed.
- Get a crypto wallet (MetaMask or similar) — use a separate wallet just for ODP, not the one with your savings.
- Get a little POL on the Polygon network (a few cents' worth covers many operations).
- Open the Profile page, connect the wallet, choose your type:
- C — individual creator (artist, photographer, maker)
- B — brand or studio
- P — proof institution (experts, auction houses)
- M — museum or collection
- You'll receive a permanent profile ID. Publish it on your website and social profiles — visibly. That public link is what makes your passports trustworthy.
- If you registered as a brand, museum or institution, also upload
/.well-known/odp.jsonto your domain — a small static file that lets software confirm the ID without a human checking by hand. See Publishing Your Profile ID.
- Open the Passport page and connect the registered wallet.
- Fill in the object: title, author, short description — these become the passport's readable on-chain card — plus photos and the Object ID identification anchors. For a physical object the hard minimum is enforced: at least one photo, dimensions, materials, and distinguishing features — the passport won't mint without them. A digital object needs its exact file hash.
- A seal is optional (since v0.6): a numbered tamper-evident sticker or an NFC chip adds a stronger physical binding on top of the minimum (see NFC Seals) — recommended for high-value objects.
- Mint. The card goes on-chain readable; everything else goes as fingerprints (hashes) — photos and details stay in your
.odpassfile. Later changes (sales, damage, restoration) are recorded as append-only events: added, never rewritten. -
Download and keep the
.odpassbundle. It's your passport's full content; the chain only stores its fingerprint. Host it publicly (then everyone can verify via the web), or keep it private and share on request. - Put the Passport ID on the object: printed, QR code, or NFC.
- 📁 Never lose your
.odpass— the chain can't restore it. - 🔑 Never lose the wallet — profiles can't be recovered (passports already minted stay valid).
- 📢 Publish your profile ID on channels you control — it's the trust anchor. How to do it properly.
- 🗺️ Don't put exact locations on-chain — mutable state is public forever (privacy rules).
Object Digital Passport — open standard, MIT licensed. These wiki pages are friendly explanations; the normative source is SPEC.md (English; русский перевод is informational). Questions and corrections → Discussions (in English, so everyone can follow).
Object Digital Passport
🇬🇧 English
🇷🇺 Русский
- Главная
- Быстрый старт
- Как работает проверка
- NFC-пломбы
- Object ID и профиль
- Публикация ID профиля
- Вопросы и ответы
Verify something · Spec (по-русски) · Repo