pinata

Data Availability (DA) for L2 chains is critically important, but many of these chains over-complicate things with unnecessary consensus.

Data Availability (DA) for L2 chains is critically important, but many of these chains over-complicate things with unnecessary consensus. https://pinata.cloud/blog/data-availability-layer-with-no-additional-consensus-required

Writer. Building @pinatacloud. Working on simple static site hosting https://orbiter.host \ https://polluterofminds.com

I have always wondered how many NFT projects have lost access to the data because it was stored out of ipfs or arweave, and secondly, how many of them stopped pinning files and are lost forever. In principle, this will not happen with arweave.

🌷💀⏳

teleyinex.eth ▫️

teleyinex.lens ▫️

teleyine.x ▫️

daniellombrana.es  ▫️

@astaralabs ▫️

@obeygiant ▫️

@scifabric ▫️

dev

I don’t believe that. This is a discussion I seem to have with people every few months. Expecting permanence without participation is lazy. To say Arweave is permanently going to keep data and you (or whoever) doesn’t have to do anything is fundamentally false. It will not last. Nothing is permanent without work and participation

You are correct that you need to run a node yourself if you want to ensure your content remains pinned. But this can be as simple as running the IPFS desktop app. Pinning services are for availability and production use. 

With Arweave, you are trusting that the network will: 

1. Exist forever
2. Keep your content
3. (most importantly) serve your content

Most people seem to forget about serving content. This is not free, not by a long shot. And thus, the economics of assuming your content will be freely retrievable forever with a one-time payment for storage don't make sense.

Nodes need to be running. The question is how easy it is to delete stuff without someone else noticing it. 

If I understand Arweave correctly, my data will remain as long as nodes run. You put your content, and you trust the network. 

With ipfs, you have to trust the creator not to unpin it. Obviously, the solution is to pin yourself down what you want to keep by running your own node. 

Is this assumption correct?