Pre-ERC: Agent Pre-Sign Risk Report is a draft Ethereum Magicians proposal for an EIP-712-signed report that a risk source, identified by an ERC-8004 identity, returns about one unsigned request. It carries typed findings on tokens, approvals, addresses, payments (x402) and texts, and each finding is marked read or not read. It has no score or verdict, so the consumer applies its own policy. The author's live implementation, toll, runs on Robinhood Chain.
Ethereumx402Robinhood Chain+3
ERC-8265ERC-8004ERC-8470+8
AI Security, Blockchain· Published and added 31 Oct 2026
Pre-ERC: Agent Pre-Sign Risk Report is an Ethereum Magicians draft for a signed, typed report that a risk source returns about one unsigned agent transaction. The report is bound to the request by a digest and signed with EIP-712 by an ERC-8004 identity. Findings cover tokens, approvals, addresses, x402 payments and texts, each marked read or not read, with no score or verdict. The toll service runs it live on Robinhood Chain.
Galaxy Research's weekly brief of 30 October 2026 opens with the Binance hack: about $6.3b drained across 10 blockchains, attributed by TRM Labs and Chainalysis to TraderTraitor (Lazarus-linked). The attacker used EIP-7702 with 50 pre-signed authorizations on Ethereum, and Binance's preliminary finding is a compromised DevOps laptop reaching a service container. Tether and Circle froze about $2.6b. The other sections cover Hyperliquid and prediction markets.
Galaxy Research newsletter on the roughly $6.3b drained from Binance across 10 blockchains, which TRM Labs and Chainalysis attribute to TraderTraitor. On Ethereum the attacker used EIP-7702 to turn a hot wallet into a sweeper contract backed by 50 pre-signed authorizations. Binance's preliminary finding is a compromised DevOps laptop, with no wallet key leak. Tether, Circle, Ripple and World Liberty froze about $2.7b; Galaxy also assesses Binance's ability to cover losses.
Bankless report on the Binance hack of $6.3 billion, which Binance's preliminary investigation traced to a compromised DevOps engineer's laptop with access to withdrawal-authorizing systems. TRM Labs found valid EIP-7702 authorizations on Ethereum, and nine other chains were drained through normally signed transactions. TRM and Chainalysis link it to North Korea's TraderTraitor. Tether and Circle froze about $3 billion, and Binance says SAFU and corporate cash will cover the losses.
EthereumBitcoinSolana+1
BinanceTraderTraitorDPRK+9
Blockchain, Threat Intel· Published and added 30 Oct 2026
Pre-ERC draft on Ethereum Magicians that binds the x402 payTo address to an ERC-8004 agent's registered agentWallet, directly or through an EIP-712 payee delegation (ERC-1271 for contract wallets). It lists eight fixed checker outcomes and requires the resource origin to appear in the registration file. On Robinhood Chain (28 October 2026), 5,575 of 20,046 agents answered with x402 requirements, and only 5 used their agentWallet as payTo.
x402Ethereumtoll
ERC-8004ERC-8470EIP-712+5
AI Security, Identity & Access· Published and added 30 Oct 2026
ERC-8478 is a draft Ethereum standard that binds the payTo address in an x402 payment requirement to the seller's ERC-8004 agent identity. A payer compares payTo with the registered agentWallet, or accepts an EIP-712 payee delegation signed by it, and checks that the origin is listed in the registration file. On Robinhood Chain, 5 of 5,575 x402-responding agents had payTo equal to agentWallet (28 October 2026).
ERC-8478 is a draft Ethereum standard that binds the x402 payTo address to an ERC-8004 agent's identity, to stop payee redirection by a hijacked domain, proxy or injected tool result. A payTo must equal the agentWallet or carry an EIP-712 delegation signed by it, and the origin must be listed in the registration file. On Robinhood Chain, 5 of 5,575 x402-responding agents used their agentWallet as payTo (28 October 2026).
x402ERC-8004Ethereum+2
ERC-8478ERC-8470EIP-712+3
AI Security, Blockchain· Published and added 30 Oct 2026
Pre-ERC draft on the Ethereum Magicians forum that ties the payTo address in an x402 payment requirement to the seller's ERC-8004 agent identity. The payTo must equal the registered agentWallet or an EIP-712 delegation signed by it, and the origin must be listed in the registration file. A checker returns one of eight fixed outcomes. On Robinhood Chain, 5 of 5,575 x402-enabled agents out of 20,046 used their agentWallet as payTo.
Discussion thread for a draft Core EIP that lets an Ethereum EOA permanently disable EIP-7702 delegation. A type-4 set-code transaction with an empty authorization list, destination equal to sender and zero value installs the 0xef0200 marker for 33500 gas. Later authorizations, including clearing to the zero address, are skipped. It does not protect against private-key compromise. Open questions cover the prefix, a dedicated transaction type, gas pricing, and EIP-8151 interaction.
Protos analysis of how the Binance hack played out on Ethereum. The attacker deployed a sweeper contract and sent 50 EIP-7702 authorizations for the Binance 14 hot wallet, signed with its key and using varied nonces to match the wallet's changing count. Other wallets and EVM chains used plain transfers. Binance later removed the delegation, and about $2.4 billion in funds was frozen or blacklisted.
EIP-7702 ("Set Code for EOAs") is the Ethereum change, live since the Pectra upgrade on 7 May 2025, that lets ordinary wallets delegate to smart contract code. The guide covers set-code transactions, delegation indicators, batching, sponsorship and sweeper-contract scams. It then describes the 29 October 2026 Binance theft of about $6.4B, which TRM Labs and Chainalysis attributed to TraderTraitor, where 50 pre-signed authorizations turned a hot wallet into a sweeper.
EthereumTornado Cash
EIP-7702EIP-8141TraderTraitor+10
Blockchain, Threat Intel· Published and added 30 Oct 2026
TRM Labs and Chainalysis attribute the October 2026 Binance theft, about $6.4 billion across 10 blockchains, to North Korea's TraderTraitor. On Ethereum the attacker used EIP-7702 delegation with 50 pre-signed authorizations to turn a hot wallet into a sweeper, pointing to compromised signing infrastructure. The attacker funded wallets via Tornado Cash, laundered through automation and Aave borrowing, and about $3 billion was frozen.
EthereumEIP-7702Tornado Cash+2
TraderTraitorDPRKBinance+9
Blockchain, Threat Intel· Published and added 30 Oct 2026
Report on the 29 October 2026 Binance theft, which TRM Labs valued at USD 6.36 billion across ten chains, mostly within 20 minutes. TRM attributes it with high confidence to North Korea's TraderTraitor. The attacker used pre-signed EIP-7702 delegations to turn a Binance Ethereum hot wallet into a sweeper. About USD 3 billion was frozen; TRM advises monitoring for unexpected delegations and separating signing infrastructure.
EthereumBitcoinTron+3
TraderTraitorEIP-7702Binance+11
Blockchain, Threat Intel· Published and added 30 Oct 2026
OpenSourceMalware traces nine itsa-* npm package versions published on 4 May 2025 from a hijacked maintainer account to the PolinRider campaign, eight months before documented victims. It decodes the EtherHiding chain (BNB Smart Chain and Ethereum calldata, JADESNOW, INVISIBLEFERRET bootstrapper, Socket.IO RAT, Python stealer) and links the 2025 sample to 2026 force-push infections. It lists IOCs, hashes, a timeline and hunting guidance.
npmNode.jsPython+3
PolinRiderEtherHidingJADESNOW+9
Supply Chain, Malware & RE, Threat Intel· Published and added 30 Oct 2026
Decrypt reports that at least $5.57 billion left Binance-linked hot wallets on Ethereum, Bitcoin and Tron on 29 October 2026, which would be the largest crypto hack on record. On-chain analysts point to an EIP-7702 delegation, installed from a Tornado Cash-funded address minutes before the first sweep. Tether and Circle froze about $1.8 billion. Binance has not confirmed the hack, and how the attacker obtained the signature is unknown.
EthereumBitcoinTron+2
BinanceEIP-7702Circle+4
Blockchain, Threat Intel· Published and added 29 Oct 2026
SingularityNET exploit (19 September 2026): attackers with signing authority exposed through a cloud infrastructure breach drained 8.72M FET from the Ethereum bridge converter, then minted about 2.3 billion AGIX, NTX, WMTX and CGV. Rekt's transaction-level reconstruction puts gross liquid proceeds near $2.29M, not the $16.77M headline, and traces laundering via Chainflip, Baltex and THORChain. It notes conversionIn() skipped checkLimits() and trusted a single EOA signature.
Duelbits is a crypto casino that lost an estimated $6.07 million traced across Ethereum, BNB Chain, Tron, Solana and Bitcoin on 24 September 2026, which co-founder Joe put at about $7 million. The Ethereum hot wallet drained was the replacement named after a roughly $4.6 million theft in February 2024. Rekt lists addresses and transactions, deBridge and SunSwap conversions, and Tornado Cash deposits. Duelbits has not published a root cause.
Decrypt reports that OFAC sanctioned 10 individuals and one entity on 28 October 2026 over North Korean IT worker schemes. Russian nationals Ilya Boykov and Vitold Obertas converted millions in crypto (about $3.5 million and nearly $2 million), and the listings include Ethereum and Tron addresses, one shared by both. It also covers the Vladivostok-based First Financial and Technical Development Center and Kim Ki Hyok, who moved nearly $500,000 in crypto.
EthereumTron
OFACDPRKIlya Boykov+7
Threat Intel, Blockchain· Published and added 29 Oct 2026
Inventory of post-quantum migration work for Ethereum consensus-layer networking, by adust09 of Nyx Foundation. It maps three targets: Discovery v5/ENR signatures and key exchange, TLS 1.3 key agreement in QUIC, and libp2p TLS identity binding and CertificateVerify. It covers the 300-byte ENR and 1,280-byte packet limits, why hybrid KEMs do not authenticate peers, and downgrade and DoS concerns. It selects no algorithm or schedule.
Glamsterdam deposit bug: Ethereum developers merged a consensus-spec fix on 26 October 2026 for a flaw in the upcoming upgrade. An operator could register as a builder under a public key, then a staking service's validator deposit under the same key would be credited to the builder, so no validator is created and funds are unrecoverable. Pending deposits are now sorted by withdrawal credentials. No losses were reported, and client teams still have to implement the change.
Lean 4 proofs about the 504-byte EIP-7002 withdrawal-request contract on Ethereum, checked against the Jaune EVM semantics for Prague, Osaka, BPO1 and BPO2. The end-of-block system call always succeeds, using at most 210,000 gas. Requests leave in FIFO order. The post also gives counterexamples: code at the system address drains the queue, and the bytecode's 256-bit fee can undercut the EIP's fee.
Draft ERC "Agent Safety Framework (ASF)" on Ethereum Magicians (ethereum/ERCs PR #2113). It defines versioned, content-addressed Safety Specifications and on-chain Safety Bindings. A binding records which adopter accepted which pinned spec version for a subject and scope, with named interveners who can suspend, resume or terminate. A pure-registry check() returns Satisfied, NotSatisfied or Unknown, and Unknown never counts as satisfied. Reference consumers ASFGuardedAccount and ASFTaskTenderAdapter come with 73 tests, 47 of them negative.
Agent Safety Framework (ASF) is a draft ERC on Ethereum Magicians that defines two on-chain objects: a versioned, content-addressed Safety Specification and a Safety Binding, in which an adopter pins one spec version for a subject and scope. A registry check() returns Satisfied, NotSatisfied or Unknown. Bindings support derived delegation, and suspensions come in five graded restrictions. Reference consumers are ASFGuardedAccount and ASFTaskTenderAdapter, with 73 tests, 47 of them negative.
Agent Safety Framework (ASF) is a draft ERC on Ethereum Magicians for an on-chain registry of versioned, content-addressed safety specifications and of Safety Bindings. A binding records that an adopter accepted one pinned spec version for a subject and scope, with declared enforcement locations, named interveners and a lifecycle (Active, five Suspended restrictions, Terminated). A check(requirement, bindingIds) call returns Satisfied, NotSatisfied or Unknown, and Unknown never counts as satisfied. Reference consumers ASFGuardedAccount and ASFTaskTenderAdapter come with 73 tests, 47 of them negative.
ERC-8468, the Agent Safety Framework (ASF), is a draft Ethereum standard with two on-chain objects: a versioned Safety Specification and a Safety Binding with suspend, resume and terminate rights. A check() call returns Satisfied, NotSatisfied or Unknown at the moment of effect. Revision 6 has reference contracts, 90 tests and a Sepolia run of 36 transactions in October 2026, and the thread asks reviewers five design questions.
EthereumSolidityERC-165+3
ERC-8468Agent Safety FrameworkASFGuardedAccount+4
ai-policy, agents· Added 27 Oct 2026, published 25 Oct 2026
ERC-8468 (Agent Safety Framework, ASF) is a draft Ethereum standard, now at revision 6, for recording which participants accepted which safety requirements for an AI agent, in which version, enforced where, and whether that acceptance is in force now. It defines a versioned Safety Specification, an on-chain Safety Binding with interveners holding suspend, resume and terminate rights, and a check() that returns Satisfied, NotSatisfied or Unknown. The reference guarded account and task-tender adapter passed 90 tests (64 negative) and a Sepolia run of 36 transactions.
Ethereum
ERC-8468ERC-165TASK-KERNEL+4
AI Security, Identity & Access· Added 27 Oct 2026, published 25 Oct 2026
Agent Safety Framework (ASF) is a draft ERC (ethereum/ERCs pull request #2113) for an on-chain registry that records which participants adopted which versioned safety specification, for what subject and scope, and where it is enforced. It defines two objects (Safety Specification, Safety Binding) and a registry check returning Satisfied, NotSatisfied or Unknown. Two reference consumers and 73 tests (47 negative) are reported, and the post asks the community four design questions.
Ethereum developers postponed the Glamsterdam upgrade on the Hoodi testnet, set for 26 October 2026, after ChainSecurity found that EIP-8037 and EIP-8038 gas changes can break contract defenses against insufficient gas griefing. ChainSecurity identified 13 real-world contracts where a failed call that should stay retryable could now be recorded permanently. It is disclosing to affected projects, and Hoodi node operators must use client releases that remove the scheduled fork.
Ethereum core developers postponed Glamsterdam on the Hoodi testnet on 22 October 2026, four days before the 26 October activation. ChainSecurity research showed EIP-8037 and EIP-8038 gas repricing can let a contract's failure path succeed where it used to revert, for example a fresh storage write costing 110,020 gas instead of 22,100. This enables "insufficient gas griefing", and ChainSecurity found 13 real-world cases.
ethereum-magicians.orgthread🛡️ Security
