How to read chain data
Understand contract addresses, token IDs, metadata, transactions, owner previews and sync timestamps.
- Audience
- Visitors, card owners, admins
- Updated
- 2026-07-29
Before a certificate is minted
Card registration and chain issuance are separate. A registered physical card can correctly show Not Minted and Certificate Being Prepared while its chain fields remain blank.
EditionKey administrators initiate certificate minting after review. Card owners do not start the mint, supply a platform private key or pay EditionKey's mint gas.
Chain fields
Contract Address identifies the deployed contract. Token ID identifies a certificate inside that contract. Transaction Hash points to a specific chain transaction. Metadata URI points to certificate metadata.
The metadata can contain the Card ID, Certificate No., collection, edition, public image and verification URL. The complete image and JSON usually live in durable external storage; the chain records the certificate and its metadata reference.
Explorer links should open public chain explorers such as BaseScan when available. Unknown fields must stay blank or pending; a missing transaction hash is safer than a fabricated one.
Mint and transaction reconciliation
Mint Center generates and stores metadata, sends an idempotent mint request through EditionKey's Base chain gateway, then records the contract, token ID, transaction hash, metadata URI and mint time.
The status moves from Not Minted to Minting and then Minted when the transaction succeeds. A failed transaction is recorded as Failed and can be retried without changing the card's Registry identity.
Sync checks the known transaction against the chain and reconciles its current result. It does not create another token and does not complete a claim or transfer by itself.
When manual chain entry is used
Manual review remains available for imported or externally issued Registry assets whose real chain facts already exist outside EditionKey. Admins may record only verified contract, token, transaction and metadata fields together with a sync timestamp.
Manual entry must not be used to invent proof for an EditionKey card that has not been minted.
Owner and claim context
Before claim, a minted NFT Certificate can remain in the EditionKey platform wallet. After the approved claim flow transfers it, the chain owner preview can change to the card owner's wallet.
Current owner is a shortened chain-level wallet preview. It can indicate certificate custody, but does not by itself prove possession of a physical collectible.