Plate IV./Plate IV. · Wrap

Wrap into ERC.

Wrapping issues a portable ERC claim backed by the underlying eNAT held, in the protocol view, by a multisig EOA. It is strictly more trust-exposed than staying raw.

Trust disclosure · application layer

This surface is part of the ERC-wrapper application layer. Wrapped assets are custodied, in the protocol-layer view, by a multi-signature EOA. Its keys can, in principle, sign any emt-transfer. There is no contract-enforced pause.

Custodian (multisig EOA): 0x9e2C5e8c1A2B3D4F5C6E7B8A9D0c1E2F3A4B5C6D
Threshold: 5-of-7
Scope: All wrapped whole eNATs and BURN fragments

You can always refuse this layer: mint and transfer via raw calldata on the protocol layer directly — no contract, no multisig, no intermediary.

Plate IV.A./Wrapper snapshot

Current wrapped supply.

Circulating supply of wrapped wholes and BURN fragments, plus the latest block for which the oracle multisig has published a witness.

Wrapped wholes

—pcs

ERC-721 supply

Wrapped BURN

—BURN

ERC-20 supply · 10^9 per ETH

Latest oracle witness

#24,836,709block

block signed by ≥ M of N indexer keys

Oracle health

—

awaiting deployment

Custodian0x9e2C…5C6D·Oracle dashboard

IV.B.1./Wrap whole eNAT

Whole into ERC-721.

Transfer your whole eNAT to the protocol operator multisig, then call wrap(blk, transferTxHash). The oracle witnesses the transfer and the contract mints an ERC-721 with tokenId = blk to your address.

01.Send emt-transferSubmit a canonical emt-transfer with src="«blk»", amt="1", to=0x9e2C5e8c… from your wallet.
02.Wait finalityThe indexer waits ~12–15 minutes. Until finality, do not call wrap() — a re-org could leave both sides broken.
03.Call wrap()Invoke IeNATWrapped721.wrap(blk, transferTxHash). The oracle verifies the transfer signed by the multisig and mints the ERC-721.
04.Receive ERC-721Your wallet now holds a transferable ERC-721 tokenId = blk. The underlying eNAT sits at the multisig EOA.

Step 1 · raw calldata (data field)

data:,{"p":"edmt","op":"emt-transfer","tick":"eNAT","amt":"1","to":"0x9e2C5e8c1A2B3D4F5C6E7B8A9D0c1E2F3A4B5C6D","src":"24736710"}

Set to = protocol operator multisig (not the wrapper contract). Set src = "24736710" to address the whole. Sign with the EOA that currently holds blk 24736710.

Pitfalls

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

IV.B.2./Unwrap whole eNAT

ERC-721 back to raw.

Burn your ERC-721; the multisig countersigns an emt-transfer returning the whole eNAT to your address. Expect ~12–15 minutes of settlement.

01.Call unwrap()Invoke IeNATWrapped721.unwrap(blk). Your ERC-721 is burned and the Unwrapped event is emitted.
02.Multisig countersignThe protocol operator multisig listens for Unwrapped events and countersigns an emt-transfer with src="«blk»", to=msg.sender.
03.Wait finalityOnce broadcast, the indexer waits for finality before marking the whole as owned by your address again.
04.Raw ownership restoredYou are once again the protocol-layer owner of block #blk. No wrapper involvement from here on.

Step 1 · contract call

IeNATWrapped721.unwrap(uint256 blk)

You call the wrapper; the multisig then produces a signed emt-transfer at the protocol layer. Both steps are required for the unwrap to complete.

Pitfalls

If > (N−M) multisig signers refuse to sign, your ERC-721 is already burned but the emt-transfer is never broadcast. Recovery requires off-chain escalation.
Do not attempt to recover by minting again — first-is-first assigns ownership to whoever captures the block, and unwrap has already committed the block's history.

IV.B.3./Wrap BURN fragment

Gwei into ERC-20.

Transfer a burn amount from one of your fragments or wholes to the multisig, then call deposit(amtGwei, transferTxHash). The contract mints the equivalent BURN ERC-20 to your address.

01.Send emt-transferBuild a canonical emt-transfer with src="balance" (or src="«blk»" to break a whole), amt="«gwei»", to={multisig}.
02.Wait finalitySame 12–15 minute window as wrap-whole. Until finality, the indexer will not emit a witness.
03.Call deposit()Invoke IBurnWrapped20.deposit(amtGwei, transferTxHash). The oracle witnesses the transfer.
04.Receive BURNThe contract mints amtGwei × 10^9 of BURN ERC-20 to your address (decimals 9).

Step 1 · raw calldata (data field)

data:,{"p":"edmt","op":"emt-transfer","tick":"eNAT","amt":"10000000","to":"0x9e2C5e8c1A2B3D4F5C6E7B8A9D0c1E2F3A4B5C6D","src":"24736710"}

BURN is fungible: decimals 9, 1 BURN = 1 gwei of protocol-layer burn. Sending to the wrapper contract instead of the multisig will leave the deposit un-backed.

Pitfalls

Wrapping fragments consolidates your FIFO queue into a single pool. Provenance of individual fragments is lost once wrapped.
If oracle health drops below M-of-N, wrap is paused while unwrap remains open. Check the snapshot panel before submitting step 1.

IV.B.4./Unwrap BURN fragment

ERC-20 back to gwei.

Burn your BURN ERC-20; the multisig countersigns an emt-transfer of the equivalent gwei back to your address. Settles in ~12–15 minutes.

01.Call withdraw()Invoke IBurnWrapped20.withdraw(amtGwei). The contract burns your BURN and emits a Withdrawn event.
02.Multisig countersignThe multisig produces an emt-transfer with src="balance", amt="«gwei»", to=msg.sender.
03.Wait finality~12–15 minutes. After finality, the indexer credits your address with a new fragment row.
04.Fragment creditedYour address has a new FIFO-ordered fragment row. You can keep it raw, wrap it again, or use it as src in future transfers.

Step 1 · contract call

IBurnWrapped20.withdraw(uint256 amtGwei)

Only whole-gwei amounts. Fractional BURN cannot be withdrawn since the protocol layer counts in gwei.

Pitfalls

If multisig signers are offline, Withdrawn is already emitted but the emt-transfer may be delayed until quorum is reached.
Withdrawn fragments enter your FIFO queue at position 'now' — they do not restore the original provenance of pre-wrap fragments.

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 multisig can serve users who do not want to self-manage their raw key lifetime.

Arguments against

Strictly more trust: multisig private-key compromise can drain all wrapped supply.
Finality lag (~12–15 min) on every wrap and unwrap; not suited for fast flipping.
UI annotations (era, rarity) do not survive through the ERC layer — the wrapper is fungible by block, not by story.

Read contract spec→Stay raw · mint calldata→