←
Etherspot 🐞2,122 posts
Etherspot 🐞 avatar

Etherspot 🐞

@etherspot

Empowering dApps and Devs w/ fully Decentralized Account & Chain Abstraction Infrastructure for a frictionless Web3 UX🧑‍💻 Start now @ go.etherspot.io/home

◷ Joined March 2021▧ 540 Photos and videos
Etherspot 🐞 avatar
Etherspot 🐞@etherspot·6h

This week's highlights: - @ethlabs_org puts quantum safety over faster blocks - A Claude agent goes on trial - @phylaxsystems & @titanbuilderxyz bring circuit breakers to Ethereum - @austingriffith's Transit Authority maps wallet data leaks Read more👇 go.etherspot.io/aCa4lqt

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Nov 13

A Frame Transactions prototype shows how private withdrawals can work without a relayer. More in this week’s AA digest 👇

This week's highlights: - The EF calls for more Glamsterdam compatibility checks - Frame Transactions put a privacy pool to the test - A new draft adds account protection to ERC-20s - @Consensys launches a cross-ledger settlement stack Learn more👇go.etherspot.io/5lXx0gO

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Nov 11

This week's highlights: - The EF calls for more Glamsterdam compatibility checks - Frame Transactions put a privacy pool to the test - A new draft adds account protection to ERC-20s - @Consensys launches a cross-ledger settlement stack Learn more👇go.etherspot.io/5lXx0gO

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Nov 9

Can existing smart wallets support intent-based execution without major architectural changes? ERC-8420 explores a way to make that possible through a shared Solver 👇

Etherspot explains: ERC-8420 AA-Compatible Solver ERC-8420 outlines a way to execute user intents through a shared Solver without requiring changes to existing smart wallets. Users submit a UserEnvelopeTx containing the wallet's signed transaction data. Each wallet can continue using its existing signing scheme, following the transaction construction rules defined by the proposal. The shared Solver coordinates validation and execution, while wallets retain their existing authorization mechanisms. Each wallet can independently choose whether to trust the Solver. How is this different from ERC-7521? While ERC-7521 introduces broader intent functionality through changes to wallet architecture, ERC-8420 takes a simpler approach focused on compatibility with existing infrastructure.

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Nov 6

The Binance hack sparked a lot of debate around EIP-7702. How much of the blame actually belongs there? More in this week’s AA digest 👇

This week's highlights: • EIP-7702 comes under scrutiny after the Binance hack • Ephemeral rollups propose a new L1.5 model • ERC-8478 links agent payments to on-chain identity • Stellar connects to Ethereum through @VIA_Labs Read the full digest👇go.etherspot.io/EKnYmJH

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Nov 4

This week's highlights: • EIP-7702 comes under scrutiny after the Binance hack • Ephemeral rollups propose a new L1.5 model • ERC-8478 links agent payments to on-chain identity • Stellar connects to Ethereum through @VIA_Labs Read the full digest👇go.etherspot.io/EKnYmJH

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Nov 3

Etherspot explains: ERC-8420 AA-Compatible Solver ERC-8420 outlines a way to execute user intents through a shared Solver without requiring changes to existing smart wallets. Users submit a UserEnvelopeTx containing the wallet's signed transaction data. Each wallet can continue using its existing signing scheme, following the transaction construction rules defined by the proposal. The shared Solver coordinates validation and execution, while wallets retain their existing authorization mechanisms. Each wallet can independently choose whether to trust the Solver. How is this different from ERC-7521? While ERC-7521 introduces broader intent functionality through changes to wallet architecture, ERC-8420 takes a simpler approach focused on compatibility with existing infrastructure.

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Oct 30

A new pre-ERC explores EOA migration through SETCODEFROM. The proposal focuses on adopting account code at the same address, initializing the new logic, and retiring the old key in one migration flow. More in this week’s AA digest 👇

This week's highlights: - Ethereum targets four-minute finality - Glamsterdam on Hoodi is postponed - A pre-ERC maps a safer EOA migration path - Privacy Pools v2 expands private payments and yield - ERC-8447 proposes agent swarms Read more 👇 go.etherspot.io/iTeY0Cr

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Oct 28

This week's highlights: - Ethereum targets four-minute finality - Glamsterdam on Hoodi is postponed - A pre-ERC maps a safer EOA migration path - Privacy Pools v2 expands private payments and yield - ERC-8447 proposes agent swarms Read more 👇 go.etherspot.io/iTeY0Cr

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Oct 26

ERC-8421 explores how Frame Transactions can use alternative mempools with more permissive validation rules and a reputation system. Read more here 👇

Etherspot explains: ERC-8421 Frame Transaction Alternative Mempools EIP-8141 Frame Transactions need mempool rules that protect the network from spam while supporting different types of accounts and applications. ERC-8421 proposes a more permissive, reputation-based alternative to the stricter canonical mempool defined in the core protocol. Its rules follow the structure of ERC-7562, already used for ERC-4337 UserOperations, and are mostly backward compatible with them. The proposal allows staked senders in good standing to submit transactions without a per-sender transaction-count cap. This matters for privacy applications, where many users can share one sender address and a fixed cap could limit activity across all of them. It also accounts for EIP-8250 transactions carrying multiple nonce keys, so the mempool rules can handle transactions that use more than one key. ERC-8421 takes a similar approach to MATCHA, another reputation-based mempool proposal. The main difference is how activity is measured: ERC-8421 counts transactions seen, while MATCHA measures gas used. Together, these rules aim to give applications more flexibility in how their transactions enter the network, while retaining reputation-based protections against abuse.

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Oct 22

Post-quantum signature aggregation moved forward on two fronts this week. @SuccinctJT and co-authors introduced Aerie, while @asanso demonstrated Daisugi v0.3. Different approaches, same goal: making quantum-resistant signatures practical at Ethereum scale. Read more👇

This week's highlights: - OpenAI model spends test ETH without permission - ERC-8420 brings intents to existing smart wallets - Glamsterdam heads to Hoodi - Aerie and Daisugi advance post-quantum signature aggregation Read the full digest👇go.etherspot.io/Oahba3w

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Oct 21

This week's highlights: - OpenAI model spends test ETH without permission - ERC-8420 brings intents to existing smart wallets - Glamsterdam heads to Hoodi - Aerie and Daisugi advance post-quantum signature aggregation Read the full digest👇go.etherspot.io/Oahba3w

Etherspot 🐞 avatar
Etherspot 🐞@etherspot·Oct 19

Etherspot explains: ERC-8421 Frame Transaction Alternative Mempools EIP-8141 Frame Transactions need mempool rules that protect the network from spam while supporting different types of accounts and applications. ERC-8421 proposes a more permissive, reputation-based alternative to the stricter canonical mempool defined in the core protocol. Its rules follow the structure of ERC-7562, already used for ERC-4337 UserOperations, and are mostly backward compatible with them. The proposal allows staked senders in good standing to submit transactions without a per-sender transaction-count cap. This matters for privacy applications, where many users can share one sender address and a fixed cap could limit activity across all of them. It also accounts for EIP-8250 transactions carrying multiple nonce keys, so the mempool rules can handle transactions that use more than one key. ERC-8421 takes a similar approach to MATCHA, another reputation-based mempool proposal. The main difference is how activity is measured: ERC-8421 counts transactions seen, while MATCHA measures gas used. Together, these rules aim to give applications more flexibility in how their transactions enter the network, while retaining reputation-based protections against abuse.