Standards

ERC-4626 — the tokenized vault standard.

ERC-4626 defines a common interface for any vault that wraps a single ERC-20 underlying asset. Deposit, mint, withdraw, redeem, share accounting — every 4626 vault speaks the same language, so the rest of DeFi can integrate without bespoke adapters. 4626.fun applies the standard to creator coins on Base.

Reference implementations: OpenZeppelin · Solmate · spec: EIP-4626.
Finalized 2022 ERC-20 underlying Composable shares Audit-friendly

The interface, in one breath

01

Asset and shares

Every 4626 vault has one underlying ERC-20 (asset()) and issues an ERC-20 share token (balanceOf, transfer, etc.). Shares represent a pro-rata claim on totalAssets().

02

Deposit and withdraw

deposit(assets, receiver) mints shares. redeem(shares, receiver, owner) burns shares and returns assets. convertToShares and convertToAssets express the current exchange rate.

03

Limits and previews

maxDeposit, maxWithdraw, previewDeposit, previewRedeem let integrators reason about caps and round-trip values without simulating a full transaction.

Why it matters for creator coins

Composability inherited free

Wallets, portfolio trackers, aggregators, and downstream protocols already understand ERC-4626. A creator-coin vault built on the standard inherits that integration surface without writing a single bespoke adapter.

Audit-friendly surface area

The standard's narrow interface and well-known reference implementations mean auditors can focus on the strategy and accounting logic rather than re-deriving deposit-and-redeem semantics from scratch.

Strategy modularity

4626 vaults can route capital through any combination of DeFi primitives — lending, concentrated LP, cross-chain — while presenting a single uniform share to the depositor.

Transferable receipts

A vault share is just an ERC-20. It can be held, sent, used as collateral, or wrapped further — the position itself is portable, not locked inside a custom interface.

EIP-7540 — async deposits and redemptions

Some vault strategies can't always settle in a single transaction — cross-chain bridges, concentrated LP unwinds, or auction-priced exits. EIP-7540 extends ERC-4626 with a request-and-claim lifecycle so async withdrawals stay inside the standard's interface.

requestDeposit / requestRedeemDepositors signal intent. The vault may queue, batch, or schedule the actual settlement based on its strategy state.
pending → claimableThe vault transitions the request through a public on-chain state machine. Integrators can query pendingDepositRequest and claimableDepositRequest.
claimOnce claimable, the depositor (or anyone permitted) finalizes the deposit or redemption in a normal transaction. More on EIP-7540 →

Read more