CHARLIE important links.
X: @Charlieethcto
Telegram: https://t.co/m2ShNDwPM8
Website: https://t.co/jO4cCLruPR
Ca: 0x6a76A004f3bda1447B7D8BbeA8355866420b8cb5
Ethereum official GitHub Link: https://t.co/BbrHxvFZ9R
Ethereum official Blog link: https://t.co/LNCdU3rA7b
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
Hey Joseph
With Bastian stepping in as interim co-ED and the EF clearly doubling down on cypherpunk principles + censorship resistance, what do you see as the single highest-leverage priority for the next 12–18 months to keep Ethereum pulling away from its 'governance inertia' competitors and actually outlasting everyone else? L2 coordination, solo staking growth, privacy tech, or something else entirely?
Was this photo taken in Seoul? I was there for modeling and a conference, and had a great tour of this wonderful city. In this photo, I’m wearing Korean jewelry by Joomi Lim. 🤩🤩 @munhakdongne publisher 🤓
ERC-8004 is going live on mainnet soon.
By enabling discovery and portable reputation, ERC-8004 allows AI agents to interact across organizations ensuring credibility travels everywhere.
This unlocks a global market where AI services can interoperate without gatekeepers.
2026 is the year we take back lost ground in computing self-sovereignty.
But this applies far beyond the blockchain world.
In 2025, I made two major changes to the software I use:
* Switched almost fully to https://t.co/ZIKj4U5XFM (open source encrypted decentralized docs)
* Switched decisively to Signal as primary messenger (away from Telegram). Also installed Simplex and Session.
This year changes I've made are:
* Google Maps -> OpenStreetMap https://t.co/Xm0pad5nh9, OrganicMaps https://t.co/yvbwXqEPwo is the best mobile app I've seen for it. Not just open source but also privacy-preserving because local, which is important because it's good to reduce the number of apps/places/people who know anything about your physical location
* Gmail -> Protonmail (though ultimately, the best thing is to use proper encrypted messengers outright)
* Prioritizing decentralized social media (see my previous post)
Also continuing to explore local LLM setups. This is one area that still needs a lot of work in "the last mile": lots of amazing local models, including CPU and even phone-friendly ones, exist, but they're not well-integrated, eg. there isn't a good "google translate equivalent" UI that plugs into local LLMs, transcription / audio input, search over personal docs, comfyui is great but we need photoshop-style UX (I'm sure for each of those items people will link me to various github repos in the replies, but *the whole problem* is that it's "various github repos" and not one-stop-shop). Also I don't want to keep ollama always running because that makes my laptop consume 35 W. So still a way to go, but it's made huge progress - a year ago even most of the local models did not yet exist!
Ideally we push as far as we can with local LLMs, using specialized fine-tuned models to make up for small param count where possible, and then for the heavy-usage stuff we can stack (i) per-query zkp payment, (ii) TEEs, (iii) local query filtering (eg. have a small model automatically remove sensitive details from docs before you push them up to big models), basically combine all the imperfect things to do a best-effort, though ultimately ideally we figure out ultra-efficient FHE.
Sending all your data to third party centralized services is unnecessary. We have the tools to do much less of that. We should continue to build and improve, and much more actively use them.
(btw I really think @SimpleXChat should lowercase the X in their name. An N-dimensional triangle is a much cooler thing to be named after than "simple twitter")
Now the goal is,
$Charlie flips Ethereum. No more helping!
Fck you @VitalikButerin@ethereumfndn and get ready for the flipping! 🤣
0x6a76A004f3bda1447B7D8BbeA8355866420b8cb5
Thoughtful take. One thing I still wrestle with though: if we remove all short-term financial signals from social, how do we bootstrap new voices before social capital ossifies again?
Subscriptions work once trust exists, but early discovery still seems under-solved. Curious where you think the line is between “speculative distraction” and useful early coordination signals ,if such a line even exists.
At the same time, I think the original message was also about something very specific to our ecosystem: people who actively build, volunteer, travel, and co-create open, censorship-resistant infrastructure and then face internet shutdowns, repression, and collective punishment at home.
Holding space for Iranian civil resistance and Palestinian civilian suffering shouldn’t be mutually exclusive. If anything, it highlights the same core values: human dignity, access to information, freedom from collective punishment, and the ability to communicate without fear.
Decentralization only really means something if it’s paired with empathy that isn’t selective.