ERC / EIP ↔ Neo Standards Mirror

Most application-level Ethereum standards have a Neo N3 counterpart — sometimes a one-to-one NEP, sometimes a stronger native primitive that makes the EIP unnecessary, and sometimes a migration pattern with known semantic differences. This module catalogs the checked-in mirror set: pick a category below, then flip between the ERC/EIP detail, the Solidity implementation, and the equivalent Neo C# implementation.

Use the mirror as a migration map, then validate production behavior against the deployment results and the Solidity support matrix.

Categories

Token Standards

Fungibles, NFTs, multi-token, RWA, multi-priv, fungible-metadata

ERC-20, 721, 777, 1046, 1155, 1363, 2135, 2981, 3525, 3643, 4400, 4519, 4906, 4907, 4494, 4910, 5006, 5008, 5023, 5169, 5192, 5216, 5375, 5380, 5484, 5489, 5496, 5507, 5521, 5528, 5570, 5585, 5615, 5646, 5679, 5725, 5732, 5750, 5773, 6059, 6093, 6105, 6150, 6220, 6239, 6381, 6454, 6672, 6909, 6982, 2309, 5114, 6147, 7007, 7053, 7066, 7144, 7160, 7231, 7432, 7528, 7531, 7634, 7857, 7943

65 standardsNEP-11 / NEP-17 / NEP-24

Account & Authentication

Ownership, signatures, smart accounts, modular wallets, SIWE, paymasters, endorsements

ERC-173, 1271, 2612, 2767, 3009, 4337, 4361, 5267, 5313, 5453, 5564, 6066, 6492, 6551, 7405, 7585, 7656, 7677, 7715, 7758, EIP-712, EIP-191, EIP-7702, EIP-3074

24 standardsNative witness scopes

Infrastructure & Patterns

Proxies, blueprints, diamond storage, registries, multicall, security middleware

ERC-165, 1014, 1056, 1167, 1820, 1967, 2470, 2535, 2771, 3448, 3668, 5202, 5269, 6357, 7201, 7579, 7746, 7786, 8042

19 standardsNEP-22 + Oracle native

DeFi Building Blocks

Vaults (sync, async, cancellable), flash loans, governance, bonds

ERC-3156, 3475, 4626, 5805, 6372, 7092, 7535, 7540, 7575, 7818, 7944

11 standardsComposition patterns

Protocol-Level EIPs

Things Ethereum had to fix at the protocol

EIP-1559, 2718, 2930, 3198, 3855, 3860, 4844, 1153, 6780, 2098

10 EIPsMost are no-ops on Neo

Live on TestNet

The frontend catalog currently exposes 129 ERC/EIP mapping pages across the five categories above. Forty-seven standards in this mirror have Solidity and Neo C# contract pairs deployed on Neo N3 TestNet (network magic 894710606). The same invocation matrix runs against the Solidity (compiled with neo-solc) and the Neo C# (compiled with nccs) versions, recording pass/fail assertion results for both implementations.

Snapshot status

The checked-in TestNet snapshot is a validation matrix, not an all-green parity certification. The latest checked-in result records 147 / 183 assertions passing; failures and repro details are listed in deployments/RESULTS.md.

Standard	Solidity	Neo C#
ERC-20 ↔ NEP-17	d76434af…f96	1f3a9b41…b43a
ERC-165 InterfaceDetector	2b5db552…1e6	a400b6cb…f49
ERC-721 ↔ NEP-11	48b5f8f5…7aa	15c664d5…baf
ERC-777 Hooked	d0f1fb49…7d	0d64d453…849
ERC-1014 DeterministicFactory	c267a2ea…b0e	462113ca…4f8
ERC-1155 Multi-Token	f1d7867c…317	ef019e6f…6bd
ERC-2309 BatchMint	20262b3b…900	2e157ce2…918
ERC-2470 SingletonFactory	625c19cb…012	602d11ec…df5
ERC-2981 ↔ NEP-24	ade57dfd…234	bf3fe7eb…5e1
ERC-3525 Bond	d0fd56da…2c6	fcfde62a…6c
ERC-4906 DynamicMetadataNFT	86f4d37e…793	3429da47…061
ERC-5114 Achievement	91e34b16…41f	d9d32f5f…039
ERC-5192 Soulbound	1b75ecb9…034	7081fcf3…2b
ERC-5267 DomainExposer	1dd8a392…b6c	dcfa0661…877
ERC-5484 ConsensualSBT	8a9e1835…951	02317b71…ac
ERC-6147 GuardedNFT	af32605e…64f	274c031d…9df
ERC-7201 NamespacedStorage	bb2553c7…f32	0932ad78…05d
ERC-7818 Expirable	fcaaf98f…64d	cb1b0441…6e0
ERC-173 Ownable	19977aea…be4	ce89aec2…459
ERC-1271 MultiSig	88eec008…de7	88079ecd…682
ERC-1820 Registry	02704624…ee4	8f36ff27…59d
ERC-1056 DID	dd6d4a48…f50	d13806f6…b30
ERC-1967 Upgradeable	48f6d58a…245	096f01e4…976
ERC-2535 Diamond	26b6f333…527	1b3c602c…dcf
ERC-2612 PermitToken	edd521fd…aa0	b451279f…70c
ERC-2771 Forwarder	6653a8da…ed9	1463ad54…0a
ERC-3156 FlashLender	b7d5cd14…7ec	a82c8142…84b
ERC-4337 SmartAccount	aa11f9ef…a56	e26da230…09f
ERC-4494 PermitNFT	e683fa29…b66	c7056410…257
ERC-4626 Vault	faf678fd…0f	0e515ad2…0c5
ERC-5805 Voting	b87fa58c…110	1d33818b…692
ERC-6372 Clock	e3c55758…42b	eb454a6b…335
ERC-6492 PreDeploySig	95170df7…9d9	7dd2cd08…fc9
ERC-7540 AsyncVault	d8838ba1…b41	c2137b33…26e
ERC-7575 MultiAssetVault	985a293c…6b1	d85564c8…ffc
ERC-7579 ModularAccount	5e6edfc0…528	cbd2e64f…f86
EIP-191 PersonalSign	64d3b4d2…eb1	d06071f8…14e
EIP-712 TypedData	8e501310…fdd	38e8f069…c9a
EIP-1153 TransientGuard	7e4e4812…a66	e67e6815…7bf
EIP-2098 CompactSig	d63ea34d…1d9	b2701b6d…eee
EIP-2718 TypedTx	4e2300b8…bf6	b600afb3…cb8
EIP-2930 AccessList	02a174b4…2c3	3570e80f…6ad
EIP-3198 FeeAware	8ed358ae…0a0	32b98cb2…630
EIP-3855 Push0	52b86044…e4d	6704d604…9f6
EIP-3860 InitcodeSize	5d95f5db…728	b58a104c…337
EIP-6780 SelfDestruct	67a59c17…930	8acf52e9…f8eb
EIP-7702 SetCode	b156b370…751	158d0d7f…bfd

Checked-in TestNet snapshot: 147 / 183 assertions pass across 47 deployed pairs. The full pass/fail matrix is in results.json and RESULTS.md. The deploy runner now exits non-zero when any compile, deploy, liveness, or assertion check fails.

What about the other catalog entries?

The checked-in catalog includes deployable demos for most entries. A small set remains outside the live TestNet pair matrix because the Ethereum mechanism is either protocol-specific, superseded by another EIP, or not yet part of the deployment snapshot.

Eighty-two catalog entries are not in the live TestNet pair matrix:

• EIP-1559 (fee-market base-fee auction) — Neo doesn't auction fees.
• EIP-4844 (blob transactions) — Neo doesn't have blobs.
• EIP-3074 (AUTH/AUTHCALL) — superseded by EIP-7702 and covered by Neo witness scopes.
• ERC-6909 (minimal multi-token) — documented as a direct Neo C# port but not part of the checked-in deployment snapshot.
• ERC-1363 (payable token) — built into NEP-17's onNEP17Payment callback; no standalone deploy needed.
• ERC-3009 (transfer with authorization) — subsumed by Neo's witness scopes; no separate contract required.
• ERC-6551 (token bound accounts) — registry-pattern catalog entry; deploy targets a per-collection setup rather than a single fixture.
• ERC-1167 (minimal proxy clones) — registry-pattern catalog entry; cloning is a deploy-time operation rather than a single fixture.
• ERC-4361 (Sign-In with Ethereum) — primarily an off-chain server convention; on-chain verifier is application-specific.
• ERC-3668 (CCIP Read) — subsumed by Neo's native Oracle service; no on-chain mirror contract needed.
• ERC-7528 (native asset address) — Neo native assets (NEO, GAS) already have well-known contract hashes; nothing to deploy.
• ERC-7656 (generalised contract-linked services) — registry-pattern catalog entry, like ERC-6551.
• ERC-3448 (MetaProxy Standard) — registry-pattern catalog entry; same deploy-time shape as ERC-1167.
• ERC-7535 (native asset vault) — collapses to ERC-4626 with asset = NEO/GAS; covered by the existing ERC-4626 deployment.
• ERC-4907 (rental NFT) — NEP-11 storage extension; no separate fixture needed beyond a port-side example.
• ERC-6093 (custom token errors) — vocabulary convention; no contract to deploy.
• ERC-7786 (cross-chain messaging gateway) — bridge-adapter pattern; per-bridge deploy depends on the chosen transport.
• ERC-5313 (light contract ownership) — view-only convention; satisfied by every existing contract that exposes getOwner.
• ERC-5564 (stealth addresses) — announcer contract is small; deploy depends on a wallet-SDK rollout to be useful.
• ERC-6066 (NFT signature validation) — NEP-11 storage extension scoped per tokenId; no separate fixture beyond an example NFT.
• ERC-3643 (T-REX regulated token) — multi-contract framework (token + identity registry + compliance modules); per-deployment shape rather than a single fixture.
• ERC-5202 (blueprint contract format) — Neo's deploy primitive already separates blob storage from execution; no magic-prefix container needed.
• ERC-7944 (async cancellation for ERC-7540) — extension of ERC-7540's request queue; covered by the existing ERC-7540 deployment plus the additional cancel flow.
• ERC-8042 (diamond storage) — storage convention for ERC-2535; covered by the existing ERC-2535 deployment plus storage-prefix discipline.
• ERC-5679 (token mint/burn) — selector convention; satisfied by every NEP-17 / NEP-11 contract that exposes a Mint wrapper.
• ERC-2135 (consumable interface) — NEP-11 storage extension; no separate fixture needed.
• ERC-7160 (multi-metadata NFT) — NEP-11 storage extension; no separate fixture needed.
• ERC-3475 (abstract storage bonds) — port-side primitive; deploy is per-issuance configuration.
• ERC-7092 (financial bonds) — port-side primitive; deploy is per-bond configuration.
• ERC-6982 (default lockable tokens) — NEP-11 storage extension; covered by per-collection deploy.
• ERC-7677 (paymaster web service) — off-chain JSON-RPC convention; on-chain footprint is optional escrow contract.
• ERC-7144 (ERC-20 with transaction validation) — NEP-17 transfer override + per-policy validator; per-deployment shape.
• ERC-7943 (Universal RWA Interface) — capability-flag + compliance umbrella; per-deployment shape rather than a single fixture.
• ERC-5006 (Rental NFT user extension for ERC-1155) — NEP-11 divisible + record storage; per-collection shape.
• ERC-2767 (contract ownership governance) — interface convention; satisfied whenever a governance contract owns the governed contract.
• ERC-7758 (modern transfer-with-authorization) — same Neo answer as ERC-3009; covered by witness scopes.
• ERC-5169 (client script URI) — token-metadata extension; one method addition to any NEP-11 / NEP-17 contract.
• ERC-5375 (NFT author and consent) — NEP-11 metadata extension; per-collection configuration shape.
• ERC-5023 (shareable NFT) — NEP-11 multi-holder extension; per-collection shape.
• ERC-7066 (lockable extension) — NEP-11 storage extension; covered by per-collection deploy.
• ERC-7432 (NFT roles) — NEP-11 storage extension; per-collection role conventions.
• ERC-6105 (no-intermediary trading) — NEP-11 listing/swap extension; per-collection shape.
• ERC-5615 (ERC-1155 supply extension) — NEP-11 divisible storage extension; covered by per-collection deploy.
• ERC-5773 (multi-asset tokens) — NEP-11 storage extension; per-collection shape.
• ERC-6059 (nestable NFTs) — NEP-11 parent-child storage extension; per-collection shape.
• ERC-4519 (physical-asset NFTs) — NEP-11 + device-pubkey extension; per-device deploy depending on physical batch.
• ERC-5570 (digital receipt NFT) — NEP-11 metadata extension; per-merchant deploy shape.
• ERC-6150 (hierarchical NFTs) — NEP-11 storage extension; per-collection shape.
• ERC-6220 (composable equippable parts) — NEP-11 + catalog extension; per-collection shape.
• ERC-5380 (entitlement extension) — NEP-11 storage extension; per-collection shape.
• ERC-5489 (NFT hyperlink) — NEP-11 storage extension; per-collection shape.
• ERC-6672 (multi-redeemable NFTs) — NEP-11 storage extension; per-collection / per-operator shape.
• ERC-7634 (limited transfer count) — NEP-11 storage extension; per-collection shape.
• ERC-7007 (AI-generated content) — NEP-11 attestation extension; per-collection / per-model shape.
• ERC-5725 (vesting NFT) — NEP-11 + NEP-17 underlying-token mechanics; per-deployment configuration.
• ERC-6454 (transferable detection) — NEP-11 view extension; satisfied by every contract that exposes IsTransferable.
• ERC-7715 (AA permission grants) — Witness-scope-based authorisation; per-account permission module deploy.
• ERC-5507 (refundable NFTs) — per-token escrow + refund window; per-collection deploy.
• ERC-5528 (refundable ERC-20) — per-buyer escrow + refund window; per-deployment shape.
• ERC-5521 (referable NFT) — citation-graph extension; per-collection shape.
• ERC-5646 (state fingerprint) — view extension; satisfied by every contract that hashes its mutable state.
• ERC-5585 (NFT authorization rights) — per-(tokenId, rights) storage extension; per-collection shape.
• ERC-6239 (semantic SBT) — NEP-11 + RDF claims storage; per-collection shape.
• ERC-7053 (digital media indexing) — event-emission convention; no per-fixture deploy needed.
• ERC-7405 (modular wallet) — per-account module dispatch; per-wallet deploy.
• ERC-7585 (cross-chain SIWE) — off-chain library convention; on-chain verifier is application-specific.
• ERC-6381 (NFT emote repository) — standalone singleton; one global deploy serves all NEP-11s.
• ERC-7857 (AI agent NFT) — NEP-11 + encrypted-metadata extension; per-collection / per-service deploy.
• ERC-7231 (identity-aggregated NFT) — NEP-11 + Merkle-root extension; per-collection shape.
• ERC-7531 (staked NFT recognition) — staking-contract view; per-staking-contract deploy.
• ERC-5216 (ERC-1155 allowance) — NEP-11 divisible storage extension; per-collection shape.
• ERC-5008 (NFT nonce) — NEP-11 storage extension; per-collection shape.
• ERC-4910 (royalty-bearing NFTs) — NEP-11 + NEP-24 escrow extension; per-collection shape.
• ERC-5732 (commit interface) — standalone commit-reveal contract; one global deploy serves any consumer.
• ERC-4400 (NFT consumable, lite) — NEP-11 storage extension; per-collection shape.
• ERC-5750 (method extensibility) — convention satisfied by every NEP-17 / NEP-11 (already four-parameter shape).
• ERC-5269 (ERC detection) — manifest supportedstandards already provides this natively.
• ERC-5453 (endorsement / generalised permit) — native witness scopes already provide per-call signature auth.
• ERC-5496 (multi-privilege NFT) — NEP-11 storage extension; per-collection shape.
• ERC-6357 (multi-delegatecall) — Neo's transaction script natively supports multi-invoke without contract changes.
• ERC-1046 (fungible tokenURI) — NEP-17 view convention; per-deployment metadata pointer.
• ERC-7746 (security middleware hooks) — pre/post hook chain pattern; per-deployment shape.

The other protocol entries in the table have live demos exposing their Neo counterparts, such as transaction version, witness scopes, PUSH0, NEF size, ContractManagement.Destroy, and NEP-30 verify.

Source pairs, deploy script, full results JSON, and instructions to reproduce live under docs/standards-mirror/deployments/.

How to Read This

Each entry shows three views in a tabbed nav bar:

Tab	What it shows
ERC / EIP Detail	The standard's purpose, interface, motivation, and the corresponding Neo mechanism.
Solidity Implementation	A reference Solidity implementation as deployed on Ethereum.
Neo C# Implementation	The idiomatic Neo equivalent — either a direct NEP, a composition pattern, or an explanation of why the EIP is a no-op on Neo because the protocol already covers it.

How To Read The Pills

Each entry carries a parity pill that summarizes the mirror relationship:

Pill	Meaning
NEP-XX (green)	Direct NEP equivalent. Same interface shape, sometimes simpler.
Native (blue)	Subsumed by Neo's protocol primitives. No NEP or contract needed.
Pattern (orange)	Composition pattern in the Neo devpack — no dedicated NEP, but a clear recipe.

Module Internals

Each category page registers its entries with a shared <StandardsMirror> Vue component that drives the master/detail UI. All content is plain Markdown — VitePress's bundled Shiki highlights every Solidity and C# block, and the search index covers everything.

To add another standard, append a <StandardEntry> block to the appropriate category page. The page automatically picks it up.

For deeper reference on the Neo standards behind the mirrors, see Standards and Contracts and devpack/standards/STANDARDS_MAPPING.md.