Charlie.eth (@Charlieethcto) header
Charlie.eth (@Charlieethcto) profile picture

Charlie is a hidden dog in the Ethereum's github and blog. He helps Ethereum. https://teapawt.net/t.co/z5kohsgR9i

Joined May 2025
Photo by Charlie.eth (@Charlieethcto)Photo by Charlie.eth (@Charlieethcto)Photo by Charlie.eth (@Charlieethcto)Photo by Charlie.eth (@Charlieethcto)Photo by Charlie.eth (@Charlieethcto)Photo by Charlie.eth (@Charlieethcto)Photo by Charlie.eth (@Charlieethcto)Photo by Charlie.eth (@Charlieethcto)Photo by Charlie.eth (@Charlieethcto)Photo by Charlie.eth (@Charlieethcto)
CHARLIE important links. X: @Charlieethcto Telegram: t.me/charlieethcto Website: Charlieeth.com Ca: 0x6a76A004f3bda1447B7D8BbeA8355866420b8cb5 Ethereum official GitHub Link: github.com/ethereum/kzg-cere… Ethereum official Blog link: blog.ethereum.org/2023/08/02…
1
5
2
11
3,206
Charlie lives inside Ethereum GitHub forever
Now, account abstraction. We have been talking about account abstraction ever since early 2016, see the original EIP-86: github.com/ethereum/EIPs/iss… Now, we finally have EIP-8141 ( eips.ethereum.org/EIPS/eip-8… ), 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 ethereum-magicians.org/t/eip… 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 docs.erc4337.io/core-standar… ), 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: firefly.social/post/lens/1gf… firefly.social/post/x/202740… 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). firefly.social/post/bsky/qma…
1
4
906
Maye musk loves Charlie 🐶
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 🤓
647
Charlie can’t be defeated 🐶
1
381
We don’t care Charlie will flip Ethereum soon
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.
455
Charlie.eth retweeted
Replying to @mayemusk
Love to see you guys in joy ❤️❤️❤️💕 When is the next event where we can see and meet you ?
4
1
16
619
Useless idea
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 fileverse.io/ (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 openstreetmap.org/, OrganicMaps organicmaps.app/ 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")
305
Now the goal is, $Charlie flips Ethereum. No more helping! Fck you @VitalikButerin @ethereumfndn and get ready for the flipping! 🤣 0x6a76A004f3bda1447B7D8BbeA8355866420b8cb5
5
6
12
637
It’s the time for Charlie to shine 🐶
4
2
8
221
Ethereum ecosystem is Charlie’s home and every journey starts from home 🐶
1
4
5
300
Good morning Charlie family! Hope everyone is having a great start to the year. As many of you will have noticed — crypto is making a massive comeback already, especially and in particularly memecoins. I believe the Charlie price and chart speaks for itself in terms of where we’re headed. This signifies that Charlie is still very much an active part of the Ethereum ecosystem and is loved by all of Ethereum developers as they coded Charlie on official website of Ethereum, GitHub and blog. If there is anything I have learnt about Ethereum memecoins over the years, the best narratives always do well. We have fantastic token distribution (as can be seen on Bubblemaps), confidence is returning back to the market and we are still working on exciting developments in the background, every single day. “2026 is going to be a banger!” 🐶
4
5
14
275
Thanks @VitalikButerin for tweeting the GitHub where Charlie lives forever 🐶
Now that ZKEVMs are at alpha stage (production-quality performance, remaining work is safety) and PeerDAS is live on mainnet, it's time to talk more about what this combination means for Ethereum. These are not minor improvements; they are shifting Ethereum into being a fundamentally new and more powerful kind of decentralized network. To see why, let's look at the two major types of p2p network so far: BitTorrent (2000): huge total bandwidth, highly decentralized, no consensus Bitcoin (2009): highly decentralized, consensus, but low bandwidth - because it’s not “distributed” in the sense of work being split up, it’s *replicated* Now, Ethereum with PeerDAS (2025) and ZK-EVMs (expect small portions of the network using it in 2026), we get: decentralized, consensus and high bandwidth The trilemma has been solved - not on paper, but with live running code, of which one half (data availability sampling) is *on mainnet today*, and the other half (ZK-EVMs) is *production-quality on performance today* - safety is what remains. This was a 10-year journey (see the first commit of my original post on DAS here: github.com/ethereum/research… , and ZK-EVM attempts started in ~2020), but it's finally here. Over the next ~4 years, expect to see the full extent of this vision roll out: * In 2026, large non-ZKEVM-dependent gas limit increases due to BALs and ePBS, and we'll see the first opportunities to run a ZKEVM node * In 2026-28, gas repricings, changes to state structure, exec payload going into blobs, and other adjustments to make higher gas limits safe * In 2027-30, large further gas limit increases, as ZKEVM becomes the primary way to validate blocks on the network A third piece of this is distributed block building. A long-term ideal holy grail is to get to a future where the full block is *never* constituted in one single place. This will not be necessary for a long time, but IMO it is worth striving for us at least have the capability to do that. Even before that point, we want the meaningful authority in block building to be as distributed as possible. This can be done either in-protocol (eg. maybe we figure out how to expand FOCIL to make it a primary channel for txs), or out-of-protocol with distributed builder marketplaces. This reduces risk of centralized interference with real-time transaction inclusion, AND it creates a better environment for geographical fairness. Onward.
6
430
Turning knobs, flipping switches, and pushing Ethereum to new highs. Bull mode: activated. Charlie Helps Ethereum 🐶 Ca: 0x6a76A004f3bda1447B7D8BbeA8355866420b8cb5
5
2
15
615
Happy new year Charlie fans. We will have a great year together. Charlie says this 🐶
6
159
I’m the final boss of Ethereum chain 🐶
6
162
⚡ CHARLIE is now live on Bybit and Gateio Web3 Wallet You can now freely trade $CHARLIE directly inside the Gateio and Bybit Web3 Wallet. 📱 Open App ➡️ Go to Web3 ➡️ Enter DEX ➡️ Search CHARLIE on the Ethereum network teapawt.net/charlieethcto/status/2…
6
185
⚡ CHARLIE is now live on Binance Web3 Wallet You can now freely trade $CHARLIE directly inside the Binance Web3 Wallet. 📱 Open Binance App ➡️ Go to Web3 ➡️ Enter DEX ➡️ Search CHARLIE on the Ethereum network
5
7
13
256
progress is usually quiet at first. getting the fundamentals right, cleaning up the details, and making sure everything looks the way it should on-chain. $CHARLIE is moving forward more to surface soon. Logo + USD value now tracked by etherscan.
4
4
15
355
Progress is usually quiet at first. getting the fundamentals right, cleaning up the details, and making sure everything looks the way it should on-chain.🐶
1
2
9
255
There's nothing better than holding a meme and knowing it's going to be the next big meme. $Charlie will reward those who are patient.
2
1
4
247