ERC-2018 primary sources — 2026-05-12

Project status in this pass

• ERC-2018 is a stagnant draft ERC, but it still exposes a distinct lower-layer control surface inside regulated-token and e-money designs.
• The clearest first-party sources were the EIP itself, the linked discussion issue, and the IoBuilders reference implementation repo.
• The main reusable insight is not security token branding but the explicit split between ordering a transfer and later clearing or rejecting it.

Primary-source snapshots

1) ERC-2018 draft

• URL: https://eips.ethereum.org/EIPS/eip-2018
• Key excerpts/signals:
  • Defines a ClearableToken interface that extends ERC-1996 and introduces orderTransfer, orderTransferFrom, processClearableTransfer, executeClearableTransfer, rejectClearableTransfer, and operator-authorization functions.
  • Says the clearing process turns the promise of a transfer into the actual movement of money, with a clearing agent deciding whether the transfer can be executed.
  • Specifies that ordered amounts are not deducted from the payer balance but are also not available for another transfer, preserving later executability.
  • Adds explicit status transitions: Ordered, InProcess, Executed, Rejected, and Cancelled.
  • Frames the motivation around offchain KYC / AML checks that may prevent a regulated-token transfer from completing in one step.
• Why it mattered:
  • This is the strongest first-party source showing ERC-2018 is really a two-step transfer-clearing primitive rather than just another compliance token interface.

2) ERC-2018 discussion issue

• URL: https://github.com/ethereum/EIPs/issues/2104
• Key excerpts/signals:
  • Restates the banking-clearing framing and the idea that a clearing agent decides whether the promised transfer becomes final movement of money.
  • Emphasizes that the proposal is meant for the time between transaction commitment and settlement rather than for ordinary instant transfers.
• Why it mattered:
  • The issue is short, but it reinforces that the standard is meant to model a real clearing workflow, not merely a transfer hook.

3) IoBuilders clearable-token reference implementation

• URL: https://github.com/IoBuilders/clearable-token
• Key excerpts/signals:
  • Describes itself as the reference implementation of the Clearable Token EIP and explicitly says it was being built to help propose a standard e-money token to the community.
  • Repeats that the clearable agent can execute, reject, or mark a transfer in process, and that the payer can only cancel before the in process transition.
  • Publishes sequence diagrams for executed, cancelled, and rejected transfer paths plus a state diagram for the full lifecycle.
  • Ships as an npm package (eip2018) for Solidity inheritance.
• Why it mattered:
  • The repo makes the workflow more legible than the EIP alone and shows ERC-2018 as a reusable middleware layer for later e-money / regulated-token stacks.

4) Raw README of the reference implementation

• URL: https://raw.githubusercontent.com/IoBuilders/clearable-token/master/README.md
• Key excerpts/signals:
  • Gives the most readable explanation of the three core post-order outcomes: execute, reject, or mark in process.
  • Clarifies that held funds preserve execution certainty while still awaiting offchain validation.
• Why it mattered:
  • Useful compact source for the practical transfer lifecycle and operator role.

Whitepaper status

• No standalone ERC-2018 whitepaper or litepaper surfaced in this pass.
• The EIP, the discussion issue, and the reference implementation repo were the strongest primary materials.

Working conclusion

ERC-2018 is best cataloged as a transfer-clearing primitive for regulated tokens and e-money systems. Its real analytical value is that it isolates a lower layer many richer compliance stacks bury: user-ordered transfers can reserve funds now, then wait for a clearing agent to move them, reject them, or lock them into an intermediate processing state after offchain checks.