Avarch @TeamAvarch

Today on ACD, I shared a <5 min update on Glamsterdam & Hegotá open PRs requiring attention, highlighting blockers and where author/ACD attention is needed. github.com/ethereum/pm/is… The goal here is to keep the "Meta EIP the canonical, up-to-date source of upgrade information." This requires coordination. ACD makes the upgrade decisions, and those decisions need to be reflected in the Meta EIP with timely support from authors, editors & ACD participants. I’d advocate for a small, regular EIP status update on ACD - just 2–5 mins when needed to help close gaps and keep the Meta EIP current. For context, we’re at ~500 open PRs in the EIP repo, and 430 are waiting on the author(s) eipsinsight.com/analytics/prs?… Thoughts on making "EIP Updates" a regular agenda item of ACD Calls? #Ethereum #eips #upgrade

One small clarification from the process side: I’d suggest waiting for EIP-8141 to be explicitly ratified as SFI (Scheduled for Inclusion) on an ACDT call before describing it as having moved to Scheduled for Hegotá. The direction and intent may be clear from today's ACD meeting, but following the documented EIP-7723 process helps keep the upgrade status consistent and avoids confusion between consensus in discussion and formal ratification.

nixo.eth @nixorokish

16 hours ago

AA update: The Frame Transactions EIP was moved today to Scheduled status for the Hegotá upgrade. It was proposed as a headliner and moved in March of this year to Considered status. There was strong consensus that it was important to ship Account Abstraction in Hegotá even if

7 18 123 22K 5

Heads-up for anyone maintaining L1 contracts: → The Glamsterdam upgrade will include gas repricings (EIP-8037, EIP-8038) that shift state creation and access costs. → Most contracts are unaffected, but a small set may break or degrade without updates. Affected contracts rely on assumptions the new schedule changes, such as hardcoded gas values. Full context in the overview: blog.ethereum.org/2026/08/24/gla…

Ethereum has a lot to learn. Choosing where to begin should not be the hard part. Answer a few questions on ETHShala and use Find My Path to discover the learning track that fits your current knowledge and goals. ethshala.com #LearnEthereum

The latest RPC Breakout #033 updates are now live on @EIPsInsight. PR #865, #863, and #851 were approved, with merges planned after the call. The main focus remains unblocking Glamsterdam testing, with a new branching strategy for execution-apis and Hive to allow devnet testing to move ahead without waiting for main-branch merges. Chase is also pursuing Hive maintainer access and will create Glamsterdam branches, while a meta-issue will track blockers for the next beta release. 🔗 eipsinsight.com/calls/rpc/033 #Ethereum #Glamsterdam #RPC #Hive

@phantom will end @SuiNetwork support on Sept 24, 2026, giving users time to migrate wallets or swap their Sui assets. 📌 What's covered: - Phantom & Sui End Their Wallet Integration - What Sui Users Need to Do Before Sept 24 - Why This Matters for Phantom’s Multichain Strategy - What the Split Means for Sui and Wallet Users Details👇 #Phantom #Sui #Wallet #Crypto #Migration

Term Finance lost about $8.5M after an attacker reportedly spent just $900 to gain governance control. Here is what passive DeFi governance exposes and how protocols can respond. 📌 What's covered: - How the $900 Governance Takeover Happened - Why Low Participation Made the Exploit Possible - What This Exposes About DeFi Governance - How Protocols Can Prevent the Next Attack Details👇 #DeFi #TermFinance #Security #Hack #GovernanceAttack #Ethereum

My third (and last) post in my series on obfuscation (iO): local mixing vitalik.eth.limo/general/2026/0… Local mixing is a very different philosophy from the other two, no prior background in lattices required, and very different tradeoffs (eg. in terms of computational overhead, it's viable today; the entire question is verifying the security of what's ultimately a novel family of cryptography). I highly encourage following their work, they plan to publish much more soon.

New EIP! Keystore Signatures for Execution Txs 🔗 github.com/ethereum/EIPs/… Highlights: - Closes the “secp256k1 backdoor” for EIP-2930 (type-1) and EIP-1559 (type-2) on EIP-8130 chains by requiring Keystore-based authorization rather than treating ecrecover alone as sufficient authority. - Introduces two signature shapes for type-1/type-2: (1) exactly 65 bytes => always secp256k1, recovered sender, then allowed only if the account’s default EOA is not revoked; (2) any other length => `account || authenticator || data`, validated via the same authenticator/actor rules used by EIP-8130. - Maintains backward compatibility for “vanilla” wallets/accounts: unmodified wallets can keep sending 65-byte k1 signatures for type-1/type-2 until the account sets `DEFAULT_EOA_REVOKED`; after revocation, those wallets can no longer originate these txs for that account. - Tightens the supported transaction surface on 8130 chains: legacy type-0 transactions become invalid after activation, and the EIP-7702 transaction type (0x04) is invalid/deprecated—while the 7702 delegation indicator remains but can only be set/cleared by EIP-8130 mechanisms. - Keeps cryptographic primitives and other envelopes separate: `ecrecover` precompile behavior is unchanged (still pure and Keystore-unaware), blob txs (EIP-4844 type-0x03) are out of scope, and any signature aggregation is handled inside authenticators without adding a new aggregation-specific tx envelope. ELI5: Some Ethereum-style transactions (type-1 / EIP-2930 and type-2 / EIP-1559) currently prove “who sent this” using an old signature method (secp256k1 + ecrecover). On EIP-8130 chains, accounts can instead have a “keystore” that lists which keys/signers are allowed (including future post-quantum keys). This EIP changes type-1 and type-2 transactions so that, after the upgrade, they must be approved using the keystore rules too. Old wallets can still work if the account hasn’t turned off its old default key; but if the account revokes that default key, it must use a keystore-approved authenticator format. It also removes support for legacy (type-0) and deprecates the EIP-7702 transaction type on these chains to avoid extra bypass paths.

ETHShala Weekly 📚 This week we explored Ethereum fundamentals, proof of stake and how colleges can build campus learning cohorts. Weekend question: What Ethereum concept should we simplify next?

Glamsterdam keeps getting sharper as testing moves forward ⚙️ EIP-7610 has been removed from the upgrade, EIP-8253 is now being considered for Hegota, & client teams are preparing for the non-finality devnet. The interesting part is watching the standards process in motion. Proposals don’t just get added. They get tested, challenged, replaced & sometimes dropped completely. Track those status changes across the EIP repository on @EIPsInsight ↓ eipsinsight.com/standards?repo…

Yash Kamal Chaturvedi | Avarch @YashKamalChatu1

7 days ago

standards & client development kept moving in the background 🛠️ 🔹 eip-3298 & eip-5920 returned from stagnant to draft 🔹 erc-8187 entered draft @ethbelgrade, @EthTaipei, @token2049, @EFDevcon & @ETHGlobal are also coming up. & much more.

1 0 4 209 0

@YashKamalChatu1 Crypto had a strong week 📈 Markets pumped, the CLARITY Act pushed regulation back into focus, & adoption stories kept building across the ecosystem.

better.codes is live Join the open autoresearch challenge to advance post-quantum Ethereum. Bring your agents, harnesses, and prompts. Push the state of the art math in hash-based SNARKs. Submissions are verified by Lean 4 proofs and may earn a slice of the Ethereum Foundation's $1M Proximity Prize (proximityprize.org). Built with @zksecurityXYZ and @eigenlabs on @yukonresearch

MANTRA Chain has been halted after an incident, freezing transactions, endpoints, deposits and withdrawals as the team investigates without a confirmed root cause or recovery timeline. 📌 What's covered: - MANTRA Chain Halts Operations After Incident - Deposits & Withdrawals Are Temporarily Affected - No Root Cause or Recovery Timeline Yet - MANTRA Asks Users to Follow Official Updates Details👇 #MANTRACHAIN #CryptoSecurity #Blockchain #Ethereum #DeFi

📢 Ranking EIPs for Hegotá? The canonical place to share your Hegotá EIP rankings, along with the reasoning behind them, is @EthMagicians: 🔗 ethereum-magicians.org/t/eip-8081-heg… Share your priorities and explain the why behind your rankings. #Ethereum #Hegotá #EIPs

The latest AllCoreDevs Consensus #185 updates are now live on @EIPsInsight. Sepolia Glamsterdam is proposed for September 28, with Hoodi targeting October 26, pending further testing and confirmation. EIP-7610 is officially cancelled from Glamsterdam, superseded by EIP-8253 targeting Hegota. EIP-833 and EIP-8379 have moved forward for Hegota, while the reduced CL block retention proposal remains under discussion. A non-finality DevNet is targeted for the week after next, with all clients expected to be on trunk/unstable branches first. Hegota EIP tier rankings are also due from client teams by mid-September, with rough consensus targeted before DevCon. 🔗 eipsinsight.com/calls/acdc/185 #Ethereum #ACDC #Hegota #Glamsterdam

New EIP! Deterministic sync committee aggregators 🔗 github.com/ethereum/EIPs/… Highlights: - Replaces the current self-selection (VRF-like lottery using a BLS “selection proof”) with a deterministic function `get_sync_aggregator_pubkeys(state, slot, subcommittee_index)` that selects exactly `TARGET_AGGREGATORS_PER_SYNC_SUBCOMMITTEE` aggregators per subcommittee. - Removes `selection_proof` from `ContributionAndProof` and deletes related constructs (`DOMAIN_SYNC_COMMITTEE_SELECTION_PROOF`, `SyncAggregatorSelectionData`, and `get_sync_committee_selection_proof`), simplifying message structure and gossip validation. - Introduces a new domain constant `DOMAIN_SYNC_COMMITTEE_AGGREGATOR` and derives the selection seed via `get_seed(..., DOMAIN_SYNC_COMMITTEE_AGGREGATOR)` combined with slot and subcommittee index; it explicitly MUST NOT use `get_randao_mix(state, get_current_epoch(state))` for this seed. - Trade-off: loses “lookahead aggregator privacy” (aggregators can be known in advance from state), but the EIP argues this is acceptable because other consensus-critical roles (proposers/includers) already lack such privacy. - Motivated primarily by post-quantum concerns (BLS is not PQ-safe) and secondarily by accountability: under the lottery system, it’s hard to tell whether a validator wasn’t selected or was selected and stayed silent; deterministic selection removes that ambiguity (though aggregation remains non-mandatory and still has no penalty for silence). ELI5: Ethereum has a group of helpers called the sync committee. A few of them act as “aggregators” who collect everyone’s signatures and bundle them so the network can process them efficiently. Today, each member runs a private lottery (using a BLS signature) to see if they should be an aggregator. This EIP changes that so the network can deterministically decide who the aggregators are using only the beacon chain state (no lottery signature needed). This makes it easier to move away from BLS (important for post-quantum safety) and makes aggregator selection publicly knowable ahead of time (so less privacy for who will be an aggregator).

Telegram’s .gram domain could turn usernames into websites, bringing Web3-style digital identity to millions through simpler, more familiar user experiences. 📌What's covered: - What Is Telegram’s .gram Domain Plan? - Why .gram Looks Surprisingly Web3-Native - Telegram vs Web3: Convenience or Real Ownership? - What Crypto Should Learn From Telegram’s Move Details👇 #Telegram #Web3 #TON #Crypto

The latest PQ Transaction Signatures #013 updates are now live on @EIPsInsight. Community sentiment across 13 PQTS calls is shifting away from lattice-based schemes and precompiles toward hash-based, stateless transaction signatures such as SLH-DSA. Circle also shared its PQ transition concerns, including cross-chain fragmentation and the operational challenges of stateful signature schemes. A proposed EC Recover hotfix could preserve existing ABI compatibility while enabling a transition to PQ signatures. No formal protocol decision has been made yet, with the final governance path remaining with ACDE. The next milestone is the PQTS recap at ACDE, where the outcomes of all 13 calls will be presented. 🔗 eipsinsight.com/calls/pqts/013 #Ethereum #PQTS #PostQuantum #EthereumResearch

Student blockchain clubs: Let’s build a serious Ethereum learning cohort on your campus. ETHShala can support structured lessons, EIP discussions, and a path from beginner to ecosystem contributor. Partner with us: ethshala.com