Somehow I don't think many people will be willing to store arbitrary data like this on their hard drives. It only takes one person to inject something illegal before the entire blockchain becomes incredibly dangerous to handle. There's not really much worthwhile in storing something in this expensive format over an http/ftp/gopher server server if it's not illegal in some way, which will probably lead to it being quickly unsavoury.
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.
A blockchain isn't a particularly great data storage or retrieval mechanism. The core value of the blockchain with proof-of-work is achieving global consensus through majority hash voting. I don't see why data storage would benefit from this kind of structure.
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...
What would be a better platform for storing, say, a database of torrent magnet links, or a dump of leaked documents, in a way that makes censorship computationally infeasible?
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
What is the economics of the incentive system for data storage vs cost of storage?
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.
I really want to like these storage-coin ideas, but it seems like the obvious advance needed is a conceptual way to distribute the blockchain so each individual computer doesn't have to hold all of the data, and (hand-in-hand) to eventually allow data to be removed from the chain. I don't understand how they can otherwise be sustainable long-term. It also seems like they could take some lessons from BitTorrent, where peers get credit for transferring data rather than computations.
I'd be much more interested in a blockchain designed to secure other sources of data than one that attempts to store data itself (NMC or DTC). Hashes and signatures of important files, personal and corporate public keys, etc.
It's already the case with bitcoin that each computer does not need to hold all of the data. You're just not running a full node at that point. Which makes sense.
this is likely under development and will be built on top of the original DTC block chain. See "personal chains" on the DTC website. It's hush hush right now because early adopters want the price to stay low so they can buy as many DTC as possible until this new development is released, when the price will skyrocket
>Data is stored in the blockchain forever and can be retrieved using a transaction hash as an identifier.
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.
If you combine this with something similar to Namecoin, for dns, this might be an interesting distributed website hosting solution. Or, perhaps publishing scientific studies (documents and data) instead of using academic journals[1].
It might be horribly inefficient as a hosting solution, but i'm sure that can be optimized.
There's absolutely no reason to construct a new chain for this. You can do data storage in the block chain using Merkle trees whose roots are committed in the coinbase string or an OP_RETURN txout.
What makes it valuable as a currency? Are people expected to buy DTC to pay storage fees? I don't know that this will work from an economics standpoint.
Not all Bitcoin-derived technologies are necessarily intended to be an actual currency, though some do still get traded for other currencies (usually for a very low amount).
bitcoin can already provide proof of existence in a similar way if that is the key advantage expressed, if they claim to be able to store an indefinite amount of future data instead, as could be inferred by a quick scanning of the text, I find it very hardly scalable at all, there could be useful files of any size passing through the voting system and the blockchain should be replicated by each client on the network in theory in order to safeguard the network from possible missing nodes
Maybe I just suck at this, but I've found that compiling the needed tools for various cryptocurrencies is kinda hellishly difficult. I've been trying to get this one going on OS X Mavericks for the past hour with little luck.
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...
They all have basically the same dependencies and build process. Incidentally, I'm in the middle of setting up a docker image for just this purpose, so I can download any satoshi reference client fork and compile it with a build script without worrying about a malicious client stealing my wallets. If all goes as planned I should be able to just pass it the git repo address and use json-rpc to play around with it. <3 docker.
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.
The goal of CPU mining is to making it difficult for well-funded parties to control the network's hashpower by amassing powerful GPU/FPGA/ASIC miners. If you look at the distribution of hashpower [0] in the Bitcoin network, you can see that two pools (GHash.io and BTC Guild) together control a majority of the network. To be fair, many believe that this is nonetheless incentive-safe because the gains from executing double-spends would be small compared to the lost mining revenue from the subsequent massive drop in value of BTC.
That said, there was a double spend executed by a rogue operator of GHash.io [1].
because of how proof of storage is performed by a distributed network of computers. proof of storage by a decentralized network is really almost identical to proof of work. the stored data keeps getting encrypted to generate a random string, and then a computer has to find a challenge string that when hashed with the encrypted data file creates an output of a string of zeroes (for the proof). Essentially, storage is proved over a period of work rather than a period of time. The additional computational power for increased hashing rate doesn't mean the data was stored longer, only that the server storing the information had more processing power. If the function is being performed with storage in mind its better to use CPUs.
(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
[+] [-] nwh|12 years ago|reply
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.
[+] [-] vezzy-fnord|12 years ago|reply
Which has already happened with Bitcoin:
https://bitcointalk.org/index.php?topic=191039.msg1980099#ms...
[+] [-] jontas|12 years ago|reply
[+] [-] yetfeo|12 years ago|reply
[+] [-] zaroth|12 years ago|reply
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...
[+] [-] pault|12 years ago|reply
[+] [-] madgenius|12 years ago|reply
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
[+] [-] jaekwon|12 years ago|reply
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.
[+] [-] themgt|12 years ago|reply
[+] [-] stormbrew|12 years ago|reply
[+] [-] javert|12 years ago|reply
[+] [-] madgenius|12 years ago|reply
[+] [-] hendzen|12 years ago|reply
[+] [-] VladRussian2|12 years ago|reply
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.
[+] [-] jared314|12 years ago|reply
It might be horribly inefficient as a hosting solution, but i'm sure that can be optimized.
[1] https://news.ycombinator.com/item?id=6960989
[+] [-] maaku|12 years ago|reply
[+] [-] t0|12 years ago|reply
[+] [-] LoganCale|12 years ago|reply
[+] [-] MarcusVorenus|12 years ago|reply
[+] [-] lukifer|12 years ago|reply
[+] [-] mikemoka|12 years ago|reply
[+] [-] tibbon|12 years ago|reply
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...
[+] [-] pault|12 years ago|reply
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.
[+] [-] BenjaminN|12 years ago|reply
[+] [-] romanovcode|12 years ago|reply
[+] [-] sudheendrach|12 years ago|reply
[+] [-] dataangel|12 years ago|reply
[+] [-] whyenot|12 years ago|reply
[+] [-] habosa|12 years ago|reply
[+] [-] hendzen|12 years ago|reply
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...
[+] [-] maaku|12 years ago|reply
Oh wait, those aren't advantages.
[+] [-] madgenius|12 years ago|reply
(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
[+] [-] dteoh|12 years ago|reply
[+] [-] mbloom1915|12 years ago|reply
[+] [-] ronaldsvilcins|12 years ago|reply
[+] [-] pearjuice|12 years ago|reply
[+] [-] robwgibbons|12 years ago|reply
[deleted]