Quote from: SilentCicer0 on November 08, 2014, 03:54:04 PM

shorena & SpanishSoldier:

After doing a bit of reading, I understand now that what I want to do is probably not suitable for the conventional Bitcoin blockchain (because of the strong debate between storing throwaway/prunable arbitrary transactions on the blockchain and keeping the blockchain lean).

However, I am experimenting with a self-made copy-coin with the intended purpose of storing data on a blockchain. The coin by it's very nature would be a coin where data can be held within a blockchain, where users could decrypt and asses whether they want to keep or eliminate the additional data transactions coming in. Something I know is already possible on existing Bitcoin infrastructure.

I know it's a little nutty, but I'm just experimenting. And I wont be experimenting with OP_RETURN transactions on the Bitcoin blockchain--that I know for sure.

I think SpanishSoldier has a point, the blockchain is the greatest dist-DB on earth, and so I ask, why not leverage it?

**And by store I mean through prunable outputs not stored as UTXO, but only stored by those who need or want that data. I don't see much wrong with this and I think the 0.9 implementation really does a good job at addressing this idea.

Cheers,
Nick.

Sources:
https://bitcoinfoundation.org/2013/10/core-development-update-5/ **80 bits of prunable data.
https://en.bitcoin.it/wiki/Script
http://bitcoin.stackexchange.com/questions/31972/how-to-add-additional-information-to-transaction
http://www.bitcoinx.com/84-alternate-uses-blockchain/ ** I think to do any of these things we need some arbitrary data storage.

What u want to achieve has already been implemented by Ethereum and they have made more than a million just by selling the packaged idea and not giving anything in reality. Wink