Truepoint

Testnet Specific

Truepoint Demo Registry

The Truepoint product on this page describes the production registry — not yet built. What's live below is a working demo on Ethereum Sepolia. The four conditions are simulated, not commercial.

01 · ASSET CLASS

Trade-finance invoices only

Other asset classes (Treasuries, real estate, fund interests) are out of scope for the demo registry.

02 · SAMPLE ASSETS

Randomly generated invoices

Submitters can auto-generate sample invoices to test the flow. Generated and user-submitted assets are recorded together — every entry is on-chain.

03 · ATTESTATION

9 wallets, randomized verdict

Attestation is performed by 9 demo Sepolia wallets operated by Truepoint. Each wallet's verify-or-flag vote is randomized — no real, independent human reviewer is involved on testnet.

04 · PERMANENCE

All entries are on-chain

Submissions, votes, and final status are written to Ethereum Sepolia and publicly queryable. Nothing is reversible inside the demo.

The chain is faithful. The registry has to be neutral.

Off-chain claims become on-chain truth. The chain only records. It doesn't verify.

No verification gate exists between platforms. Anything submitted is written down faithfully.

The same asset can be registered on every platform. No single registry can see the duplicate.

01 Cross-platform visibility

The shared registry every platform checks before minting.

02 Continuous attestation

Independent specialists verify, not once, but continuously.

03 Structural neutrality

No platform owns it. That's why every platform can trust it.

04 Immutable record

Every lock, flag, and vote is on-chain and unalterable.

02Mechanism

A four-step protocol.
Duplicate registration is structurally impossible.

STEP 01

Submit

A tokenization platform submits the asset's identifying fields to the registry contract. The required field set is fixed per asset class — trade-finance invoices use five.

STEP 02

Fingerprint

The contract computes keccak256(abi.encode(...)) over the asset's required fields. The submitting wallet is excluded — two platforms submitting the same asset produce the same hash.

STEP 03

Detect

Registry scans for the fingerprint. Found → reverts with AssetAlreadyRegistered, returning the lock owner and timestamp. Not found → status set to Pending.

STEP 04

Attest

A pool of independent attestors votes. Pool size is set per asset class; the threshold model is constant — a supermajority verifies. Trade-finance invoices use a 9-attestor pool with a 7-of-9 threshold. Threshold met → status Locked. Not met → status Flagged. Every vote and dispute reason is on-chain.

03Data Model

Identifying fields.
One fingerprint.

Asset class shown: trade-finance invoice · Other classes use their own identifying fields

Trade-finance invoices commit five fields. Other asset classes have their own fixed fields. Change any one value and the fingerprint changes entirely — hash the same values from any wallet on any platform and you arrive at the same 32 bytes.

01

Issuer Registration ID

GB-12345678

02

Counterparty Registration ID

US-87654321

03

Invoice Number

INV-2024-00521

04

Invoice Value

USD 1,250,000.00

05

Due Date

2024-09-15

Fingerprint Output

keccak256(abi.encode(...))

—

AlgorithmSHA-3 / KECCAK-256 Output32 bytes / 64 hex chars Platform fieldexcluded from hash Asset classTrade finance invoice

Computed in your browser with the same keccak256 the registry uses on-chain. The fingerprint reveals no underlying data — only that this exact combination has been registered. Trade-finance invoices use these five identifying fields in both testnet and production; other asset classes use their own.

04Outcomes

Three on-chain states.
Every record is reachable.

PENDING

Awaiting consensus.

Asset submitted and fingerprinted. Attestor voting in progress. No further submission of this fingerprint can succeed until consensus resolves.

Emitted: AssetSubmitted(fingerprint, platform, timestamp)

LOCKED

Registered & locked.

Threshold met. Asset is locked to the submitting platform. Any subsequent submission of this fingerprint from any platform reverts with AssetAlreadyRegistered.

Emitted: AssetLocked(fingerprint, platform, verifiedCount)

FLAGGED

Threshold not met.

Attestation consensus failed. Full vote breakdown and dispute reasons remain on-chain. The submitting platform may proceed at its own risk — Truepoint records, it does not judge.

Emitted: AssetFlagged(fingerprint, verifiedCount, disputedCount)

One registry. Every platform. One identity.

Truepoint Demo Registry

The chain is faithful. The registry has to be neutral.

A four-step protocol.
Duplicate registration is structurally impossible.

Identifying fields.
One fingerprint.

Three on-chain states.
Every record is reachable.

Submit an asset.
Or query one.

One registry. Every platform. One identity.

Truepoint Demo Registry

The chain is faithful. The registry has to be neutral.

A four-step protocol.Duplicate registration is structurally impossible.

Identifying fields.One fingerprint.

Three on-chain states.Every record is reachable.

Submit an asset.Or query one.

A four-step protocol.
Duplicate registration is structurally impossible.

Identifying fields.
One fingerprint.

Three on-chain states.
Every record is reachable.

Submit an asset.
Or query one.