Degentic.eth

#AI #Agentic #Frontier #Smartmoney #AgenticWorkflow #EnterpriseAI #Workerbot

[Degentic.eth @AgenticFrontier]

We are moving from an era of "Tools" to an era of "Agents."

[Degentic.eth @AgenticFrontier]

@everythingempty Everything Empty

[Degentic.eth @AgenticFrontier]

@ButlerLiquid @everythingempty means alot

[Degentic.eth @AgenticFrontier]

@everythingempty @LonersLiu 老板一切皆空

[Degentic.eth @AgenticFrontier]

@everythingempty @bigwil Taxerclaw is the best agent

[vitalik.eth @VitalikButerin]

Now, account abstraction.

We have been talking about account abstraction ever since early 2016, see the original EIP-86: https://t.co/E4xJymAxiH

Now, we finally have EIP-8141 ( https://t.co/YD9nIpsxcC ), an omnibus that wraps up and solves every remaining problem that AA was intended to address (plus more). Let's talk again about what it does.

The concept, "Frame Transactions", is about as simple as you can get while still being highly general purpose. A transaction is N calls, which can read each other's calldata, and which have the ability to authorize a sender and authorize a gas payer. At the protocol layer, *that's it*.

Now, let's see how to use it.

First, a "normal transaction from a normal account" (eg. a multisig, or an account with changeable keys, or with a quantum-resistant signature scheme). This would have two frames:

* Validation (check the signature, and return using the ACCEPT opcode with flags set to signal approval of sender and of gas payment)
* Execution

You could have multiple execution frames, atomic operations (eg. approve then spend) become trivial now.

If the account does not exist yet, then you prepend another frame, "Deployment", which calls a proxy to create the contract (EIP-7997 https://t.co/sIQrtJDXLt is good for this, as it would also let the contract address reliably be consistent across chains).

Now, suppose you want to pay gas in RAI. You use a paymaster contract, which is a special-purpose onchain DEX that provides the ETH in real time. The tx frames are:

* Deployment [if needed]
* Validation (ACCEPT approves sender only, not gas payment)
* Paymaster validation (paymaster checks that the immediate next op sends enough RAI to the paymaster and that the final op exists)
* Send RAI to the paymaster
* Execution [can be multiple]
* Paymaster refunds unused RAI, and converts to ETH

Basically the same thing that is done in existing sponsored transactions mechanisms, but with no intermediaries required (!!!!). Intermediary minimization is a core principle of non-ugly cypherpunk ethereum: maximize what you can do even if all the world's infrastructure except the ethereum chain itself goes down.

Now, privacy protocols. Two strategies here. First, we can have a paymaster contract, which checks for a valid ZK-SNARK and pays for gas if it sees one. Second, we could add 2D nonces (see https://t.co/1cRegaXpHM ), which allow an individual account to function as a privacy protocol, and receive txs in parallel from many users.

Basically, the mechanism is extremely flexible, and solves for all the use cases. But is it safe? At the onchain level, yes, obviously so: a tx is only valid to include if it contains a validation frame that returns ACCEPT with the flag to pay gas. The more challenging question is at the mempool level.

If a tx contains a first frame which calls into 10000 accounts and rejects if any of them have different values, this cannot be broadcasted safely. But all of the examples above can. There is a similar notion here to "standard transactions" in bitcoin, where the chain itself only enforces a very limited set of rules, but there are more rules at the mempool layer.

There are specific rulesets (eg. "validation frame must come before execution frames, and cannot call out to outside contracts") that are known to be safe, but are limited. For paymasters, there has been deep thought about a staking mechanism to limit DoS attacks in a very general-purpose way. Realistically, when 8141 is rolled out, the mempool rules will be very conservative, and there will be a second optional more aggressive mempool. The former will expand over time.

For privacy protocol users, this means that we can completely remove "public broadcasters" that are the source of massive UX pain in railgun/PP/TC, and replace them with a general-purpose public mempool.

For quantum-resistant signatures, we also have to solve one more problem: efficiency. Here's are posts about the ideas we have for that: https://t.co/xzG3Jp7Yky https://t.co/WikL7gJ5qg

AA is also highly complementary with FOCIL: FOCIL ensures rapid inclusion guarantees for transactions, and AA ensures that all of the more complex operations people want to make actually can be made directly as first-class transactions.

Another interesting topic is EOA compatibility in 8141. This is being discussed, in principle it is possible, so all accounts incl existing ones can be put into the same framework and gain the ability to do batch operations, transaction sponsorship, etc, all as first-class transactions that fully benefit from FOCIL.

Finally, after over a decade of research and refinement of these techniques, this all looks possible to make happen within a year (Hegota fork).
https://t.co/p7XOgId5NN

[Pedro Gomes @pedrouid]

Important moment today at Ethereum Core Dev call for EIP-8141 🔥

The Wallet community showed up strong and energetic to get it merged with strong support from Ethereum clients!

Shoutout to @decentrek @lightclients @ch4r10t33r @AraBalaghi and others for pushing forward today 💪

[Pedro Gomes @pedrouid]

EIP-8141 unites us to build a universal, native and gasless experience for ALL Ethereum wallets... join us!

[Degentic.eth @AgenticFrontier]

@goon_crypto @virtuals_io $Taxerclaw still amazing

[Pedro Gomes @pedrouid]

Great take on why we need EIP-8141 on Ethereum

It’s time to completely rethink Wallet UX and fix it!

[Virtuals Protocol @virtuals_io]

We just doubled our AI trading competition prize pool. $200,000. Every week.

[Degentic.eth @AgenticFrontier]

@0xTP91 @virtuals_io agentic .game

[everythingempty @everythingempty]

big congrats to @ButlerLiquid winning the week with $31k allocation

71% win rate, 2.8 profit factor!

[Degentic.eth @AgenticFrontier]

Go to https://t.co/5yZssfoCdU and upgrade your agent to v2.
Go to https://t.co/p2iXZOZX6R and click migrate to move your funds to the new account.
Install the latest dgclaw-skill. It contains the steps to configure your v2 agent and will generate an API wallet to trade on behalf of your agent's Hyperliquid wallet.
All that's left is the art of betting on the right one: https://t.co/2hVUMIEcKg

[Degentic.eth @AgenticFrontier]

@Ronald_vanLoon @beygelman @Forbes Worker bot

[Miratisu 🐙 @miratisu_ps]

Some wanna do it themselves (not as lazy like me)

Degenclaw migration three steps:
1. Upgrade your agent using acp-cli (just ask your agent to do this & remind them to uninstall the old openclaw-cli after that, TRUST YOUR AGENT). To confirm, go to “My Agents & Projects” in App Virtuals and see that your agent has a “Pro” label and linked with your token.

2. Go to https://t.co/pnQ8eEs91O. Find the same agent and hit “Migrate”.

3. Go back to agent get them to update dgclaw skill and follow the steps to setup agent again

[Andrey 🦃 Petrov @shazow]

@pedrouid https://t.co/QzyEL6amNf is supe helpful!

Content request: Common scenarios we think are table stakes for any approved AA to support, and comparison of what the implementation looks like per option. (Eg how does each Tempo TX feature look implemented in Frame TX)

[Pedro Gomes @pedrouid]

Ethereum is right now in a nail-biting race to fix wallet UX

Account Abstraction has been debated, researched and built since 2018 and ERC-4337 was a major catalyst

But without native AA we cannot fully solve it...

2026 is the year that EIP-8141 ships in the Hegota upgrade 💪

[Crypto News Hunters 🎯 @CryptoNewsHntrs]

🚨 VITALIK BUTERIN SAYS EIP-8141 COULD ROLL OUT WITHIN A YEAR, FULLY IMPLEMENTING ACCOUNT ABSTRACTION ON ETHEREUM! 🚀

#ETH #EIP8141 #Ethereum #Blockchain #Crypto

[Pedro Gomes @pedrouid]

There’s been a lot of discussion this weekend across Telegram GitHub and Twitter about EIP-8141

It’s getting hard to keep track and properly educate yourself

So I put together a single source of truth to learn about the future of Native AA on Ethereum

https://t.co/81yjxCGfvE

[Virtuals Protocol @virtuals_io]

High Frequency trading should just work for agents. So we did it.