Arc における「アプリケーション」の意味
取引インフラではなくアプリケーションです。ERC-8004 のエージェントレジストリはオラクルではなくここに置いています。高頻度の NewFeedback イベントが運ぶのは価格ではなくソフトウェアエージェントの評価スコアであり、デコードしたペイロードがそれを裏付けています。各行には、それを特定した測定が添えられています。
| アドレス | ラベル | トークン | 根拠 | 最初のブロック | 最終ブロック |
|---|---|---|---|---|---|
| コントラクトデプロイサービス | — | 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: 評価レジストリ（2 番目のデプロイ） | — | 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 | — |