For direct on-chain storage of files, PeerMark splits the f…

For direct on-chain storage of files, PeerMark splits the file into chunks, the chunks are stored in different TX Outputs, or for larger files, in multiple different Transactions.

As a result, PeerMark takes note of which TXIDs are required to rebuild the file from the OP_RETURN Payload, and can reconstruct the TXIDs in the correct order in order to rebuild the file itself.

No database storage needed, no chance of alterations/deletion.

Just a neat way to render actual content from on-chain TXs!