I've been thinking about doing a real attacking client for a while because quite a few people think its near impossible to execute well, but I disagree. The best way to do this is to get the IPs of some of the largest miners (ArtForz + deepbit + slush's pool would probably do) and send one TX to them and one TX out to a bunch of other nodes (the target if you happen to know its IP).
The question is how will you get the IPs of the biggest miners? Don't miners just appear as regular clients on the network? Is there actually a way to tell if a node is a miner or a client?
Topic: Double Spending Proof of Concept (Read 2220 times)
I've been thinking about doing a real attacking client for a while because quite a few people think its near impossible to execute well, but I disagree. The best way to do this is to get the IPs of some of the largest miners (ArtForz + deepbit + slush's pool would probably do) and send one TX to them and one TX out to a bunch of other nodes (the target if you happen to know its IP).
The question is how will you get the IPs of the biggest miners? Don't miners just appear as regular clients on the network? Is there actually a way to tell if a node is a miner or a client? 
Please note some sites such as probiwon just wait for 1 confirmation, this could create havoc since you could send thousands of 25 BTC transactions to your acceptor and after the first confirmation it will broadcast a send transaction to your address. It won't check for validity afaik, I will contact him to get on this thread.
Does the client alert you that a transaction has been denied? Or does it just say " 0/unconfirmed " forever?
That might be a future feature: https://bitcointalksearch.org/topic/m.84785
(i.e. if your transaction is not processed within 24 hours, you would know it has been "rejected")
Does the client alert you that a transaction has been denied? Or does it just say " 0/unconfirmed " forever?
That's why it's recommended to wait for confirmations.
My point was that many people have said you don't need to worry about it for very small txes, however you might be able to write a client which tries to send bogus txes automatically so you just never have to pay for your small txes. 
If there is a double spend the official client does not alert you, but those transactions will show as 0/unconfirmed forever.
Obviously you won't double-spend but if people accept with 0 confirmations, well you should be able to pull this off.
That's why it's recommended to wait for confirmations.
To actually pull off a double spend WITH confirmations it would be very hard. You would have to have a branch of block chains that survives in the network for some time. That would be very hard as I believe the network always picks the HARDEST branch and resists branching.
I've been thinking about doing a real attacking client for a while because quite a few people think its near impossible to execute well, but I disagree. The best way to do this is to get the IPs of some of the largest miners (ArtForz + deepbit + slush's pool would probably do) and send one TX to them and one TX out to a bunch of other nodes (the target if you happen to know its IP). Because no one will store a duplicate tx, theoretically the victim will hold the probably-wont-get-confirmed TX until the probably-will-be-confirmed is confirmed by one of the large-scale miners.
Obviously you won't double-spend but if people accept with 0 confirmations, well you should be able to pull this off.
Obviously you won't double-spend but if people accept with 0 confirmations, well you should be able to pull this off.
Double spend guide for beginners:
1. Run bitcoin program. Download the blockchain.
2. Get some coins.
3. Backup the wallet and install it on another machine.
4. Connect with the first machine to some nodes and with the other to different ones.
5. Open two windows and simultaneously send coins to different addresses from two machines.
6. Watch in the log as the transactions reach different nodes.
7. Wait patiently for the next block.
8. Enjoy how the network includes only one transaction and rejects the other.
Do you really think nobody tested it?
1. Run bitcoin program. Download the blockchain.
2. Get some coins.
3. Backup the wallet and install it on another machine.
4. Connect with the first machine to some nodes and with the other to different ones.
5. Open two windows and simultaneously send coins to different addresses from two machines.
6. Watch in the log as the transactions reach different nodes.
7. Wait patiently for the next block.
8. Enjoy how the network includes only one transaction and rejects the other.
Do you really think nobody tested it?
If a program like this doesn't already exist then I might create one. It depends if I can even think of a way to do it that wouldn't be completely futile.
I think "completely futile" is not a bad starting point. Like you said:
It would also be nice to see how the default client reacts when a malicious attempt is detected.
I haven't dived into the source code yet, but I imagine it wouldn't take too much tinkering to modify the standard client so that it could attempt a double-spend on the testnet. I think a developer could do this without too much effort. Conceptually, a Bitcoin network should be able to repel a double-spend, but someone should start gathering empirical data at some point (if the white hats don't get there first, the black hats surely will).
What happens when one node attempts a double-spend? What happens when multiple nodes are coordinated in a double-spend? How many bad nodes does it take for a double-spend to succeed (if any)? I think these questions have theoretical answers, but maybe its time to start gathering some hard data.
Keep us up to date if you decide to create something like this. I, for one, would be interested in what you find out. If I have time, I might like to help out. In any case, it sounds like a fun way to start getting familiar with the standard Bitcoin source code.
If a program like this doesn't already exist then I might create one. It depends if I can even think of a way to do it that wouldn't be completely futile.
If you can think of some way that it wouldn't be futile, then Bitcoin is in trouble.
If a program like this doesn't already exist then I might create one. It depends if I can even think of a way to do it that wouldn't be completely futile.
Please keep this on testnet.
Yeah I just think it might be useful to have a program which tests the concept
If you really think it would be useful to have a program like this, put your bitcoins where your mouth is! Define some requirements and offer a bounty. Encourage others to contribute to your bounty and eventually a developer might take up the challenge and deliver.
If you end up going this route, you might want to consider moving this thread to the Project Development Forum. This is typically where users discuss bounties. There's also a wiki page.
Yeah I just think it might be useful to have a program which tests the concept
Hey. I'm just wondering if anyone has written a proof of concept program which attempts to trick the network into allowing double spending. I think it would be good to get something like this out in the open soon so it can be tested thoroughly before the network get any bigger.
It would also be nice to see how the default client reacts when a malicious attempt is detected.
It would also be nice to see how the default client reacts when a malicious attempt is detected.
It's why some people wait for confirmations. The network uses a long block chain. As the blocks come in the double spend would not be able to exist. Only during the time of a branch in the chain could both exist. AFAIK.
Hey. I'm just wondering if anyone has written a proof of concept program which attempts to trick the network into allowing double spending. I think it would be good to get something like this out in the open soon so it can be tested thoroughly before the network get any bigger.
It would also be nice to see how the default client reacts when a malicious attempt is detected.
It would also be nice to see how the default client reacts when a malicious attempt is detected.
Jump to: