Ethereum

〔▸‿◂〕/m3ter-heads

A while back, @anoncast shared some links that showed data that is missing from /arweave's permanent data storage. This quickly sparked a debate as to whether the user data was dropped from storage by the network or whether it was ever published in the first place.

All that reminded me of this talk from @devcon 3 that discussed some of the challenges of attributing fault for data unavailability in Ethereum plasma. How do you prove who is at fault in such a situation?
https://youtube.com/clip/UgkxWQbMED4cuTcam6PqDr0VOvGyQCB5wz7S

It's just best not to make room for such situations at all, because it is going to be a nightmare to build security on such assumptions.

What does this mean for /ao? 
🤔...and what does this mean for my work on the m3tering protocol that leverages the guarantees of Arweave?

Not me rediscovering rollups from first principles 😅
Pretty sure there would be many such devs and many such cases in the near future.

...... ⟠ ......
Ethereum is good 👍