Что означает «Адреса с метками» в Arc
Весь реестр одним списком. Имя здесь получено из связи с фабрикой, из строки в собственном байткоде контракта, из заголовка блока или от самого уровня исполнения — никогда из догадки и никогда из внешнего сходства. Класс обоснования публикуется рядом с каждой строкой именно затем, чтобы метка, опирающаяся только на самоназвание контракта через name(), выглядела заметно слабее метки, опирающейся на связь с фабрикой, а не стояла рядом как равная.
| Адрес | Метка | Токен | Обоснование | Первый блок | Последний блок |
|---|---|---|---|---|---|
| Сервис развёртывания контрактов | — | Sole emitter of 19,856 logs on topic0 0x1445764f... in blocks > 54,080,000. Bytecode carries `Bytecode cannot be empty`, `Custom contract deployment failed`, `Counter deployment failed`, `Referral transfer failed` — a paid deploy-a-contract service, which is a plausible source of the 61,665 distinct contracts that emitted OwnershipTransferred over the same range. |
Адрес — это 20-байтовый идентификатор, который может хранить баланс и, если содержит код, исполнять его. Газ в Arc оплачивается в USDC, поэтому баланс адреса выражен в долларах, а не в волатильном активе.
| 54 281 486 |
| — |
| 0x8004A818...9A494BD9e | ERC-8004: реестр идентичностей | — | Its EIP-1967 implementation 0x7274e874...9c02 carries the literal `ERC8004IdentityRegistry` in deployed bytecode, read at block 54,290,008 — the standard names itself. Corroborated by the event stream: emitted 566 Registered(uint256,string,address) and 568 MetadataSet(uint256,string,string,bytes) events in 53,963,591-54,259,161; both signatures were recovered by matching keccak preimages against the observed topic0s (0xca52e62c...bc4a and 0x2c149ed5...468b) and match exactly. Also mints an ERC-721 per registration and emits EIP-4906 MetadataUpdate. On every one of the 568 MetadataSet events the indexed topic equals keccak of the readable key carried in the payload, so the key is verified rather than assumed. 505 of its registrations publish a base64 data-URI agent card, and those cards embed the literal URL https://eips.ethereum.org/EIPS/eip-8004#registration-v1. 0x8004-prefixed vanity address, alongside the reputation registry 0x8004b663...8713 and the validation registry 0x8004cb1b...4272.Строка в байткоде · измерено на блоке 54 290 008 | 54 290 008 | — |
| 0x16e0FA7f...1BE31dA34 | ERC-8004: реестр репутации (реализация) | — | The implementation 0x8004b663...8713 delegates to, read from EIP-1967 slot 0x360894a1... at block 54,281,486. Bytecode carries `Self-feedback not allowed`, `bad identity`, `Empty URI`, `clientAddresses required`.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x8004B663...3B7388713 | ERC-8004: реестр репутации (прокси) | — | Busiest of the two emitters of the chain's THIRD-busiest event, 278,675 of 476,450 logs on topic0 0x6a4a6174... in blocks > 54,080,000. An EIP-1967 minimal proxy (storage slot 0x360894a1... holds 0x16e0fa7f...da34). NOT a price oracle: the implementation's bytecode carries `Self-feedback not allowed`, `bad identity`, `clientAddresses required`, and the event's own data payload decodes to the ASCII string `successful_execution` plus three empty strings — an attestation record, not a price. The standard is named from cryptographic proof rather than resemblance: keccak of `NewFeedback(uint256,address,uint64,int128,uint8,string,string,string,string,string,bytes32)` is exactly the observed topic0 0x6a4a6174...febc, recovered by brute-forcing preimages. It sits at a 0x8004-prefixed vanity address alongside the identity registry 0x8004a818...bd9e and the validation registry 0x8004cb1b...4272, and the agent cards published through that identity registry embed the literal URL https://eips.ethereum.org/EIPS/eip-8004#registration-v1. It indexes agentId, clientAddress and tag1, so its third topic is keccak(tag1) rather than the feedback counter — verified on 464,153 of 464,153 events.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x4C80b778...e49AE9FFE | ERC-8004: реестр репутации (второе развёртывание) | — | Second emitter of the same feedback event, 197,775 logs in blocks > 54,080,000. A standalone 13,188-byte deployment (no proxy) whose bytecode carries `Feedback not found`, `Already revoked`, `IdentityRegistry not set`. Emits nothing else. This emitter carries the decisive evidence against reading the event as a price feed: its 736-byte payload is a percent-encoded data URI that decodes to `{"d":"trading/futures Score:88","s":88,"e":"cex:bybit","ts":"2026-07-29T16:28:05.861Z"}` — a subject, an integer score, an issuing entity and a timestamp. Sampled payloads score `trading/spot` from `cex:binance` and `risk/simulation` from `security:tenderly`. There is no price, no pair and no decimals anywhere in it — the score's scale is a uint8 in the event itself, and score/10**decimals equals the number stated in that JSON on 781,125 of 781,125 events carrying one. The standard is named from cryptographic proof rather than resemblance: keccak of `NewFeedback(uint256,address,uint64,int128,uint8,string,string,string,string,string,bytes32)` is exactly the observed topic0 0x6a4a6174...febc, recovered by brute-forcing preimages. This deployment indexes the uint64 feedback counter where the other indexes tag1, so the same topic0 carries two incompatible payload layouts.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x8004Cb1B...7acEB4272 | ERC-8004: реестр валидаций | — | Sole emitter of ValidationRequest(address,uint256,string,bytes32) (42 events) and ValidationResponse(address,uint256,bytes32,uint8,string,bytes32,string) (18 events) in 53,962,678-54,278,830. Both signatures were recovered by keccak preimage search against the observed topic0s 0x530436c3...5059 and 0xafddf629...49ae and match exactly. Request and response share a bytes32 request hash in their third topic, and the agent ids they name are the same ids the reputation registry at 0x8004b663...8713 scores. Rare by design rather than by disuse: 60 events against that registry's 464,155. Its EIP-1967 implementation 0xdb31f5d9...7f99 carries no naming string — only the revert `bad identity`, which the reputation registry's implementation also carries — so this row rests on the two signatures, the shared 0x8004 vanity prefix and the shared agent ids, not on a name the contract gives itself. It is the weakest of the ERC-8004 rows and is marked as such.Сигнатура события · измерено на блоке 54 290 008 | 54 290 008 | — |
| 0x76a816EF...7b065d9De | InfinityName | — | name() returns `InfinityName`, symbol() `INAME`; classified ERC-721 by the indexer. Sole emitter of 7,383 logs on each of two topics in blocks > 54,080,000, in a chain whose event registry already carries NameRegistered and PrimaryNameSet — consistent with a naming service, but only its own metadata names it.Со слов контракта · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x1290B4f2...233e9ADCc | SayGM | — | Sole emitter of four topics totalling 235,511 logs in blocks > 54,080,000 — 65,382 + 65,383 + 65,386 + 39,393. Bytecode carries `SayGM: User not in leaderboard`, `SayGM: Wait before sending another GM`, `SayGM: Incorrect ETH fee`.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0xECF33655...e234e4453 | zkCodex: квест деплоера | — | Sole emitter of 42,675 logs on topic0 0x27f210c3... in blocks > 54,080,000. Bytecode carries the literal `Hello World with zkCodex!` alongside `Exceeds max supply` and `Referral payment failed`. Hundreds of ERC-20 contracts in the token registry are named `zkCodex Token Deployer`, which is what this contract mints.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x34A0b64a...8aDD67E9C | Фабрика AMM (роутер 0x284c5afc) | — | The router 0x284c5afc...66b1, sender of 4,625 Swap events in blocks > 54,100,000, answers factory() with this address. Its own bytecode carries only generic reverts (`Pool exists`, `Identical tokens`, `Insufficient liquidity minted`), so no brand can be asserted.Связь с фабрикой · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0xd67F63A4...c8B5743a5 | ArcFlow V25: фабрика | — | Deployed bytecode contains `ArcFlowV25: PAIR_EXISTS`, `ArcFlowV25: IDENTICAL_ADDRESSES`, `ArcFlow V25`. Emitted 560 PairCreated events in 54,051,461-54,220,147, and 380 of the 460 addresses that emitted a Uniswap-V2-shaped Swap answer factory() with it — the largest V2 family on the chain by pair count.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0xa16aF7FC...23b23e3a8 | Arcin V2: фабрика | — | Deployed bytecode contains the literal `Arcin V2`. The router 0xa01a6f36...eab9, sender of 598 Swap events in blocks > 54,100,000, answers factory() with this address.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x724B24E0...b8f68A8D4 | OnmiFun: фабрика | — | Deployed bytecode contains `OnmiFunFactory: FORBIDDEN`, `OnmiFun: PAIR_EXISTS` and the LP token name `Onmifun LPs`. Its pairs carry the LP symbol Onmi-LP — for example 0x95b0d01ebf734178e27ea8c44d654792e1ce9e29.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x9DE50a65...9c121821D | Tower: фабрика | — | Deployed bytecode contains the revert prefixes `Tower: PAIR_EXISTS`, `Tower: IDENTICAL_ADDRESSES`, `Tower: K`. Pairs that answer factory() with this address carry the LP symbol TOWER-LP — for example 0xfa4cc09c073742b7ea534e0b55b8d2bb3089668c (USDC/EURC), the busiest V2-shaped pair on the chain.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x205879F4...31756a210 | Фабрика, совместимая с V2 (резервы uint256) | — | Emitted 1,146 PairCreated events in 53,959,833-54,256,240, the most of any V2-shaped factory. 518 of the 541 addresses that emit Sync(uint256,uint256) — the wide-reserve variant, topic0 0xcf2aa508... — answer factory() with it, and those same pairs emit the standard Uniswap-V2 Swap. No brand string in its bytecode; no router of its own was identified.Связь с фабрикой · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x065b21b2...E7D11a010 | Фабрика, совместимая с V3 | — | Emitted 46 PoolCreated events in 53,974,730-54,210,026. The router 0xb5d2f3aa...1c7f, sender of 334 Swap events in blocks > 54,100,000, answers factory() with it.Связь с фабрикой · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x0fB6EEDA...52a27f59c | Фабрика, совместимая с V3 | — | 58 of the 139 addresses that emitted a Uniswap-V3-shaped Swap answer factory() with this address, including the three busiest pools on the chain (0x1c02648c..., 0x715f78de..., 0x66a038f2...). Two routers name it: 0xa545bcb1...c31b and 0xbf4479c0...275f. Its bytecode carries no brand string, so this is deliberately not given a protocol name.Связь с фабрикой · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x7E875574...68914c01A | Фабрика, совместимая с V3 | — | Five of the addresses that emitted a V3-shaped Swap answer factory() with it. The router 0xc2d2829c...de68, sender of 722 Swap events in blocks > 54,100,000, names it.Связь с фабрикой · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0xAb6A8AAb...9688a1971 | Фабрика, совместимая с V3 | — | Emitted 15 PoolCreated events in 53,976,111-54,220,224; 20 of the 139 addresses that emitted a V3-shaped Swap answer factory() with it. Two routers name it: 0x996ebb17...69a5 and 0x509cf58c...3d01. No brand string in its bytecode. It answers owner() with 0x3682652c...55b8, the same EOA that owns the ArcFlow NFT, which suggests this is ArcFlow's V3 deployment — but a shared owner EOA is a statement about who holds a key, not about what the code is, and the ArcFlow V2 factory exposes no owner() to corroborate it. Recorded as a lead; `protocol` stays null until something stronger than a shared key supports the brand.Связь с фабрикой · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0xBa27C71b...91Fd53A93 | Фабрика, совместимая с V3 (больше всего пулов) | — | Emitted 6,467 PoolCreated(address,address,uint24,int24,address) events in 53,959,754-54,280,912 — more than every other factory on the chain combined. owner() returns 0xd8c7430b...5103. Its pools carry almost no swap volume, and its bytecode has no brand string, so it is named by shape and rank only.Сигнатура события · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x60EDeFB0...3Ba1979e2 | XyloNet: фабрика | — | Deployed bytecode contains `XyloFactory: INVALID_A` alongside the embedded pool creation code (`XyloPool: INVALID_A`, `XyloPool: TOO_EARLY`, `XyloPool: ZERO_ADDRESS`) and the LP-token prefix family `XyloERC20: INVALID_SIGNATURE`. Both labelled XyloNet contracts point at it: the pool 0x3df3966f...3bb1 and the router 0x73742278...1023 each answer factory() with this address. It emits no logs of its own over the indexed range, so it is identified by its bytecode and by the two contracts that name it rather than by a creation event.Строка в байткоде · измерено на блоке 54 285 491 | 54 285 491 | — |
| 0x3DF3966F...0ce083BB1 | XyloNet: пул USDC-EURC | — | name() returns `XyloNet USDC-EURC LP`, symbol() `XYLO-USDC-EURC`. Bytecode carries `XyloPool: A_CHANGE_TOO_LARGE` and `XyloPool: INVALID_A` — a stableswap amplification parameter, not a constant-product pair. Emitted 24,340 logs on one Xylo-specific topic in blocks > 54,080,000.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x284C5Afc...A9dfd66b1 | Роутер AMM (пулы 0x34a0b64a) | — | factory() returns 0x34a0b64a...7e9c. Sender of 4,625 Swap events in blocks > 54,100,000 — the third-busiest router on the chain.Связь с фабрикой · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x49f9636F...Fe6BC219B | Роутер AMM и реестр пулов | — | Second-busiest emitter of the same aggregator-shaped Swap event, 102,982 logs in blocks > 54,080,000. Bytecode carries `Invalid path`, `No Liquidity`, `Pool already exists`, `Same token addresses` — it both creates pools and routes through them. No brand string.Строка в байткоде · измерено на блоке 54 281 486 | 54 281 486 | — |
| 0x4AA8c7Ac...1ac76824A | ArcFlow V25: роутер | — | factory() returns 0xd67f63a4...43a5, the ArcFlow V25 factory. Sender of 436 Swap events in blocks > 54,100,000.Связь с фабрикой · измерено на блоке 54 281 486 | 54 281 486 | — |