FRESH BOUNDED ETHEREUM/POLYGON ATTACKER CHECK

The fixed Ethereum head is26310742 (2026-10-31 05:45:59UTC); Polygon96480071 (05:46:03UTC). Scope is the same10 tracked addresses, explicit four-token filters on each chain, Ethereum native trace_filter, canonical Polygon native/CTF events, and tracked-account emitted events. No arbitrary-wallet or public-hub expansion.

This check found actual new Ethereum E4 activity after the preceding04:14 snapshot: nonce0→2 and0.5→0.3997874672242106ETH. The36 full/partition queries form12 consistent groups. They contain two unique top-level E4 transaction traces, no subcalls, and no other matching activity.138 of140 pinned state values are unchanged. Polygon cash/native/CTF/control scope is unchanged; secondary owner054 and batchnonce3 persist.

E4 nonce0 at04:39:35UTC sends0.1ETH to3dce0a29139a851da1dfca56af8e8a6440b4d952, transactionf166955fd26ad73eac5d739f40baf7ca543f51814e572b3000d59d53dff772f8. Nonce1 at04:44:47UTC sends0ETH to the same address, transactioneb8585ed4dd02041b21606f2d7b102e4137ec9b69b4dd8251927dd9532ab4e35. Both complete EIP1559 RLP/hash reconstructions and actual signatures recoverE4; independent provider records and fresh ecrecover calls agree.

The first input contains1201 opaque bytes. The second contains81 public bytes referencing the exact first hash. Complete financial inputs are retained for exact offline verification, remain uninterpreted, and are not treated as factual statements or instructions. No embedded instructions were followed.

Gas148375318649480+64157457139920=212532775789400wei.0.5ETH minus0.1ETH minus gas equals0.3997874672242106ETH exactly. The recipient had balance0,nonce0,empty runtime before the first transaction and0.1ETH,nonce0,empty runtime through the fixed head. This does not prove an EOA, recipient private-key custody or a common controller. A counterfactual contract/offchain arrangement is possible. The amount alone does not classify a mixer, bridge or exit. Any separately established published recovery-address role must preserve its explicit chain and source provenance.

E4 and the observed recipient have no exact match in the bounded role-labeled117-address inventory, which includes the verified E044 trio. Selected26 is only a subset; neither set is exhaustive or establishes human ownership.

One auxiliary Polygon Publicnode owner/nonce batch returned403. Successful dRPC calls close that getter gap; the failure is preserved and never counted as zero. No supplementary profile/activity API was fetched in this lane.

Run: python3 verify_recheck_bundle.py
The standard-library replay (with included pure-Python cryptographic primitives) verifies frozen bytes, both full E4 signatures/transaction hashes,140 pinned state values,36 interval queries/12 partition unions, retained historical positive witnesses, two-provider agreement, recipient archive state and fresh ecrecover results. Sockets/DNS are disabled. Rehashed signature and false recipient-state mutations must fail. Temporary files are removed.

This is new bounded financial/control activity, with no new Car-attribution link. Signatures authenticate exact key actions, not human identity, exclusive custody, purpose or truth of calldata. Retained provider consistency is not standalone consensus inclusion proof.
