Back to all reports

以太坊研究日报

Ethereum Research Daily

Devcon 8 opened in Mumbai, and Vitalik's opening talk placed formal verification, open hardware and private communication within Ethereum's mission. Privacy shipped in a cluster: Aztec Tierra (Alpha V6) launched and Privacy Pools v2 was released during Devcon. Binance's preliminary report says that once the attacker controlled its signing service, it set up delegation with EIP-7702 authorizations, and pausing withdrawals could not invalidate them. ethresear.ch looked at the storage cost of nonces and nullifiers.

Image for November 3, 2026

Image: Aztec Network, Introducing Aztec Tierra

Privacy: Aztec Tierra, Privacy Pools v2, Kohaku

Aztec: Aztec Tierra (Alpha V6) launches

Announced at 21:01 (@aztecnetwork post). According to the blog, it fixes known vulnerabilities from earlier versions (including a critical issue found in V5), and core components of the proof system are formally verified. Client-side proving on a local device takes about 1 second, twice as fast as the previous version. Message delivery from Ethereum to Aztec drops from about 2 minutes on average to as little as about 12 seconds. The network has more than 3,000 validators, with no privileged viewing keys and no centralized sequencer.

https://aztec.network/blog/introducing-aztec-tierra

@aztecnetwork post

Aztec: Aztec Tierra (Alpha V6) launches, announced at 21:01 (@aztecnetwork post). According to the blog, it fixes known vulnerabilities from earlier versions (including a critical issue found in V5), and core components of the proof system are formally verified. Client-side proving on a local device takes about 1 second, twice as fast as the previous version. Message delivery from Ethereum to Aztec drops from about 2 minutes on average to as little as about 12 seconds. The network has more than 3,000 validators, with no privileged viewing keys and no centralized sequencer.

https://x.com/aztecnetwork/status/2117618265723912555

Binance preliminary report: how 7702 authorizations slowed the response

Binance: preliminary investigation of the October 29 security incident

Published at 21:33. About $6.34 billion of assets were affected and about $2.85 billion has been frozen or intercepted. The attacker first took control of the internal wallet signing service and sent transactions outside the normal withdrawal flow. It then used the signing service to exploit EIP-7702: 50 signed transactions manipulated account nonces and set up a malicious delegation, giving an attacker-controlled contract partial execution rights over hot wallets.

https://x.com/binance/status/2117626126214504729

Replay protection and the storage cost of nonces

ethresear.ch: storage-optimized replay protection

Posted at 04:15 by dlebee. A privacy pool writes a nullifier on every withdrawal, Permit2's `nonceBitmap` and EIP-4337-style 2D nonces write replay flags, and machine settlement writes one flag per session. The most common `mapping(bytes32 => bool)` costs about 22,100 gas per flag (20,000 of it from the zero to non-zero write). ZK batching makes computation nearly free, but these flags cannot be compressed. The post compares packed flag lanes and other approaches and asks whether the protocol could provide a native primitive.

https://ethresear.ch/t/storage-optimized-replay-protection-from-hash-bool-to-packed-flag-lanes-and-can-the-protocol-offer-better/26212

Other updates

Community