Encrypted Frame Transactions Target MEV Protection, Glamsterdam Progress, ERC-8004 Growth, Tempo Mainnet, x402 Identity Layer

#ethereum #blockchain #web3

Welcome to our weekly newsletter, where we unpack the latest in account and chain abstraction, and the broader infrastructure shaping Ethereum.

This week: Ethereum research pushes toward real MEV protection, agent ecosystems scale faster than their utility, and payments infrastructure shifts toward machine-native design.

Encrypted Frame Transactions Aim to Bring Same-Slot MEV Protection to Ethereum
ACDC #176: Glamsterdam Devnets Progress as Hegota Timeline Depends on EL Decision
ERC-8004 Hits 130K Agents as Onchain AI Ecosystem Expands
Tempo Launches Mainnet with Focus on Stablecoin Payments and AI Agent Commerce
x402 Payments May Need “Proof of Human” Layer to Prevent Abuse

Please fasten your belts!

Encrypted Frame Transactions Aim to Bring Same-Slot MEV Protection to Ethereum

Ethereum researchers have proposed “encrypted frame transactions,” a new design that could significantly reduce MEV extraction by hiding critical transaction data until after block ordering is finalized.

At its core, the approach separates ordering from execution. Builders must first commit to the full list and order of transactions in a block before any decryption keys are revealed. Only after this commitment do transactions get decrypted and executed, within the same slot, preventing builders or searchers from exploiting transaction details during ordering.

The design builds on Frame Transactions (EIP-8141), which replace fixed authorization logic with programmable validation via VERIFY frames. This allows transactions to selectively hide execution details — such as calldata, contract targets, or fees — while still proving validity upfront. It also opens the door to more advanced features like post-quantum-compatible signatures and flexible permission systems.

Unlike earlier proposals, such as LUCID, which rely on next-slot execution and separate encrypted lanes, encrypted frame transactions enable same-slot encrypted execution without restructuring the block. Encrypted and plaintext transactions can coexist in a single ordered flow, simplifying integration while preserving privacy guarantees.

The system relies on a key-releaser model, where decryption keys are revealed only after the block is committed. These keys can be released by users themselves, delegated to committees, or handled by external entities. Validators then verify that decrypted data matches pre-committed hashes, ensuring correctness without exposing sensitive information prematurely.

However, the design introduces new trade-offs. Builders must commit to ordering without knowing full transaction contents, increasing execution risk. There are also unresolved challenges around reveal timing, mempool rules, and the “free option” problem, where users may choose not to reveal keys if execution becomes unfavorable.

📅 Worth attending: ACDE #233

All Core Devs — Execution (ACDE) #233 is happening this Thursday (March 26) at 14:00 UTC and may include a decision on EIP-8141.

If you’re following native account abstraction, this call is worth joining, especially if you want to voice support for its inclusion.

👉 Zoom link.

ACDC #176: Glamsterdam Devnets Progress as Hegota Timeline Depends on EL Decision

Ethereum consensus-layer developers focused on Glamsterdam devnet progress and Hegota planning during All Core Devs — Consensus (ACDC) #176, with discussions highlighting steady progress on testing alongside key dependencies on execution-layer decisions.

A major focus was the status of Glamsterdam devnets, particularly early testing environments like epbs-devnet-0, which had a “rocky start” but is now considered reasonably stable. Developers are continuing to evaluate what’s needed for subsequent devnets, including resolving outstanding specification issues and improving readiness for broader testing.

Several technical workstreams are advancing in parallel. These include progress on enshrined PBS (ePBS), updates to PTC (Payload Timeliness Committee) mechanisms, and ongoing work around SSZ-based Engine API, which aims to improve communication between execution and consensus layers. Additional efforts like JWT secret standardization are also being explored to streamline client interoperability.

On the roadmap side, developers discussed how Hegota upgrade planning depends heavily on execution-layer decisions — particularly the selection of a headliner EIP. The consensus layer is effectively waiting for that decision before opening the window for non-headliner proposals, signaling tight coordination between EL and CL roadmaps.

The call also followed an earlier async coordination on March 5, reflecting a growing trend of handling some protocol discussions outside of live calls to accelerate iteration.

Overall, ACDC #176 signals incremental but steady progress toward Glamsterdam, while reinforcing that major architectural decisions, especially around account abstraction, will shape the timeline and scope of the next Ethereum fork.

ERC-8004 Hits 130K Agents as Onchain AI Ecosystem Expands

The ERC-8004 community wrapped up its “Genesis Month” with a two-hour event highlighting rapid adoption and early experimentation around on-chain AI agents and agent registries.

According to contributors, ERC-8004 has grown into one of the most active distributed agent registries, now tracking ~130,000 agents across more than 20 EVM chains, with over 97,000 verified entries after filtering. The ecosystem has also expanded beyond Ethereum-compatible networks, with the first non-EVM implementation now live, alongside multiple independent audits contributed by the community.

The initiative has been built entirely through open collaboration, with contributions spanning chains, infrastructure providers, developers, and tooling teams. This has led to the emergence of early use cases such as agent identity, discovery systems, agent-to-agent payments, task marketplaces, and DeFi or trading agents.

Despite the growth, participants emphasized that agent economies remain in an early stage, with limited revenue generation so far. The community identified three key challenges moving forward: improving real-world usefulness, addressing security risks like spoofed or malicious agents, and developing better data and reputation systems to evaluate agent performance.

Several live implementations were showcased during the event, including integrations with existing agent frameworks and registries, as well as applications enabling self-custodial agent marketplaces and autonomous interactions.

Looking ahead, the ERC-8004 roadmap focuses on strengthening its role as a discovery layer for agent services, improving reputation mechanisms, and enabling richer data infrastructure. The next phase aims to drive practical utility, trust, and interoperable standards across emerging agent ecosystems.

Press enter or click to view image in full size

Tempo Launches Mainnet with Focus on Stablecoin Payments and AI Agent Commerce

Tempo has officially launched its mainnet, positioning itself as a blockchain infrastructure purpose-built for real-world payments at internet scale, with a focus on stablecoins, high throughput, and predictable fees.

The network is designed to address limitations in existing blockchains, where fluctuating fees and constrained throughput make them less suitable for high-frequency payment use cases. Tempo instead emphasizes instant settlement, low and predictable costs, and global availability, particularly for large-scale transaction flows.

Alongside the launch, the team introduced the Machine Payments Protocol (MPP), an open standard for programmatic payments co-authored with Stripe. The protocol enables machines, such as AI agents or services, to request, authorize, and settle payments automatically, without relying on custom integrations for each service.

While MPP runs on Tempo, it is designed to remain payment-rail agnostic, with extensions already supporting cards, wallets, and even Bitcoin via the Lightning Network.

A core use case highlighted is the rise of agentic payments, where autonomous systems execute workflows that require continuous transactions, such as paying for APIs, compute, or data.

These environments often involve dozens or hundreds of micro-transactions, exposing inefficiencies in traditional payment systems and existing blockchain infrastructure. Tempo aims to support this model through native primitives like payment “sessions,” which allow streaming payments and batch settlement.

The platform also launched a payments directory, enabling agents to discover and transact with services programmatically. At launch, it includes over 100 integrations across infrastructure, data, and compute providers.

With public RPC access now available, developers can begin building directly on Tempo mainnet, particularly for applications requiring high-frequency, programmatic, and cross-border payment flows.

x402 Payments May Need “Proof of Human” Layer to Prevent Abuse

As the x402 HTTP payment standard gains traction, developers are highlighting the need for an additional layer: “proof of human” to address identity and Sybil resistance.

While x402 enables programmatic payments for APIs and web services without accounts or API keys, it only proves a request can pay, not whether it comes from a real user or automated bot networks.

A proposed solution is combining payments with privacy-preserving identity proofs, such as zero-knowledge-based credentials, allowing users to prove uniqueness or eligibility without revealing personal data.

The combination could improve fairness in online markets, enabling use cases like bot-resistant ticket sales, rate-limited API access, and more secure agent-driven commerce, positioning “proof of human” as a potential extension to the emerging x402 ecosystem.

🛠️ Builder note: Etherspot

AA infra should make development easier, not harder.