Standards
Standards and Compatibility
1Do composes established standards and protocolizes runtime and wallet-level asset capabilities.
2 sectionsstandards
01
Directly used today
- ERC-7702 for EOA delegation to Account Runtime.
- EIP-712 for orders, plans, sessions, and wallet-level transfer signatures.
- ERC-1271 for contract-wallet signature validation.
- ERC-7201 for namespaced account and app storage.
- ERC-165 for runtime capability discovery.
- ERC-20 / ERC-721 for current assets.
- ERC-3156 for the Flash Loan app's lender and borrower interfaces.
02
1Do proposal interfaces
The ERC drafts initiated by 1Do form four layers: assets, wallet asset management, signed authorization and transfer, and Runtime execution. The current deployment directly implements the Runtime, one-time pull, and signed-transfer capabilities while remaining compatible with existing ERC-20 / ERC-721 assets.
- Asset layer — ERC-7196 / ERC-7561: simplified tokens and NFTs that retain balance, ownership, and basic transfer semantics. They remove ERC-20 transferFrom, approve, and allowance, and ERC-721 approve, setApprovalForAll, getApproved, isApprovedForAll, and safeTransferFrom. They are compatibility directions, not asset requirements for the current deployment.
- Wallet asset-management layer — ERC-7204 / ERC-7564: wallet-level token transfer and allowance management, plus NFT transfer and operator management, as companion wallet interfaces for simplified assets. The current Runtime does not require this layer.
- Signed-authorization layer — ERC-8064 / ERC-8067: Permit extensions for ERC-7204 / ERC-7564 based on EIP-712, ERC-1271, scoped nonces, and validity windows, allowing relayers to submit wallet-level token or NFT authorization. They currently remain drafts.
- Signed-transfer layer — ERC-8112 / ERC-8114: one explicit token or NFT transfer authorized by an offchain signature, currently implemented by Account. 1Do also extends ERC-8112 with asset == address(0) for native currency.
- Runtime execution layer — ERC-8280: the minimum Runtime app host and local-enablement interface, represented by IAccountAppRuntime. Any address may trigger executeRuntimeApp, but execution still requires wallet-local enablement, global Registry gating, and app-specific validation.
- Runtime execution layer — ERC-8284 / ERC-8285: target-bound token and NFT pulls valid only within one execution window, represented by IWalletAssetPullExecutor. Authority binds target, asset, amount cap or tokenId and leaves no reusable authorization afterward.
Proposal status
The 1Do ERC proposals in this section should currently be read as drafts. Numbers, interfaces, and names may change during review. Integrations should verify the proposal repositories, 1do-core source, deployed ABIs, and deployed versions.