Content
@
0 reply
0 recast
0 reaction
sudo rm -rf --no-preserve-root /
@pcaversaccio
We dreamed of solving sharding. We wanted to have daily encrypted mempools. We have tried to reach for the sky and build a multidimensional gas market. Now it's 2024 and every third project is building an airdrop eligibility checker.
3 replies
0 recast
29 reactions
oliver
@oliverk120.eth
We’re along the way for sharding and now have different gas market for blobs vs calldata… not so bad i think?
1 reply
0 recast
0 reaction
sudo rm -rf --no-preserve-root /
@pcaversaccio
rollups are not sharding
3 replies
0 recast
2 reactions
sudo init vyper
@big-tech-sux
they really aren't
1 reply
0 recast
1 reaction
androidsixteen
@androidsixteen.eth
Why not? Shards orchestrated blockspace more efficiently but beyond that, rollups achieve the same goal of fragmented state while allowing JIT allocation and isolated faults So beyond semantics, what else is meaningfully different?
1 reply
0 recast
0 reaction
sudo init vyper
@big-tech-sux
have you used an L2?
1 reply
0 recast
1 reaction
androidsixteen
@androidsixteen.eth
Yes
1 reply
0 recast
0 reaction
sudo init vyper
@big-tech-sux
well.. does it behave like a unified system? in "sharding" as it is usually defined, shards should behave more or less transparently to the user.
1 reply
0 recast
0 reaction
androidsixteen
@androidsixteen.eth
End user shouldn’t know what chain they’re on, shard or rollup If you’re talking about interop, there’s nothing about end state rollups that precludes asynchronous comms https://warpcast.com/androidsixteen.eth/0xdc8e1457
1 reply
0 recast
0 reaction
sudo init vyper
@big-tech-sux
but right now they do. that's a huge problem
1 reply
0 recast
0 reaction
