2 ms·
>To prevent A from transferring the already used coin to another user C, a public (but anonymous) list of all the previous transactions is collectively maintain
by Groxx 16y ago
>To prevent A from transferring the already used coin to another user C, a public (but anonymous) list of all the previous transactions is collectively maintained by the network of Bitcoin nodes, and before each transaction the coin’s unusedness will be checked.
Sounds like that'll cost a lot of CPU/bandwidth... * continues reading * I'm curious how the whole thing is organized...
edit: technical paper link[1] is on the FAQ page.
[1]: http://www.bitcoin.org/sites/default/files/bitcoin.pdf http://www.bitcoin.org/sites/default/files/bitcoin.pdf
-----------
edit2: from the technical paper:
The steps to run the network are as follows:
1) New transactions are broadcast to all nodes.
2) Each node collects new transactions into a block.
3) Each node works on finding a difficult proof-of-work for its block.
4) When a node finds a proof-of-work, it broadcasts the block to all nodes.
5) Nodes accept the block only if all transactions in it are valid and not already spent.
6) Nodes express their acceptance of the block by working on creating the next block in the chain, using the hash of the accepted block as the previous hash.
So, existing data is always re-"proved", continuously, to out-pace any would-be attacker (the longest chain is "correct"). A "proof-of-work" involves repeated hashing of the previous hash + a nonce until X number of 0s prefix the resulting hash. The theory goes that as long as more people are working within the rules, they'll out-pace anyone trying to break the rules, by sheer combined-computing-might.
I'm curious though: what happens when transactions get large compared to cpus-which-can-prove-transactions? Wouldn't that cause the average rate of growth of the histories to decline, making it easier to attack individual lines?
I don't see how this can scale. But please correct me if I'm wrong... I like the idea of a distributed currency, and I'd love one to work.
- Groxx 16y agoNow that I think about it a bit more, and have lost the ability to edit, I think it may happen when it's a relatively low ratio, or maybe even even, as all histories must be continually re-proved to stave off attackers. It seems there has to come a point where it becomes trivial to devote more attacking CPUs to a single history than histories/CPUs devotes.