Bitcoin Forum
July 29, 2024, 08:25:10 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Why 6 confirmations?  (Read 381 times)
dominicus (OP)
Member
**
Offline Offline

Activity: 97
Merit: 10



View Profile
July 09, 2013, 01:16:04 PM
 #1

Why do many bitcoin services implement 6 confirmations before BTC credit?
What's so special about 6 vs. 5 or 2?


Help me troubleshoot my BTC address.
Send some coins here: 1FkQS1RuEmSppCPdGPVGHtc4aj2nBiHAYF
If I don't return your test transfer, it must be having issues still.
bitcoin44me
Full Member
***
Offline Offline

Activity: 252
Merit: 100


MARKETPLACE FOR PAID ADVICE LIVE BROADCASTS


View Profile
July 09, 2013, 01:24:06 PM
 #2

Which one?

I think that most services are requiring 1 or 3 confirmations.
It is to prevent double spending. The higher the number of confirmations is, the lower the risk is.


But it will delay the transaction.
Most of the time, 1 confirmation is enough.

dominicus (OP)
Member
**
Offline Offline

Activity: 97
Merit: 10



View Profile
July 09, 2013, 01:38:17 PM
 #3

mtgox, and if I recall correctly, coinbase & bitpay post BTC transfers after 6.

I understand the part about lowering double-spend risk, but why not implement a risk-based wait period?  If the transaction is for smaller amounts, wait for fewer confirmations and viceversa.

Seems like a lost opportunity to speed up the network.  May be a trade-off between pursuit of a consistent user experience vs. mitigating overall fraud risk.

I was just wondering if there were any technical aspects behind this, 6 confirmations being ~1hr, might have been related to the ability of the network to spot a forks in the blockchain or such.

Help me troubleshoot my BTC address.
Send some coins here: 1FkQS1RuEmSppCPdGPVGHtc4aj2nBiHAYF
If I don't return your test transfer, it must be having issues still.
Pages: [1]
  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!