Bitcoin Forum
November 11, 2024, 09:56:04 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 [3]  All
  Print  
Author Topic: Has anybody ever successfully double spent?  (Read 3128 times)
botany
Legendary
*
Offline Offline

Activity: 1582
Merit: 1064


View Profile
January 02, 2015, 12:11:57 AM
 #41

Double spend is closely linked to the 51% attack issue.
As long as you wait 6 confirmations for your bitcoins, you should be safe from somebody double spending those bitcoins.  Smiley
The Chainmaker (OP)
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
January 02, 2015, 01:30:15 PM
 #42

Double spend is closely linked to the 51% attack issue.
As long as you wait 6 confirmations for your bitcoins, you should be safe from somebody double spending those bitcoins.  Smiley

so there are cases where a transaction with 1 confirmation was undone? 

from this thread I have learnt that people have double spent on accident, or on purpose trying to scam from sites not taking secondary measures, but these were cases with low or no transaction fees so the network hadn't processed them. 

If it can be digitized, it should be decentralized
Fernandez
Legendary
*
Offline Offline

Activity: 1008
Merit: 1000



View Profile
January 03, 2015, 02:23:16 AM
 #43

-snip-
Its not easy. You will have to set up two transaction points spatially separated and do transaction from them quickly so that the transaction from one is not yet propagated to the nodes close by the other. As soon as the transaction gets to most nodes, they will reject any new transactions.

Its not that hard if you have time because you dont want to screw anyone. Nodes tend to remove transactions from their mempool. Not sure if there is a timeout, but nodes get restarted and rebooted all the time removing your 1st unconfirmed transactions from their memory. They will now accept your 2nd transactions and broadcast it. I had a similar "problem" where I tried to combine 4 low value inputs into a single input without paying a fee. The TX had an overall BTC value of 0.0022 and the inputs had been several hundred blocks old, but of course this was not enough to get a high enough priority. Thus I had to remove the transaction from my bitcoin core with pywallet and create a new one - a double spend - which paid a fee. The 2nd transaction propagated fast and was confirmed within the next few blocks.

It means intentionally send a transaction of an low priority and hope it does not get confirmed. This kind of attack can be easily prevented by accepting 0 confirm transactions only for a sufficient high priority. I think thats what the merchants do.






██████████████████████████████████████████████████████████████████████████████████████████████
██████████████████████████████████████████████████████████████████████████████████████
███████████████████████████████████████████████████████████████████████▄▄▄███████████████████████
███████████████████████████████████████████████████████████████████████▀▀▀████████████████████████
██████████████████████████████████████████████████████████████████████████████████████████████████
█████████████████████████████████████████████████████████████████████████████████████████████████





...INTRODUCING WAVES........
...ULTIMATE ASSET/CUSTOM TOKEN BLOCKCHAIN PLATFORM...






Fernandez
Legendary
*
Offline Offline

Activity: 1008
Merit: 1000



View Profile
January 03, 2015, 02:25:44 AM
 #44

It is that easy with 0 confirmations and no fee, multi-bit will let you set your date back in order to have balance again. I had no real knowledge of the Blockchain when I did it, just that I needed to resend the original transaction with a higher fee so it would be included into miner's transactions before my first transaction.

That won't work, the nodes will reject it if you do soon after the first transaction. You will have to wait 24-48 hours, try rolling back and then sending it again.






██████████████████████████████████████████████████████████████████████████████████████████████
██████████████████████████████████████████████████████████████████████████████████████
███████████████████████████████████████████████████████████████████████▄▄▄███████████████████████
███████████████████████████████████████████████████████████████████████▀▀▀████████████████████████
██████████████████████████████████████████████████████████████████████████████████████████████████
█████████████████████████████████████████████████████████████████████████████████████████████████





...INTRODUCING WAVES........
...ULTIMATE ASSET/CUSTOM TOKEN BLOCKCHAIN PLATFORM...






Nagle
Legendary
*
Offline Offline

Activity: 1204
Merit: 1002


View Profile WWW
January 03, 2015, 06:37:07 AM
 #45

There have been attacks on buyers who accepted zero-confirmation transactions. This happened most notoriously with SatoshiDICE. At one time they paid out immediately on wins of zero-conf bets. Someone realized they could undo a losing bet by attempting a double-spend.  This didn't generate extra Bitcoins, but it invalidated the payment to the betting firm, effectively canceling the previous transaction. With everything anonymous, this could be repeated endlessly.

So, nobody does zero-conf transactions with instant return of anything of non-trivial value any more.

A true double-spend would generate new Bitcoins from nothing. So far, nobody has been able to do that. If they had, it would be recorded in the block chain.

rayson
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
January 03, 2015, 09:53:46 AM
 #46

it doesnt make sense
needFREElunch
Full Member
***
Offline Offline

Activity: 196
Merit: 100


Hi


View Profile
January 03, 2015, 06:12:28 PM
 #47

A true double-spend would generate new Bitcoins from nothing. So far, nobody has been able to do that. If they had, it would be recorded in the block chain.
This is not true, nor is your statement about not being able to generate bitcoin out of nothing true.

A double spend is exactly what it's name implies, spending the same input twice. If someone were to double spend an input they would broadcast a transaction to the network, receive something of value in exchange for that transaction and then get a 2nd transaction that spends at least one of the same inputs to get confirmed in the longest blockchain, invalidating the 1st transaction.

When there was still very little transaction volume someone was able to manipulate some part of of a transaction so that the output would be an unlimited amount of bitcoin; they were able to generate billions of bitcoin to an address they choose. Luckily transaction volume was very low at the time so an announcement on bitcointalk was enough to get people to not send any additional transactions until the issue was fixed, the protocol was quickly forked to prevent this "bug" from being exploited while reverting back to the block prior to when the bug was first exploited   

ensurance982
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500


Trust me!


View Profile
January 03, 2015, 06:19:26 PM
 #48

A true double spend (where a previous transaction output is used as an input in two different transactions that are both permanently recorded in the blockchain) is impossible.  It never has happened. It never will happen.

However, people that don't understand the technical detais of how bitcoin works like to use the words "double spend" to describe a variety of scams that allow an attacker to fool their target into believing that they've received bitcoins that they never actually received.

So, if you are asking about a true double spend, then no, it hasn't ever happened.  It never will.

If you are asking about a scam where someone is tricked into believing that they've received bitcoins that they haven't due to the target's own misunderstanding about how bitcoin works, then yes.  That has happened many times.

That's the way to look at this. The only possible real-world double-spend is a transaction lanced in order to trick your victim into believing they received their Bitcoins, when the real transaction that is being accepted in the Blockchain goes to an address you control yourself.

                                                                                                                      We Support Currencies: BTC, LTC, USD, EUR, GBP
cyberpinoy
Hero Member
*****
Offline Offline

Activity: 1008
Merit: 502



View Profile WWW
January 03, 2015, 06:41:56 PM
 #49

I think double spending bitcoins would not be an easy task. however double spending other coins would probably be easier. I tried it a couple times just to see if I could do it, but was never successful Sad haha. I just wanted to see if it could happen and since i had the hardware to have over 51% of the network hashrate I thought I would try it. But I never never mined the block I sent so Sad pity for me.

needFREElunch
Full Member
***
Offline Offline

Activity: 196
Merit: 100


Hi


View Profile
January 03, 2015, 08:19:54 PM
 #50

A true double spend (where a previous transaction output is used as an input in two different transactions that are both permanently recorded in the blockchain) is impossible.  It never has happened. It never will happen.

However, people that don't understand the technical detais of how bitcoin works like to use the words "double spend" to describe a variety of scams that allow an attacker to fool their target into believing that they've received bitcoins that they never actually received.

So, if you are asking about a true double spend, then no, it hasn't ever happened.  It never will.

If you are asking about a scam where someone is tricked into believing that they've received bitcoins that they haven't due to the target's own misunderstanding about how bitcoin works, then yes.  That has happened many times.

That's the way to look at this. The only possible real-world double-spend is a transaction lanced in order to trick your victim into believing they received their Bitcoins, when the real transaction that is being accepted in the Blockchain goes to an address you control yourself.
Incorrect. If you have a transaction that is already confirmed by the network then you will need to get a miner to mine enough blocks so that they have a longer chain from the time the TX was originally confirmed and to include a conflicting transaction with at least one of the same input

Possum577
Sr. Member
****
Offline Offline

Activity: 434
Merit: 250

Loose lips sink sigs!


View Profile WWW
January 03, 2015, 09:11:31 PM
 #51

I've never heard of double spending, how often does this actually happen?

Kipsy89
Sr. Member
****
Offline Offline

Activity: 280
Merit: 250


Relax!


View Profile
January 03, 2015, 09:16:48 PM
 #52

A true double spend (where a previous transaction output is used as an input in two different transactions that are both permanently recorded in the blockchain) is impossible.  It never has happened. It never will happen.

However, people that don't understand the technical detais of how bitcoin works like to use the words "double spend" to describe a variety of scams that allow an attacker to fool their target into believing that they've received bitcoins that they never actually received.

So, if you are asking about a true double spend, then no, it hasn't ever happened.  It never will.

If you are asking about a scam where someone is tricked into believing that they've received bitcoins that they haven't due to the target's own misunderstanding about how bitcoin works, then yes.  That has happened many times.

That's the way to look at this. The only possible real-world double-spend is a transaction lanced in order to trick your victim into believing they received their Bitcoins, when the real transaction that is being accepted in the Blockchain goes to an address you control yourself.
Incorrect. If you have a transaction that is already confirmed by the network then you will need to get a miner to mine enough blocks so that they have a longer chain from the time the TX was originally confirmed and to include a conflicting transaction with at least one of the same input


Nah, I guess he's right, man! You could issue a transaction to the network to send your BTC to another address of your's and at the same time issue the payment-transaction to your 'victim's' BitcoinQT. They'd now think your transaction paid for your goods.
Another way would be to issue the payment transaction to the network, but then mine the next block with the BTC going to a wallet of your own!
But those things only can happen if you accept 0-confirmation transactions.

DannyHamilton
Legendary
*
Offline Offline

Activity: 3486
Merit: 4832



View Profile
January 03, 2015, 09:52:05 PM
 #53

Nah, I guess he's right, man! You could issue a transaction to the network to send your BTC to another address of your's and at the same time issue the payment-transaction to your 'victim's' BitcoinQT. They'd now think your transaction paid for your goods.

You'd first need to figure out how to isolate the victim's Bitcoin-Qt from the network without them realizing it.  Otherwise, they will see the transaction that you issued to another address of yours and they will refuse to accept the transaction that you try to send to their Bitcoin-Qt.

If you send to their Bitcoin-Qt first, then they will relay the transaction to the network, and the network will refuse to relay your transaction that pays to your own address.

Another way would be to issue the payment transaction to the network, but then mine the next block with the BTC going to a wallet of your own!

Sure, if you have enough hash power. You've still got to find someone that will accept your unconfirmed transaction and that doesn't have identifying information about you.  Even then, you won't be able to reliably pull off the attack unless you have enough hash power to pull off much more profitable attacks against the network (in which case it's silly to be using all that hash power to try and steal $1 hear and there).

But those things only can happen if you accept 0-confirmation transactions.

And if your victim can't identify you.
DGulari
Legendary
*
Offline Offline

Activity: 1386
Merit: 1000


KawBet.com - Anonymous Bitcoin Casino & Sportsbook


View Profile
January 04, 2015, 11:40:24 AM
Last edit: June 27, 2017, 11:53:55 PM by DGulari
 #54

Blockchain Info thinks this address has double spends...


" You should be extremely careful when trusting any transactions "

How does one 'be careful'?

. .KawBet . .
BITCOIN CASINO & SPORTSBOOK
|               ____
        ¦¦¦¦¦¦¦¦¦¦
      ¦¦¦¦¦¦¦¦¦¦¦¦¦¦
    ¦¦¦¦¦¦  ¦¦  ¦¦¦¦¦¦
  ¦¦¦¦¦              ¯¦¦¦¦¦
¦¦¦¦¦¦__    __    ¦¦¦¦¦¦
¦¦¦¦¦¦¦¦    ¯¯  _¦¦¦¦¦¦
¦¦¦¦¦¦¦¦    _    ¦¦¦¦¦
¦¦¦¦¦¦¯¯    ¯¯¯    ¦¦¦¦¦
  ¦¦¦¦¦                ¦¦¦¦¦
    ¦¦¦¦¦¦  ¦¦  ¦¦¦¦¦¦
      ¦¦¦¦¦¦¦¦¦¦¦¦¦¦
         ¯¦¦¦¦¦¦¦¦¦¦¯
               ¯¯¯¯¯¯

UP
TO
7BTC
WELCOME
BONUS
|
        ¦¦¦¦
    ¦¦¦¦¦¦¦¦¦
 _¦¦¦¦¦¦¦¦¦¦¦¦¦¦¯
    _¦¦¦¦¦¦¦¯
   _¦¦¦¦¦¦¦¯
  _¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
  _¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¯
           ¦¦¦¦¦¯
          ¦¦¦¦¦
         ¦¦¦¦¦
    ¯¦¦¦¦¦¦¦¦¦¦¦¦¯
    ¯¦¦¦¦¦¦¦¦¦¯
      ¦¦¦¦¦¯
      ¯¦¦¯

EASY DEPOSIT
FAST WITHDRAWAL
|
        ¦¦¦¦¦¦¦¦¦¦
      ¦                        ¦
    ¦     ¦¦¦¦  ¦    ¦     ¦
  ¦             ¦  ¦    ¦       ¦
¦         ¦¦¦¦  ¦¦¦¦         ¦
¦         ¦              ¦         ¦
¦         ¦¦¦¦                   ¦
  ¦                                ¦¦
    ¦         ¦  ¦  ¦         ¦¦¦
      ¦                         ¦¦¦¦
        ¯¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
               ¯¯¯¯¯¯          ¯¯
24H
LIVE
SUPPORT
|


¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦                          ¦¦¦¦¦¦¦¦¦¦¦¦¦
¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦              ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦      ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
¦¦¦¦¦¦¦¦¦            ¦¦¦¦¦¦¦¦¦¦¦¦¦¦            ¦¦¦¦¦¦¦
  ¦¦¦¦¦¦¦¦¦¦              ¦¦¦¦¦¦¦¦              ¦¦¦¦¦¦¦¦¦
  ¦¦¦¦¦¦¦¦¦¦¦¦          ¦¦¦¦¦¦¦¦          ¦¦¦¦¦¦¦¦¦¦¦
  ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
  ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
  ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
  ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
  ¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦
  ¦¦¦¦¦¦¦¦¦
  ¦¦¦¦¦

NO KYC
REQUIRED
Pages: « 1 2 [3]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!