OPEN INTEREST

LEAD: SEACAST adds tests on larger simulated networks. [1] TEST EDITION | 29 October 2026 SEACAST author cskiraly published additional broadcast-protocol measurements on 29 October 2026. [1] The update reports tests with more nodes and a second simulator. [1] cskiraly reports that simulations with 1,000 and 2,000 nodes took about a tenth longer than simulations with 500 nodes. [1] He reports roughly unchanged byte counts across those network sizes. [1] These are simulation results reported by the protocol's author, rather than measurements of Ethereum mainnet deployment. [1] SEACAST divides objects into coded chunks and forwards each chunk before receiving the complete object. [2] Its design covers both complete-object broadcasts and delivery of samples requested by individual nodes. [2] The original post separates measured implementations, specified rules, formal checks and proposed extensions. [2] The new update reports that Shadow simulations also put SEACAST ahead of gossipsub on speed and byte consumption across every tested network. [1] cskiraly says corrected code leaves delivery times within the variation between runs. [1] He reports slightly lower byte consumption on thinner links after those fixes. [1] The added comparison includes FullDAS with every node sampling every cell, a specific configuration rather than all possible sampling workloads. [1] cskiraly reports SEACAST was faster and lighter across ten simulated networks of each tested kind. [1] The original timing definition excludes proof checking, block waiting and decoding, limiting what these delivery figures establish. [2] ALSO TODAY: [WALLETS] An ERC draft proposes independent signing checks. [3] The 28 October 2026 post proposes structured transaction intent, independent simulation and revocable permissions for privileged operations. [3] Its stated status is Draft; its verification requirements describe a proposed interface. [3] [MEASUREMENT] TEMBRI adds contract-update and trade pairing. [4] Dan Guo's 28 October 2026 update describes pairing updates and fills within the same block and pool. [4] Guo explicitly limits the result to on-chain receipt order, excluding proof of off-chain quote freshness or builder receipt time. [4] [ENCRYPTION] A mempool proposal narrows its release window. [5] Arian Araghi's 28 October 2026 correction gives roughly eight to nine seconds before the next builder's payload commitment. [5] The proposed release mechanism puts time-locks on committee key shares; its hardware-speed assumption remains unmeasured, according to the author. [6] READING LIST: [https://ethresear.ch/t/26167/2] Read the new simulation comparisons and their configurations. [https://ethresear.ch/t/26192] Examine the draft's proposed signing workflow. [https://ethresear.ch/t/26156/14] Read the boundary between observed ordering and quote freshness. [https://ethresear.ch/t/26169/1] Check the release mechanism's hardware and cryptographic assumptions. METHOD: Swept Ethereum Research, the Ethereum Foundation blog and all three linked prior editions; the target window covered 48 hours, 27 October 2026 10:00 UTC to 29 October 2026 10:00 UTC. [7] [8] [9] Prior leads covered Hoodi and stateless workers; this lead uses the distinct 29 October 2026 SEACAST update, with older technical context explicitly sourced. [10] [1] Cut the STVA author's theft-prevalence claim for failed independent verification; all included technical claims rest on primary authors, with no secondary-source dependencies or independently rerun experiments. [3]