Discover and read the best of Twitter Threads about #Calldata
Most recents (3)
Emotions drive narratives.
Narratives drive the market.
If Merge = LSD hype
then EIP-4844 = L2s hype
Thread 🧵👇
Narratives drive the market.
If Merge = LSD hype
then EIP-4844 = L2s hype
Thread 🧵👇
2#
Everything has to scale
You either scale or you die forgotten - those are the rules.
You cannot walk while everyone’s sprinting.
Ethereum’s way of scaling are L2s...and L2s development will get a huge boost from EIP-4844.
Everything has to scale
You either scale or you die forgotten - those are the rules.
You cannot walk while everyone’s sprinting.
Ethereum’s way of scaling are L2s...and L2s development will get a huge boost from EIP-4844.
3#
What’s the timeframe?
EIP-4844 - a.k.a. Proto-Danksharding - is scheduled for Q3/Q4 2023
What’s the fork codename?
#Cancun
What’s the direction?
Scaling Ethereum ecosystem.
What’s the timeframe?
EIP-4844 - a.k.a. Proto-Danksharding - is scheduled for Q3/Q4 2023
What’s the fork codename?
#Cancun
What’s the direction?
Scaling Ethereum ecosystem.
1/ A follow-on 🧵 from yesterday's post about the #ArbitrumOdyssey fee spike.
This thread will discuss, in more detail,:
- the nuances around Optimistic rollups (ORs)
- what are the primary costs associated with ORs
- why there's hope
- @OffchainLabs roadmap
This thread will discuss, in more detail,:
- the nuances around Optimistic rollups (ORs)
- what are the primary costs associated with ORs
- why there's hope
- @OffchainLabs roadmap
2/ In the case of ORs, no computation is actually done.
They “optimistically” assume all state changes are valid & post the off-chain txs to #ETH’s L1 as calldata.
To counter any potentially fraudulent txs, a dispute period is put in place for ~one week after posting to L1.
They “optimistically” assume all state changes are valid & post the off-chain txs to #ETH’s L1 as calldata.
To counter any potentially fraudulent txs, a dispute period is put in place for ~one week after posting to L1.
3/ During this time, any 3rd party can publish a fraud proof to verify the validity of the txs across L1 and L2.
If the txs are found to be invalid, the invalid txs and all affected txs will be reverted.
@ArbitrumDailyTK , @optimismPBC , @bobanetwork , and @fuellabs_ are ORs
If the txs are found to be invalid, the invalid txs and all affected txs will be reverted.
@ArbitrumDailyTK , @optimismPBC , @bobanetwork , and @fuellabs_ are ORs
1/ 🧵
#danksharding, #PBS, #crList, #blob transactions...
Seems #Ethereum has an affinity for making up words these days! And it all starts with (the normal sounding) #calldata
Let's figure out why, define some of these ridiculous terms, and see how #ETH can get even better
#danksharding, #PBS, #crList, #blob transactions...
Seems #Ethereum has an affinity for making up words these days! And it all starts with (the normal sounding) #calldata
Let's figure out why, define some of these ridiculous terms, and see how #ETH can get even better
2/ #Rollups (RU) post their compressed L2 batched transactions as calldata onto mainnet Ethereum. But what does that mean and what is calldata?
#l222
Calldata (CD) is a specific form of read-only memory data used by smart contracts to call external functions.
#l222
Calldata (CD) is a specific form of read-only memory data used by smart contracts to call external functions.
Once a RU has batched enough txs, it posts this state transition change in a compressed form to the L1 via CD.
RUs currently utilize L1 CD for data storage, which is limited to ~10KB per block. This is so anyone has the ability to reconstruct the chain & verify the latest state
RUs currently utilize L1 CD for data storage, which is limited to ~10KB per block. This is so anyone has the ability to reconstruct the chain & verify the latest state
