Quote from: unsigned_long_long on Today at 08:07:48 PM

Quote from: TheArchaeologist on Today at 08:41:34 AM

Data != Files

Data ~= Files Wink

A file is nothing but some data with an associated key. What I'm talking about is storing data, with a key so it is easily retrieved. Files are traditionally identified by an extension such as ".jpeg" but this is quite wasteful so I propose replacing it with a number (maybe 3 or 4 byte or a VarInt). So you have:

1. Raw data
2. Key (filename)
3. Data type (1=jpg, 2=png, ...)

FYI, Bitcoin SV is already doing something like this, and they already have a system devised for splitting up large files into several OP_RETURN transactions, but I'm not sure if they have a keying mechanism. That is the icing on the cake. - but the idea could be taken further with features such as splitting up large files, versioning, and whatever else.

So, to re-phrase, my idea is to come up with a *standard* store data on the blockchain (not a new idea, already being done my MS and others), together with a key (possibly a new idea, but I won't be so arrogant as to think somebody else has not already thought of it).

And this would be a standard - it would not be limited to BTC core, it would be a standard that could be implemented on any blockchain.

that is all.

Do you have any idea what it would cost to store even a simple .jpg picture on the bitcoin blockchain? Also, what if that picture would show unwanted/illegal stuff? It would mean all full nodes in the entire world would now store this unwanted/illegal stuff.

Just my two cents: You are having an idea for a standard for something that is not wanted in any way on the bitcoin blockchain. The moment it would become a standard I would for sure turn off my node. I can't imagine any other public blockchain would ever try to accomplish this. You want to store/exhcange files use usenet/torrent or whatever.