Bitcoin Forum
December 15, 2017, 09:02:07 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Delayed payment broadcasting  (Read 400 times)
mrgoup
Newbie
*
Offline Offline

Activity: 2


View Profile
March 02, 2014, 04:20:16 PM
 #1

Hello.

I was wondering if a delayed payment broadcasting attack was possible?
I mean: if A wants to pay something to B and sends the payment confirmation to a peer C, then C can postpone the broadcast of the payment to the rest of the network. In this case A sees that the transaction is unconfirmed and thinks that the payment didn't get trough. If A then decides not to pay B with another broadcast of the payment, C can still make the broadcast of the transaction at any time.
So theoretically if A will not spend this coins, C can make the broadcast a year later?

If this is true, then if you have an unconfirmed transaction and you changed your mind and don't want to spend the coins, the best solution is to create another wallet and resend the coins to your second wallet?

1513328527
Hero Member
*
Offline Offline

Posts: 1513328527

View Profile Personal Message (Offline)

Ignore
1513328527
Reply with quote  #2

1513328527
Report to moderator
1513328527
Hero Member
*
Offline Offline

Posts: 1513328527

View Profile Personal Message (Offline)

Ignore
1513328527
Reply with quote  #2

1513328527
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1513328527
Hero Member
*
Offline Offline

Posts: 1513328527

View Profile Personal Message (Offline)

Ignore
1513328527
Reply with quote  #2

1513328527
Report to moderator
1513328527
Hero Member
*
Offline Offline

Posts: 1513328527

View Profile Personal Message (Offline)

Ignore
1513328527
Reply with quote  #2

1513328527
Report to moderator
1513328527
Hero Member
*
Offline Offline

Posts: 1513328527

View Profile Personal Message (Offline)

Ignore
1513328527
Reply with quote  #2

1513328527
Report to moderator
Automatic
Full Member
***
Offline Offline

Activity: 238


View Profile
March 02, 2014, 04:24:35 PM
 #2

As long as the transaction is valid (I.E. script returns a positive value, transaction is signed, inputs aren't spent, etc...), then, the transaction can be broadcasted at any time.

A node could delay payment, but, each node on the bitcoin network is connected to eight other nodes, randomly selected from nodes they've heard of before, at-least, if not more. It'd be somewhat hard to become all eight nodes to block all communication to the outside world. If you do spend some money, then want to take it back, the only way is to invalidate the transaction you previously signed, most likely by just spending the inputs (And hoping it gets confirmed first, but, in your case it would).

Anyway, why'd you be sending money then wanting your money back? This is a selling point of BTC, no chargebacks.

Please ask for a signed message from my on-site Bitcoin address (Check my profile) before doing any offsite trades with me.
mrgoup
Newbie
*
Offline Offline

Activity: 2


View Profile
March 02, 2014, 04:41:23 PM
 #3

I was playing around with the debug window and once I thought that I saw that I was connected only to one peer, so I was also wondering if there was a minimum number of peers parameter somewhere in the qt wallet (so that for example if you don't have enough peers, you can't maker any payments?).

I am sure there could be examples where you pay for something and then wait for confirmation for a day and meanwhile change your mind.
You could also make another transaction (with different coins), but then the bad peer let's the previous one trough and you spend twice the amount, anyway it was a theoretical example, so that I can plan a better attack khm... understand the network in a better way  Smiley.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!