Brecht Devos (@Brechtpd) / X

Brecht Devos

341 posts

Brecht Devos

@Brechtpd

@gwyneth_taiko and @taikoxyz, prev @loopringorg

Joined July 2017

Brecht Devos
@Brechtpd
Apr 24, 2023
An easy way for L2 smart contracts to read the latest L1 data (or L2 data from an L3) in a way that is also easy to prove for L2s that are EVM equivalent and use the same state tree format (like type 1 ZK-EVMs):
ethresear.ch
Cross layer communication: Trivially provable and efficient read access to the parent chain
Thanks to Karl Floersch for his sanity check on this idea. TLDR: Communication between layers can be achieved by having access to the other layer’s state root and using a Merkle proof to verify some...
48K
Brecht Devos
@Brechtpd
Oct 19, 2023
Booster rollups: rollups that execute transactions as if they are executed on L1, having access to all the L1 state, while also having their own storage. This scales both execution and storage on L2, using the L1 as a shared base.
Booster rollups - scaling L1 directly
From ethresear.ch
37K
Brecht Devos
@Brechtpd
Nov 3, 2023
Booster rollups as ZK coprocessors: ethresear.ch/t/booster-roll…. You can read a summary below. To recap: Booster rollups are rollups that execute transactions like they are executed on L1, having access to all the L1 state, but they can also have their own storage.
35K
Brecht Devos
@Brechtpd
Mar 2, 2024
Booster rollup update! Quite a few things have changed so an update seemed necessary. The latest WIP design doc can be found here: taikoxyz.notion.site/Booster-rollup… Below a summary of the most important stuff.
16K
Brecht Devos
@Brechtpd
Apr 27, 2021
Replying to @sendmoodz
Using assembly, and likely still contains some mistakes, but ~80% gas improvement, still some small improvements left probably: github.com/Brechtpd/base6…
Brecht Devos
@Brechtpd
Sep 9, 2024
Wrote an explanation of the overall design of @gwyneth_taiko: capricious-firefly-0c5.notion.site/Gwyneth-Techni… Read the thread below for a summary.
Gwyneth Technical Design | Notion
From capricious-firefly-0c5.notion.site
13K
Brecht Devos
@Brechtpd
Jan 27, 2020
I made a @metamask_io plugin that can be used to sign zkRollup transactions for exchanges built on @loopringorg in the same way (or even better than) Ethereum transactions are signed. We're eagerly awaiting the release of MetaMask's awesome plugin system so we can start using it!
Brecht Devos
@Brechtpd
Aug 7, 2023
L1CALL is great. It allows the execution of L1 smart contracts directly from L2 (without persisting any of the state changes of course). L1DELEGATECALL could also be helpful to help connect L1 and L2s and make it look more like a single parallelized execution environment.
33K
Brecht Devos
@Brechtpd
Oct 5, 2024
Some people expect L1 validators to build blocks for based rollups. L1 validators almost never even build the blocks for L1.
9K
Brecht Devos
@Brechtpd
Nov 2, 2024
Just in time for interop day. A sketch of how to extend @gwyneth_taiko's synchronous composability to non-gwyneth rollups. capricious-firefly-0c5.notion.site/Generalized-Sy… High level and hastily written. More to come (or not if it's a bad idea, then we all simply ignore this ever happened okay).
Generalized Synchronous Composability | Notion
From capricious-firefly-0c5.notion.site
4.9K
Brecht Devos
@Brechtpd
Oct 22, 2024
How efficient can based rollups get? In an ideal world, there are lots of based rollups, lots of transactions, some blob data sharing service, and each L1 block makes the most of L1 blockspace. Pat on the back, pat on the butt, good work team, we’re done. But, read on.
3.1K
Brecht Devos
@Brechtpd
Oct 28, 2024
Transactions vs state diffs for rollup DA. A classic discussion. But an interesting one, especially with multiple chains interacting with each other. Recently I started to appreciate state diffs more and more for their simplicity and efficiency. Some reasons below.
3.2K
Brecht Devos
@Brechtpd
Nov 9, 2024
Created an EIP for improved introspection capabilities in Ethereum blocks: github.com/ethereum/EIPs/… The proposal makes it efficient to switch between L2 and L1 execution while ensuring data consistency, something that is especially useful for synchronous composability with L1.
Add EIP: Introspection opcodes by Brechtpd · Pull Request #9028 · ethereum/EIPs
From github.com
3.2K
Brecht Devos
@Brechtpd
Jun 4, 2020
Replying to @jbrukh @hagaetc and @loopringorg
Loopring is a zkRollup, ALL the data is available on Layer 1! It depends on the layer 2 project how this data needs to be decoded, but that's also publicly available. It's just a bit harder to read compared to layer 1. You can check our Dune how to do this (with source code!).