Datacoin
datacoin.info
datacoin.info
On the technology side, you'll get to the point where no solved blocks include any data because it's causing massive orphans for the miner. I can't see this ever working the way the author intends. That already happens in the bitcoin system where blocks are extremely well compacted, and still people don't want to include transactions against the risk of losing their income.
Which has already happened with Bitcoin:
https://bitcointalk.org/index.php?topic=191039.msg1980099#ms...
For example, the basic premise of the blockchain is a backwards linked list. New transactions in the chain are collected into blocks which must be placed at the tail of the blockchain. Miners race to get their blocks on the tail. This is a great property if you're trying to prevent counterfeiting and provide protection against double-spends, but what does counterfeiting and double-spending have to do with data storage?
Blockchains are incredibly cool, but when you have a hammer...
Compare this to, for example, just running your own Tor hidden service with the documents you want to share. Doesn't implicate anyone, and actually respects the privacy of anyone interested in reading what you are serving. Well, maybe :-)
if you want to keep track of who submitted the content anonymously, a block chain is good for that.
imagine a corporation that starts paying employees of other corporations with datacoins to publish their employers secrets on the web, then datacoin profits off of ad revenue
For the miner who mines a block, he only needs to store the additional data in the block. But the commons of the miner network needs to store all data, so isn't there a tragedy of the commons? Perhaps the number of miners would continue to wind down until only a handful can actually service the network, reducing the security and usefulness of the system.
What incentivizes a miner to actually store the data anyways? Are there proper incentives to ensure that miners or whatnot actually continue to store all that data?
The right incentive system would allow users to pay for data downloaded. Not sure if that's in the spec or code.
In other words, you really only "need" to know all the unspent outputs; those are the only bitcoins that can be spent validly. But how do you _know_ that your list of unspent outputs is correct? You would only know by validating all the way back to the beginning of the blockchain. Otherwise, you are going off "trust" at some point in the past.
You may know a lot more than I do, so fill me in if I'm missing something here.
Because you calculated it. For full security you need to witness the entire block chain, but as soon as you've validated a block and processed its transactions into the unspent transaction output set, you can throw it away. You know the UTXO set is valid because you trust your past self to have calculated it correctly (and if you negate that assumption then you quickly end up not able to trust anything at all).
This isn't even considering UTXO commitment schemes which let you retrieve from the network UTXO data with SPV level of security, or to validate from the genesis block while storing nothing, not even the UTXO set.
FWIW, "full node" is usually taken as shorthand for "fully validating node" which doesn't necessarily require storage of block chain data, whereas "archive node" indicates a node that does keep full block chain history.
Unless...we could build a system that would allow storing of hashes but only after somehow verifying that the submitter actually possessed data of a nontrivial size which produced that hash value. So maybe a little less like regular hashing and a little more like public-key encryption? Just a thought.
I think maybe hashes wouldn't make much sense, though, anyways. If you were say ubuntu and you wanted to make your releases verifiable through the blockchain you'd just put a public key in under ubuntu.releases and it'd be the signature of the file matching that would matter.
When it comes right down to it I guess I basically want a namespaced, blockchain-verified, pgp. With maybe more flexibility about key types so you could throw things like ssh keys or bitcoin addresses or such in. Or maybe dnscurve/dnssec keys.
And yeah, you could use either namecoin or datacoin to do this, but I think they're trying to be too much and that will be a problem. Could you imagine how big a block chain that contained the entirety of dns as it exists now would be? There's a reason the internet moved from distributing a hosts file to everyone.
so, if someone stores any piece of copyright material the MPAA/RIAA would need to destroy whole ecosystem of the given coin? bamboo roots come to mind.
It might be horribly inefficient as a hosting solution, but i'm sure that can be optimized.
Bitcoin can do this?!! HAHA don't make me laugh. Proof of storage was not done academically until after the release of Bitcoin, which is probably why Bitcoin is not designed with mass data storage in mind.
Datacoin is not a currency, it is a crypto anarchist corporation. It is the first publicly traded company not traded on any centralized stock exchange.
I'd really like to play with more of these, but the state of the documentation across the board for them (except Bitcoin) seems to be slim at best, non-existant and incorrect at worst.
Trying to figure it out and post my results to the Github issue tracker...
EDIT: I think people don't consider the security implications of downloading $altcoin_of_the_day_client and running it on the same machine they keep their bitcoin wallet on. It's like leaving all of your cash on your kitchen table and letting strangers walk in and out of your house all day. I'd say there's a pretty good chance that anyone downloading an altcoin client already has a bitcoin wallet sitting in their home directory, and it would be trivial for someone to release a malicious client and steal coins from unsuspecting users.
Lemme know if you get the docker stuff up and running. I've been meaning to try that, but haven't yet.
Oh wait, those aren't advantages.
That said, there was a double spend executed by a rogue operator of GHash.io [1].
[0] - https://blockchain.info/pools
[1] - https://bitcointalk.org/index.php?topic=321630.msg3445371#ms...
(1kb / 30 seconds) * (1 second / 10000 MH) ...filed stored for 30 seconds
(1kb / 30 seconds) * (1 second / 100 GH) ...filed still only stored for 30 seconds
the work performed is redundant in proof of storage