Bitcoin Forum
May 06, 2024, 09:07:00 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: The cost of Bitcoin attacks  (Read 1723 times)
Decoded
Legendary
*
Offline Offline

Activity: 1232
Merit: 1029


give me your cryptos


View Profile
October 27, 2015, 11:13:57 AM
 #21

It's near impossible to get a double transaction with even 1 confo.

Just think about the usual 3 confos... Jeez!

looking for a signature campaign, dm me for that
1714986420
Hero Member
*
Offline Offline

Posts: 1714986420

View Profile Personal Message (Offline)

Ignore
1714986420
Reply with quote  #2

1714986420
Report to moderator
Unlike traditional banking where clients have only a few account numbers, with Bitcoin people can create an unlimited number of accounts (addresses). This can be used to easily track payments, and it improves anonymity.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
amaclin
Legendary
*
Offline Offline

Activity: 1260
Merit: 1019


View Profile
October 27, 2015, 01:47:20 PM
 #22

It's near impossible to get a double transaction with even 1 confo.
yes. in mainnet. today
fbueller
Sr. Member
****
Offline Offline

Activity: 412
Merit: 266


View Profile
October 27, 2015, 03:27:49 PM
 #23

Check the blockchain.info page on blockchain forks. You'll see one-block-deep forks happen all the time. Your application needs to be able to undo a 'successful payment' because reorgs occur.

Should a certain someone Wink have his signature malleator running, a transaction with TXID A that confirmed in block A might have a different TXID if block B replaces block A.

So you have to be able to totally undo a successful transaction if the tip changes and orphans any block you have that includes a payment.

Bitwasp Developer.
Pages: « 1 [2]  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!