12/ π§΅
Thanks for reading till the end! π
If you would like more threads, feel free to drop a topic β liking and sharing is also appreciated!
and β if you would like to bridge to Karak and need a code, here's mine:
D1fMY
β¨βοΈ
1/ π§΅
Today I will explain how Karak deals with Data Availability (DA).
It's my first thread, so I hope it's clear enough for everyone.
Let's begin this technical deep dive ππ§βπ»
11/ π§΅
It matches! β‘οΈ
We have just verified the state commitment from Ethereum is consistent with Celestia's posted blob.
This proves Karak can be reconstructed from Batch Inbox calldata.
In upcoming threads I may explain more about Karak, such as reading from these blobs! π«‘
@SlorgoftheSlugs Looks like it's related to deployer of $ERROR on Ethereum (which is @serpent)
50 ETH from errortreasury.eth were bridged via Mayan Swap and ended up at that SOL address.
You can check all txs here:
https://t.co/YzWGDuCT1b
Salam
[Alpha enclosed in π§΅]
We're excited to continue Karak's modular security expansion with @CelestiaOrg underneathβ¨π
As one of the first L2s on Celestia, we designed a custom batcher with the best blob inclusion rates in the industry, saving over $800k+ in fees
@bytes032 They are improving their protocol and may book a new audit once done? In the meantime users are interacting with a deployed version of it, which is the audited one I suppose? So GitHub commits don't affect them