ERC-2309: Consecutive Transfer Event
A gas-optimization standard: instead of emitting one Transfer event per token in a batch mint, emit a single ConsecutiveTransfer(fromId, toId, fromAddr, toAddr) event covering the entire range. Indexers (TheGraph, OpenSea) parse this and synthesize per-token transfers off-chain.
Required Event
event ConsecutiveTransfer(
uint256 indexed fromTokenId,
uint256 toTokenId,
address indexed fromAddress,
address indexed toAddress
);Neo Equivalent: Same Event Pattern
Neo's event system supports identical semantics — emit one event covering a range instead of N events. Below is the Neo C# port. The event signature is named ConsecutiveTransfer and indexers can subscribe to it just as they would on Ethereum.
Live on Neo TestNet
Both implementations are deployed on Neo N3 TestNet (network magic 894710606).
| Implementation | Contract Hash | Deploy Tx |
|---|---|---|
Solidity (neo-solc) | 0x20262b3b96d92a0db7bfdc4782903fb3d997f900 | 0x014b746a…f4fd44 |
Neo C# (nccs) | 0x2e157ce2532dee6084f53c1a848975bd960be918 | 0x60d5dcf1…7d1bd2 |
Cross-implementation invocations match on claimDeployer, totalMinted, getDeployer. Source pairs under docs/standards-mirror/deployments/erc-2309/.
