Sepolia tech previewConfidential Modular Token

Public passports. Private fields. Policy-bound disclosure.

Encrypted product passport infrastructure for scoped access and aggregate predicate checks.

Configured Sepolia contracts, wallet transactions, and browser-side reads.

Demo CMT Passport

Public passport shell with private encrypted fields.

initialized
Public facts
Collection
Demo CMT
Token
#042
Schema
product-passport
Encrypted handles
bytes32
inspectionScoreeligible
0x7c42...b901
privateOwnerIdentityeligible
0x43be...19a2
module
assetCore
type
EUINT64
predicate
ENABLED
Scoped access

Decrypt only the approved field handle.

Aggregate predicate

Return one encrypted yes/no result.

Public shell stays readable.
Policy returns disclosure or one aggregate result.
Sepolia previewWallet gated writes

Confidential product passports need more than metadata.

CMT Studio shows a modular token model where public product facts, encrypted handles, access policies, and predicate policies stay connected on one passport.

Public passport shell

Issuer, collection, token identity, and schema context stay readable for marketplaces and inspectors.

Encrypted token fields

Private values live as field handles, not public plaintext, while modules keep field definitions explicit.

Policy-bound disclosure

Scoped access and aggregate predicates answer authorized questions without turning every field public.

How to read a CMT.

The demo is not a static NFT viewer. It walks through the confidential field lifecycle.

Token shell

ERC-721 identity plus public product context.

Field definition

Module, type, access policy, predicate policy.

Encrypted handle

Per-token private value read through getField.

Policy result

Authorized decrypt or one aggregate yes/no.

predicate surface

Prove private facts without exposing private fields.

The test user can compare encrypted handles, request approved disclosure, and receive one aggregate predicate result.

Warranty still valid

predicate
guaranteeExpiration >= current time
aggregate yes/no

Supplier risk below threshold

predicate
forced labor + anomaly scores in bundle
private threshold check

Disclosure is authorized

predicate
viewer has scoped field access
decrypt eligible handle

DPP data initialized

predicate
required encrypted handles are non-zero
ready for access flow
Studio control plane

Follow the same field through every demo surface.

The test website is most convincing when users see one encrypted field move from initialization to disclosure and aggregate proof.

getField
handle is non-zero
moduleId + fieldId
same pair across flows
predicate intent
2 to 8 encrypted fields
result
one encrypted yes/no

Two demo collections. One confidential field model.

Each collection has its own public metadata and module map, but encrypted fields use the same disclosure surface.

Demo workflow

Test the CMT flow in one pass.

Start at mint, initialize encrypted fields, then test access, decrypt, and aggregate predicate execution.

Start testing

Mint

Create a Sepolia demo CMT.

Initialize

Set encrypted demo handles.

Grant

Claim group or scoped access.

Decrypt

Reveal only eligible fields.

Predicate

Compute one aggregate yes/no result.

module execution surface

Built around explicit modules, field definitions, and policy checks.

CMTBase
ERC-721 token shell, module execution, field storage
Modules
Authenticity, guarantee, luxury info, DPP core, access, predicates
Field definitions
Type, access policy, predicate policy, initialization status
Demo controller
Allowlisted mint, initialize, update, grant, and predicate approval flows
Test release scope

Serious demo, clear boundaries.

The landing points to the Sepolia preview and does not claim legal certification, production compliance, or mainnet readiness.

Controlled disclosure
Encrypted field handles
Aggregate predicate intents

Give the tester a real path, not a brochure.

Start with a CMT, initialize encrypted fields, then test disclosure and aggregate predicate behavior.