One console for the full CIPNFT flow: register your encryption identity, accept Terms, tokenize encrypted metadata, decrypt by owner or with a view key, manage your vault, and handle offers.
// ENCRYPT, TOKENIZE, VIEW
// KEY LOGIN + REGISTRATION
Key login creates (or imports) your local secret key in this browser. Key registration stores only the corresponding public key on-chain so other participants can encrypt to you. Standard is X25519 sealed-box; Quantum-resistant is ML‑KEM‑768.
// TERMS + FEES
Tokenization is blocked unless you accept the current Terms version on-chain.
// ENCRYPT DATA AND TOKENIZE
Plaintext is encrypted client-side, then stored as ciphertext in contract state.
// OPTIONAL VIEW KEY
If enabled, anyone with the plaintext key can decrypt. This key is never stored on-chain.
// LOAD TOKEN
// OWNER DECRYPT
Uses your encryption identity from Key Login + Registration to decrypt the loaded token.
// VIEW KEY
If the token has view access enabled, anyone with the plaintext key can decrypt.
// MY VAULT
Sync tokens you currently own from the contract's on-chain owner index (state-based), then list/delist, update price, scrub encrypted data from current state, or burn the token.
// INCOMING OFFERS
This loads all offers across all tokens you currently own using the contract’s on-chain owner index + offer index (state). It does not preload full token ciphertext. Each offer row includes the token ID and an OPEN link. Delivering requires your owner decryption identity (to re-wrap the DEK).
// VIEW KEY ON TRANSFER
// MY OFFERS
Offers are visible on-chain. This panel reads your offers from the contract’s on-chain offer index (state) and verifies each offer’s current status. If an offer shows DELIVERED / READY, click VERIFY & FINALIZE to complete the trade (buyer-safe).