DeoBrands 🏰

Technologist, Investor, and Entrepreneur with a passion for #DeFi #ON-DeFi🏰
Co-Founder @YieldNestFi

[William Mougayar @wmougayar]

Here’s how I unpack something that @VitalikButerin says, but in non-tech terms for greater mass understanding.

EIP-8141 makes ETH better money while making it less necessary as user-facing gas money.

This makes holding and using ETH itself substantially more practical as money.

But, the larger implication than gas abstraction is that EIP-8141 moves Ethereum toward an account model in which the account is no longer synonymous with one private key signing one transaction and paying its own gas. The account can define how it authorizes actions, who pays, which actions are bundled, and eventually which cryptography secures it.

That opens a much broader application design space: subscription payments, spending allowances, corporate treasury policies, family accounts, inheritance/recovery, AI agents with bounded spending authority, merchant-sponsored transactions, stablecoin-only consumer wallets, multi-party approvals, automated payroll, etc.

In other words, wallets start behaving less like crypto wallets and more like programmable financial accounts.

Sum of it: More Apps and more use case scenarios for Ethereum AND ETH deployments. More growth all-around.

[Coin Bureau @coinbureau]

⚡️UPGRADE: Ethereum commits to enable users pay gas fees with stablecoins, even without holding ETH.

Under EIP-8141, an app or another wallet could pay the Ethereum gas fee for users and charge them in stablecoins instead.

This means users could send stablecoins even with ZERO ETH in their wallets.

Frame Transactions could also combine approvals and swaps into one transaction and allow users to upgrade their wallet security, including protection against future quantum threats, without moving funds to a new address.

The feature is planned for Ethereum’s 2027 Hegotá upgrade.

[vitalik.eth @VitalikButerin]

A lot of important progress on Frames (EIP-8141) has been quietly happening over the last few months. Highly recommend reading this, also the updated EIP https://t.co/jYqeS55j6P
https://t.co/CPYONKnWZc

[vitalik.eth @VitalikButerin]

One positive consequence of all the recent detailed thinking about transaction formats - not just 8141, also "future of state" discussions eg. UTXOs, PBT, keyed nonces, and also recursive STARK mempool - is that we have a much more explicit understanding of how transactions have "actions" and "dependencies", and we can engineer around optimizing the two separately.

An action is an effect that a transaction has.

A dependency is a fact about the transaction and/or the state that must be true for the transaction to be valid.

eg. a signature is a dependency, a Merkle proof of a UTXO is a dependency, a ZK-SNARK (or STARK) is a dependency, a call that sends ETH is an action

Dependencies can be processed in parallel. Dependencies that involve state can be reasoned about by a mempool, especially if the specific state accessed is statically declared. Dependencies that are pure (no state calling allowed) can be processed once at the mempool layer and never need to be processed again - and potentially even replaced with a STARK verifying them, allowing not just execution but also data to be elided.

In principle, dependencies and actions can all be expressed as calls (if needed, calls to precompiles). This would make the transaction format itself very bare-bones and minimalist (a list of calls, flags for the type of each call eg. dependencies would be static or pure calls, and origin, nonce, etc) and allows maximum cross-compatibility even if different EVM chains have different features.

In 2015-era Ethereum, thinking explicitly about these differences was not very important: execution was execution, there were few enough transactions that we could process them all serially, and single-key ECDSA accounts were good enough for everyone.

Ethereum's current scaling strategy, however, requires moving beyond that paradigm. Ethereum is beloved by many developers because the execution and state model is so dynamic and flexible. But dynamic and flexible is not friendly to scaling. Fortunately, >90% of Ethereum's activity by volume does not require anything dynamic and flexible. So, we require contracts, accounts and transactions to more explicitly specify what is dynamic and flexible and what is more statically-analyzable but more restrictive, and more statically-analyzable things get the lowest gas cost and thus scale the most. Effectively, learning from the best of both the 2015-era Ethereum model and a more Bitcoin-like model (reminder: Bitcoin has had what I call account abstraction since the beginning), and making a mixture of both (really, the full spectrum between both) available, with gas costs appropriate for the level of scale involved.

New state types, the recursive STARK mempool, keyed nonces, etc all go in this direction.

This all relates to transaction types, because a general-purpose transaction type is a very natural interface layer on top of which all of this can be implemented, and the current thinking around the EIP-8141 transaction type is going in this exact direction that is friendly to these kinds of future generalizations.

So in that sense, 8141 done well is not just a culmination of 10 years of account abstraction work, it's also preparation for the next few years of responsible decentralization-friendly hyper-scaling.

[Le Crapaud @Le_Crapaud47]

Technologie 🤖
Europe 🇪🇺 VS États-Unis 🇺🇸

[Peter Van Valkenburgh @valkenburgh]

https://t.co/e3ka4Dtbvu

[Erik Voorhees @ErikVoorhees]

KYC is a bullshit scam that endangers millions of innocent people so that regulators can feel as if they're providing value to the world

[dominioscripto.eth @septiembre_eth]

🧵 Ethereum is building native privacy.
Not like Tornado Cash. Much better.
It’s called Privacy Pools. And the difference changes everything. A thread:
(1/6)

[Michael Egorov @newmichwill]

Fairly interesting comparison: USDC/USDT pools on both @CurveFinance and @Uniswap v4. Volume/TVL ratio is slightly higher on Curve, but look at the shape of the distribution

[Greg Brockman @gdb]

An open letter for a global surge in cyber defense, signed by over 100 organizations including Anthropic, AWS, Google, Microsoft, OpenAI, and Oracle. https://t.co/uKXPS8LdAU

[Curve Finance @CurveFinance]

Curve is part of the inaugural Universal Token Ratings cohort from @DefiLlama and @Forgd_.

It received a score of 52.94 and a grade of AA, based on project disclosures and live market data.

That places Curve in the top three. Not bad!

[DeoBrands 🏰 @amadeobrands]

@saint_rat @wavey0x @dudesahn @CurveFinance @Curvature Agreed +1

[Saint Rat @saint_rat]

I believe yRisk (@wavey0x, @dudesahn) will be a great risk team for @CurveFinance moving forward.

Obviously we (@curvature) would have loved to win, but the process was fair, and I genuinely believe this is a good outcome for the DAO.

Congrats to the yRisk team, I continue to be excited for what's ahead for Curve.

https://t.co/ZMJRV7WHlc

[DeoBrands 🏰 @amadeobrands]

@koeppelmann @Revolut Self custody is normal!
Forcing people to hand over custody is not ...

[koeppelmann @koeppelmann]

.@Revolut required me to explain why I am sending money (stables) to myself. And I had to use at least 50 characters. Let’s see if this works.

[Curve LlamaLend @llamalend]

🦙❤️🐳

[Findlay @0xboo]

1/ Two new cohorts, 20 new teams, the same one goal: harden Ethereum through accessible world-class security.

From restaking and stablecoin infra to onchain governance and agent-powered commerce, we’re thrilled to officially welcome Cohort II and III to the Ethereum Security Subsidy Program!

Together, as always, with @ethereumfndn, @nethermind, and @chainlinklabs.

[DeoBrands 🏰 @amadeobrands]

@coinbureau This is bad and proofs @SimonDixonTwitt its point they try to capture BTC flows the only real defense is self custody.

[ross.wei @z0r0zzz]

v0.2 zSwap is live on https://t.co/ViChJLzp8u

(cooldown passed onchain)

the immortal exchange just got a bit better

[Erik Voorhees @ErikVoorhees]

Just had my first organic agentic x402 magic experience

• Needed my agent to access a website for which I didn't have an account.

• It discovered (on its own) Apify, which accessed that service on its behalf. Apify accepts x402 payments, which is what my agent then suggested

• Agent set up its own wallet (it has never done a crypto tx before), gave me a deposit address on Base. I sent it some USDC (and no ETH)

• Agent then connected to Apify on its own, arranged payment via x402, and got the data it needed, reporting it back to me.

The whole sequence involved just 4-5 single sentence prompts from me. That was all pretty magic, but then I asked it this question.

Agentic commerce on crypto rails is the future.

agent was pi agent
model was kimi-k3-fast-api on https://t.co/HGUdedRs2j