Plate VII./Plate VII. · Documentation

Canonical documentation.

The eDMT canon is small, strict, and honest about its boundaries. Protocol rules are immutable; everything else is a reference implementation you may fork or replace.

Authoritative source·protocol/00·living document — check repo for changes

Plate VII.A./By layer

Four surfaces.

Protocol at the base; contracts, backend, and frontend above; narrative and FAQ aside. Each layer has a different change policy.

VII.A.1.protocol/

Protocol layer

Trustless. Rules are frozen at deployment. No admin, no upgrade key, no pause.

00 · 协议规范
The only authoritative source for protocol semantics — mint, transfer, FIFO, first-is-first.
05 · Indexer Spec
How a compliant indexer is expected to behave, including reorg handling and convergence.

VII.A.2.contracts/

Contracts reference

Application layer. May fork; each fork inherits its own trust assumptions.

06 · Marketplace Spec
ERC-721 / ERC-20 wrapper, Marketplace, and Oracle specification. Includes the 'custody = signature' hard rule.

VII.A.3.backend/

Backend services

Anyone may run their own. Disagreement triggers convergence via protocol rules, not voting.

07 · Backend Spec
Indexer deployment, API shape, Supabase schema, multisig daemon topology.

VII.A.4.frontend/

Frontend reference

Anyone may run their own UI. All user-facing actions must disclose trust.

08 · Frontend Spec
Product spec — Mint, Explore, Trade, Wrap, Stats, Profile, Docs.
09 · Design Tokens
Why the design system looks like a state gazette rather than a startup landing page.
design-system.md
Design system handbook — tokens, patterns, components, do/don't.

VII.A.5.narrative/

Narrative & culture

Cross-layer. Educational. Must not contradict the protocol spec.

Narrative — why eDMT exists
Opens in this site.
Technical overview — cross-layer walkthrough
Opens in repository.
Valuation — economic model
Opens in repository.
FAQ — common questions
Opens in this site.

Plate VII.B./By role

Entry points by reader.

Each role has a recommended path through the canon. You may always read out of order — nothing you read later will contradict what you read first.

I.Holder

Potential user

You want to know what this is and whether to participate.

01Read Narrative · Why eDMT.
02Skim the FAQ.
03Open Mint and observe a block.

II.Indexer

Protocol engineer

You want to run a compliant indexer or audit protocol rules.

01Read protocol/00 end to end.
02Read protocol/05 implementation spec.
03Run a reference indexer alongside your own and diff the state.

III.Contracts

Smart-contract engineer

You want to implement or audit the ERC wrappers and marketplace.

01Read protocol/00 for the hard rules contracts depend on.
02Read contracts/06 including §1.5 'custody = signature'.
03Diff your implementation against the reference ABI.

IV.Backend

Backend · DevOps

You want to deploy the indexer, API, and multisig daemons.

01Read backend/07 deployment spec.
02Read protocol/05 to know what the indexer must produce.
03Read contracts/06 §5 for oracle multisig topology.

V.Frontend

Frontend · design

You want to ship a web app on top of the reference backend.

01Read frontend/08 product spec.
02Read frontend/design-system.md and 09-Design-Tokens.md.
03Read contracts/06 §1.5 / §7 for required trust disclosure UI.

VI.Research

Protocol researcher

You want to understand the reasoning or fork the design.

01Read all layers end to end in order 00 → 05 → 06 → 07 → 08 → narrative.
02Focus on 'trust assumption' and 'anti-pattern' sections.
03Write down where your fork disagrees and justify each divergence.

Plate VII.C./Plate VII.C. · Promises

What we commit to.

A short table of standing commitments. Each commitment is pinned to a specific layer — violating it constitutes a deviation from the reference spec.

Promise	Layer	Substance
Rules never change	Protocol	Once published on mainnet (element registration + ticker deploy), the letter of the protocol never changes.
No admin, no upgrade, no pause	Protocol	Protocol-level selectors contain zero admin authority. There is nothing to seize.
No burn threshold beyond 1 gwei, no supply cap, no team reserve	Protocol	Scarcity is produced by EIP-1559 distribution. We add no artificial constraint.
Anyone can run an independent indexer	Protocol	No centralized feed. Reference implementations are convenience, not gatekeeper.
Contract code is immutable after deployment	Application	The wrapper contract itself carries no upgrade, pause, or fee-change authority.
The wrapper does not pretend to be trustless	Application	Multi-sig EOA custody is disclosed on every application-layer surface.
Users always have a raw calldata path	Protocol fallback	If you distrust the application layer, you may mint and transfer peer-to-peer at the protocol layer forever.

Plate VII.D./Plate VII.D. · Glossary

Core terms.

eDMT: Ethereum Digital Matter — a non-arbitrary token protocol on ETH mainnet.
eNAT: First ticker under eDMT; one block, one eNAT, indivisibly tied to that block's EIP-1559 burn.
burn(N): floor(baseFeePerGas(N) × gasUsed(N) / 10^9), unit: gwei.
first-is-first: For a given block N, ownership goes forever to the first on-chain emt-mint tx that captures it.
whole: A complete eNAT tied to a single block, carrying its full burn balance.
fragment: A sub-gwei balance produced when a whole is partially transferred; FIFO-ordered per address.
src: Required field on emt-transfer calldata: "«blk»" for whole view, "balance" for fragment view.
Indexer: Program that decodes ETH mainnet calldata into eDMT state — it does not create facts, it reports them.
Protocol Operator: M-of-N multisig EOA; it is the protocol-layer owner of all wrapped assets.
Oracle: Multi-indexer multi-signature witness scheme feeding application-layer contracts with indexer state.

Plate VII.E./Related

Elsewhere on this site.

Narrative FAQ Stats Repository EIP-1559