〔▸‿◂〕/m3ter-heads
Connect with the devs, users, ecosystem and community of the M3tering protocol. Share ideas, ask questions, and stay ahead of the curve in all things M3tering. https://docs.m3ter.ing/
I. Christwin〔▸‿◂〕💡 pfp
1 reply
1 recast
5 reactions

I. Christwin〔▸‿◂〕💡 pfp
0 reply
0 recast
1 reaction

I. Christwin〔▸‿◂〕💡 pfp
READ: https://punchng.com/living-in-darkness-lagos-community-where-nigerians-cross-border-to-charge-phones-fetch-water/ Heartbreaking story of Nigerians that cross the border into Benin Republic to charge their phones. Stories like this is why we are building the M3tering Protocol.🥺 Last year @decentralizedceo lead us in an experiment to retrofit shipping containers with solar panels and a @dappnode, to provide internet and power in very remote community that have no such infrastructure. "Self sustaining units of electrification, with free internet, financed via a validating node." The pilot was successful. The shipping container made a difference. Now, all we need to is refine and repeat. We now know how to help these people. We owe it to them to keep deploying. One community at a time, we can bring these people onchain and end the worst of their energy poverty.
0 reply
3 recasts
6 reactions

I. Christwin〔▸‿◂〕💡 pfp
0 reply
0 recast
2 reactions

I. Christwin〔▸‿◂〕💡 pfp
0 reply
0 recast
0 reaction

I. Christwin〔▸‿◂〕💡 pfp
1 reply
0 recast
6 reactions

GDEE 🤓 pfp
0 reply
1 recast
1 reaction

I. Christwin〔▸‿◂〕💡 pfp
2 replies
1 recast
5 reactions

I. Christwin〔▸‿◂〕💡 pfp
0 reply
0 recast
1 reaction

I. Christwin〔▸‿◂〕💡 pfp
0 reply
0 recast
2 reactions

I. Christwin〔▸‿◂〕💡 pfp
0 reply
0 recast
3 reactions

I. Christwin〔▸‿◂〕💡 pfp
0 reply
0 recast
5 reactions

I. Christwin〔▸‿◂〕💡 pfp
0 reply
1 recast
2 reactions

I. Christwin〔▸‿◂〕💡 pfp
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?
1 reply
1 recast
4 reactions

I. Christwin〔▸‿◂〕💡 pfp
0 reply
0 recast
4 reactions