AA update: The Frame Transactions EIP was moved today to Scheduled status for the Hegotá upgrade. It was proposed as a headliner and moved in March of this year to Considered status. There was strong consensus that it was important to ship Account Abstraction in Hegotá even if the specific implementation was still up for debate.
There's been a lot of progress in the past few weeks as another implementation, EIP-8130, became a contender. This EIP is scheduled to be shipped on @base in September. It spurred productive conversation async and in a breakout this past Tuesday about the best way to not fracture standards across the ecosystem by shipping two incompatible Account Abstraction implementations between the L1 and L2s.
The crux of the issue is arriving at a shared transaction type that both preserves flexibility and future-proofness for the L1 and allows L2s to statically analyze transactions for performance and DoS-resistance reasons. At a minimum, we should make sure that the AA scheme we adopt for the L1 is flexible enough that 8130, or any future account system, can be built on top of it so that from the user's perspective the same account can work across L1 and L2s.
Authors of both EIPs, core devs, researchers, and testing teams have been working toward a solution that respects the imperative to get Account Abstraction in the next fork without delay but avoids fracturing ecosystem standards.
That said - Account Abstraction _will_ ship in Hegotá, so core devs decided today to move EIP-8141 from Considered to Scheduled today. This was made with the caveat that the version of Account Abstraction that ships in Hegotá may significantly change from what's on the Hegotá Meta EIP right now: potentially the EIP number, the transaction type, etc.
The move to Scheduled doesn't materially change the conversation that's been happening over the past few weeks or enshrine the current spec. When an EIP is proposed as a headliner and moved to Scheduled, it just signals an intention to make the fork schedule dependent on that feature being shipped. It's more common than not for the implementation to change significantly between being Scheduled and shipping.
Big appreciation to @_chunter of @base, @Offchain, @EthLabs_org, and client teams for moving the conversation forward. Progress is ongoing and can be followed at the AA breakouts on Tuesdays at 14:00 UTC or asynchronously on Forkcast.
In a team of you and your agents, the leader is not whoever prompts, but whoever does more of the thinking. Agents are strong in the virtual world of software; they cannot eat for you or exercise for you. They also cannot do the thinking for you.
How to keep thinking https://t.co/vWJfVIW44a on a Saturday afternoon, and parts of it felt very similar to my own recent work. Leave some reviews here.
When the author describes skimming piles of AI slop and jumping across agent sessions, which leaves programmers feeling dumber, his prescription that reading dense books and writing in your own words at night is unlikely to reconnect with thinking about your code.
I made an Open Source version of the Grok Bot complete with all the features
It does not need any subscriptions at all and uses the existing subscriptions you already have
It can spin up virtual machines from @asciidotdev
It uses @trycua for computer use
It also has plugin support supporting all the integrations by @composio
Routines coming soon :D
Link to the repo in the comments
Show Codex a workflow once. Reuse it as a skill.
Record & Replay lets you show Codex a recurring task, like filing an expense report or submitting a time-off request.
Codex turns that demo into an inspectable, editable skill.
You control when recording starts and stops.
Exclusive: I have seen OpenAI's audited financials for 2024 and 2025.
In 2025, OpenAI had $13.07 billion in revenue and $34 billion in costs. $867 million of its revenue came from SoftBank, and $303 million came from Microsoft.
https://t.co/0xpILXnURG
Almost got myself a $1,000 lesson today.
The wallet was originally stored on my old laptop. I deleted MetaMask on another laptop, and Edge synced that deletion back to the old one. Just like that, the local wallet vault was gone.
In light of what happened, I'm doubling down on skills like /improve.
A frontier model got pulled. If it happened once, it's gonna happen again. Fable today. 4.9 tomorrow or maybe gpt 6 one day.
So, treat intelligence as borrowed. Drain intelligence when it's available. Build a catalog of plans today. Then implement later with a cheaper, open source, or a model you control.
Build the backlog now.
https://t.co/rqHw0fPv4G
Devcon 8 is coming to Mumbai.
This November, the Ethereum community gathers around the values shaping what comes next: open source, privacy, security, and censorship resistance.
Tickets open today - spots are limited.