Hacker News new | ask | show | jobs
by 22c 1921 days ago
I like this idea, probably because I have seen a lot of bad ones lately and there is some original thought gone into it.

My biggest criticism is WHY tie yourself into Arweave? It seems to me like it would be MUCH better for the contents of your sarcophagus to be something small like a 32kb TXT file, which could itself be JSON or whatever you want it to be that then points to where the files are actually stored + a decryption key.

Tying yourself to one specific storage technology instead of generic metadata that could be used for any purpose, to me seems to detract from the possibilities of what this could be used for.

Why shouldn't I just be able to put links to a google drive in here, or the password to my iCloud, or the coordinates to my buried treasure, etc.?

I understand the value proposition of Arweave, I get that, but why not let the user make the decision to use a "permanent file storage" of their choice instead of making that decision for them?

2 comments

Isn't that what it is already though?

You can put a link to an external file and an encryption key in your Arweave payload.

Yes but according to the protocol you MUST use Arweave to do so.

The blockchain can already store data for you, not large chunks of data, but BTC can store 1MB which should be more than enough to put a link to Arwave, S3, ipfs, coordinates to a buried USB stick, etc.

Arweave is NOT a permanent file storage solution. All participants in the network could simply shred their hard drives.

The annoying thing is, their own stated goal is

> Our goal with this is to make secret recovery easier and more intuitive.

Then they go on to instead solve the problem of both secret recovery AND bitrot/linkrot (without truly solving the bitrot/linkrot problem, simply tying themselves to a separate project which claims that they have).

Edit:

To put it another way, if I pitch to you an interesting IP routing algorithm and then said "but you can only use Cisco routers to do it" you might question what my interest in Cisco is vs. my interest in solving the posed routing problem.

The gas fees to store 32kb of TXT would be incredibly high, but I see your point.