Wrap — eDMT

Loading wallet…

Plate IV.A./Wrapper snapshot

Current wrapped supply.

Circulating supply of wrapped wholes and BURN fragments.

Wrapped wholes

—pcs

ERC-721 supply

Wrapped BURN

—BURN

ERC-20 supply · 10^9 per ETH

Indexer head

#26,334,076block

real status; the other cards are placeholders

Operator EOA0x342b…0a21

IV.B.1./Mint wENAT

eNAT into wENAT.

Hand one raw eNAT to the operator, then let the contract mint a tradable ERC-721 for you. This page prepares both the protocol calldata and the contract call.

01.Choose your blkPick a whole eNAT currently held by your protocol address. The page builds the transfer calldata to the operator.
02.Page waits for finalityAfter the first wallet confirmation, the page records the tx and waits the 12–15 minute finality window.
03.Continue automaticallyOnce confirmations are ready, the page gets the operator receipt and opens the second wallet confirmation to mint wENAT.
04.NFT arrivesYour wallet receives wENAT tokenId = blk. You can list it on /trade/whole.

Pitfalls

If you send to the wrapper contract address, unwrap is permanently dead. The custodian must be the operator EOA.
If you call wrap() before finality, a mainnet re-org can void the transfer — the contract will accept it and then be unbacked.

Plate IV.C./Plate IV.C. · Why wrap

When wrapping is justified.

Arguments for wrapping

Composability with standard ERC-721 / ERC-20 tooling — AMMs, marketplaces, portfolio trackers.
Liquid secondary market for fragments without the price opacity of peer-to-peer gwei transfers.
Custody abstraction — the operator EOA can serve users who do not want to self-manage their raw key lifetime.

Arguments against

Strictly more trust: a single operator EOA private-key compromise can drain all wrapped supply. There is no multi-signature backstop.
Finality lag (~12–15 min) on every wrap and unwrap; not suited for workflows that need instant state changes.
Era, rarity, and similar tags are lost after wrapping — the wrapper only recognizes block numbers.

Read contract spec→Stay raw · mint calldata→

When wrapping is justified.

Arguments for wrapping

Composability with standard ERC-721 / ERC-20 tooling — AMMs, marketplaces, portfolio trackers.
Liquid secondary market for fragments without the price opacity of peer-to-peer gwei transfers.
Custody abstraction — the operator EOA can serve users who do not want to self-manage their raw key lifetime.

Arguments against

Strictly more trust: a single operator EOA private-key compromise can drain all wrapped supply. There is no multi-signature backstop.
Finality lag (~12–15 min) on every wrap and unwrap; not suited for workflows that need instant state changes.
Era, rarity, and similar tags are lost after wrapping — the wrapper only recognizes block numbers.

Wrap into ERC.

Current wrapped supply.

eNAT into wENAT.

wENAT back to eNAT.

BURN into bENAT.

bENAT back to BURN.

When wrapping is justified.

Wrap into ERC.

Current wrapped supply.

eNAT into wENAT.

wENAT back to eNAT.

BURN into bENAT.

bENAT back to BURN.

When wrapping is justified.