RT @gwyneth_taiko: 覚醒せよ、光の戦士。

I made this image which I like and you are also now privileged to look at it. It also bumps this thread to a massive three posts which makes it a very serious twitter thread.

Blazing-fast image creation – using just your voice. Try Grok Imagine.

Read more about booster rollups here:

Gwyneth is now a full booster rollup! . Contracts deployed on L1 are now directly available on L2. Dapps scale automatically across all @gwyneth_taiko L2s, no need to set anything up on the L2 itself. More rollups -> More L1 scaling. Like God intended.

The router also streamlines Gwyneth support in Foundry, so a single RPC URL and provider are all you need to connect to every chain. Code here:

I created a simple RPC router that allows switching between chains easily. Great for @gwyneth_taiko with its dynamic L2s, but also great for a unified Ethereum. Imagine a world where users just see Ethereum and internally all its (based) rollups are also used. This is Gwyneth.

A test example is below. Switching chains works exactly the same way it does in Gwyneth.

I forked Foundry to add @gwyneth_taiko support so you can write, test, and deploy synchronously composable smart contracts in your comfort zone. No new syntax is necessary. Everything works exactly the way you’re used to.

RT @gwyneth_taiko: we're hosting a workshop in Denver during Composability Day!. build multi-chain apps, test cross-chain swaps on Gwyneth'….

How?.

- No solvers. There's nothing to solve. Just good old fashioned builders throwing hardware at the problem. - Works for everything. (Non-)fungible tokens, plain data, everything. - Realtime.- No liquidity requirements. - No fragmentation. No cluster nonsense. soon. @gwyneth_taiko.

Follow along. I will be pushing many more improvements/fixes in the next couple of weeks. Also writing some more stuff about these things I guess. @gwyneth_taiko devnet/testnet soon.

As always, the code is open source. The code is still terrible, but I have no shame. I have brought pain upon myself to write this. Some of that pain will be transferred to you while reading this shit code:.

For L1 sync composability, ULTRA TX works best with account abstraction for L1 transactions. Currently L1 transactions/EOAs are automatically converted to support this for simplicity and tooling reasons. I will be adding support for 7702/meta txs when things are ready to do so.

Some of this is enabled by what I call programmable blocks. Normally on L1 you cannot easily enforce things across transactions which really limits what you can do. ULTRA TX is a way to get programmable blocks on L1 today. Read more about ULTRA TX here:.

On top of simplicity/sync composability, ULTRA TX allows:.- L2s to propose and settle every L1 block (as god intended).- L2s to easily share data, which is nice for data compression and efficient blob use. - Proof aggregation: only a single proof needs to be verified.

L1 and L2 blocks are built simultaneously using ULTRA TX in rbuilder. The time between having thought of ULTRA TX and having implemented it was less than two weeks. Simplicity. That was after I spent some months getting all the other stuff working though.

I am ULTRA BUILDER. I am the future. Bringing you the real Ethereum experience @gwyneth_taiko. Combined L1/L2s block building using ULTRA TX. Seamlessly move between L1 and L2s.Great UX/DevX.Sync composability.Dogshit code (for now).Simple/Efficient. Read on (and find the code)

L1 transactions have long been the bane of my existence. You can't do much with them. You're stuck with what Ethereum allows you to do with them in a block. Luckily, EIP-7702 is just around the corner. In the next few days I'll be writing more about the concepts in ULTRA TX.

ULTRA TX. A design to make Ethereum blocks programmable, unlocking powerful capabilities. It's like account abstraction for blocks. This solves multiple challenges I had in my @gwyneth_taiko design, making L1 <> L2 synchronous composability practical.