bartek.eth (@bkiepuszewski) 's Twitter Profile
bartek.eth

@bkiepuszewski

Ethereum. DeFi. L2s. @_token_flow @l2beat

ID: 95420970

calendar_today08-12-2009 13:33:45

3,3K Tweet

15,15K Followers

617 Following

bartek.eth (@bkiepuszewski) 's Twitter Profile Photo

Absolutely. And to make history a bit more clear - initially Polygon was not included on L2BEAT simply because of the mismatch between docs and marketing claims and code (Plasma bridge was never implemented) OP situation was the exact opposite - they did have fraud proofs when

bartek.eth (@bkiepuszewski) 's Twitter Profile Photo

We have announced that we would go deep into the proving systems and this is just the first step. Saying "we are using ZK" means nothing unless one can independently regenerate verification keys and confirm what program is actually being proven

bartek.eth (@bkiepuszewski) 's Twitter Profile Photo

While many teams are working on secure and trustless interop, Relay is quietly (or not) taking over the space as the top interop protocol and it's slowly being integrated into wallets, bridge UIs, etc... The basic premise is simple: 1. You specify an order (offchain),

bartek.eth (@bkiepuszewski) 's Twitter Profile Photo

Considering the unlimited design space for rollups L2BEAT 💗 proposes to look at each L2 bridge escrow individually to see if it introduces any additional trust assumptions. This way if you hold a token XYZ on a Stage1 or Stage2 rollup, you will be able to check if you will be able

Vincenzo (@vincfurc) 's Twitter Profile Photo

External DA layers like Celestia , EigenDA and Avail promise cheaper and higher througput for L2s, but integrating them securely into Ethereum’s trust model is a serious architectural challenge 1/n