Skip to content
eDeed
Build on eDeed

Integrate the ownership layer

Give your users portable, verifiable ownership rights — no custody, no bridge, no wrapped tokens. You consume the protocol; you never run it.

Designed to plug into

eDeed deeds are plain ERC-20s on Monad — every wallet, DEX, and app already speaks them.

MetaMaskRabbyCoinbase WalletFrameAny ERC-20 walletDEX aggregatorsBlock explorersIndexersMetaMaskRabbyCoinbase WalletFrameAny ERC-20 walletDEX aggregatorsBlock explorersIndexers
You consume — you don’t host

Integrators use the deployed protocol surfaces. There is no node to run, no prover to operate, and no need to fork or modify the protocol to build on it.

How the protocol works

Four atoms, one invariant: the locked pool always backs every deed in circulation.

  1. 1

    Lock

    A user locks a real asset in the source-chain LockBook. It stays there — eDeed never takes custody.

  2. 2

    Mint the deed

    A zero-knowledge proof mints a deed on Monad. Its balance is ownership and redemption authority in one.

  3. 3

    Move freely

    The deed is an ordinary ERC-20. Transfer, split, or compose it for a fraction of a cent.

  4. 4

    Redeem

    The final holder burns the deed; the pool releases the real asset on its source chain to that holder.

What you can build

Accept deeds as payment

Read an ERC-20 balance on Monad. No proofs, no special SDK — just standard token calls.

Delegate with subkeys

Let an app or bot spend on a user’s behalf with a revocable subkey embedded in the deed.

Track routes & proofs

Index Lock, Mint, and Redeem events to follow ownership across every channel.

Verify, don’t trust

Every move is backed by an SP1 proof anyone can check. No operator sits in the path.

Supported networks

Any EVM chain can host a LockBook, a Deed, or both. Six channels are live or verified today.

E
Ethereum
Locks assetsHosts deeds
B
Base
Locks assetsHosts deeds
M
Monad
Locks assetsHosts deeds
A
Arbitrum
Locks assets
O
Optimism
Locks assets
P
Polygon
Locks assets

Add your chain

Bringing a new EVM network into the mesh is a deploy + wiring job — the protocol code is chain-agnostic.

  1. 1

    Deploy the pair

    Deploy EdeedLockBook on the asset chain and EdeedDeed on the deed chain for your (chain, asset) pair.

  2. 2

    Pin the proof key

    Register the SP1 verification key so only valid lock/burn proofs can mint or redeem.

  3. 3

    Wire the reader

    The engine’s witness reader is chain-agnostic — point it at the new chain’s headers and state.

  4. 4

    Open a channel

    List the new (source → target) route. It goes live once an end-to-end proof passes.

Address reference

Current testnet deployment — the addresses your integration reads.

RouteAssetLockBook · asset escrowDeed · ownership right
EthereumMonadETH0x71fe…31f00xc7D7…a2b3
EthereumMonadUSDC0x7A2f…695a0x70Ec…6888
BaseMonadETH0x2a8d…E6c90x5c6C…1e36
BaseMonadUSDC0x5EB5…81300x574F…6c4f
MonadEthereumMON0x165e…F4350x4e5a…83A4
MonadBaseMON0x2686…c5870xB1db…1463
BaseEthereumETH0x7cA9…74230x6894…9Ae3
BaseEthereumUSDC0x7291…236e0x820A…3d24
EthereumBaseETH0x8036…939D0x8352…4d0F
EthereumBaseUSDC0x7C1E…195C0x94C7…ecb0

Core infrastructure (shared)

Deployed once, reused by every channel. CREATE3-deterministic: the same address recurs on every chain (ADR-058).

ContractChainAddress
Redeem verifier (SP1 Groth16)
Same address on every lock chain
Sepolia + Base0xbc67…2dC6
Ethereum light client (BLS)
Anchors Sepolia finality on Monad
Monad0x3DCC…26B8
Monad checkpoint oracle
MON→ETH trusted mint gate (challenge window)
Sepolia0x8823…f068
Monad testnet · chain 10143Ethereum Sepolia · chain 11155111Base Sepolia · chain 84532