Bitcoin Forum
November 10, 2024, 10:55:10 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 [3]  All
  Print  
Author Topic: I'm so tired of seeing the complaint on block confirmation times. Here's why.  (Read 2614 times)
cbeast
Donator
Legendary
*
Offline Offline

Activity: 1736
Merit: 1014

Let's talk governance, lipstick, and pigs.


View Profile
December 28, 2014, 08:03:33 AM
 #41

I was talking about the main mining pool. I meant centralized - not mature. You are free to disagree though.
As I understand it, there are centralized mining farms, but not centralized mining pools. Miners on pools are free to jump to other pools. Mining farms don't mine on pools, but compete with them instead. Miners don't generally allow a pool to get too large. I realize that pools can conspire. As cypherdoc is fond of saying, it's not a fault with the Bitcoin protocol, it's a human choice.

True, but still looks pretty centralized to me. https://blockchain.info/pools. If a merchant connects to the top 5 pools, he has access to more than 51% of the total hashrate. I'm not criticizing the network, it's working as intended. I'm saying that it wouldn't take much for a merchant to accept 0-confirmation transactions while getting reasonable security.
I think side chains are inevitable as a necessary evil. Kinda like lawyers.

Any significantly advanced cryptocurrency is indistinguishable from Ponzi Tulips.
dwma
Sr. Member
****
Offline Offline

Activity: 405
Merit: 250


View Profile
December 28, 2014, 09:06:16 AM
 #42

agreed 99% of Tx's dont really require confirms..

but for all of those that do need confirms.. they cry when they wait over 10 minutes.. but i have never ever seen them post when their TX's have taken them just a couple minutes to confirm due to fast hashing
\

It isn't fast hashing, it is just luck.  I've had to sit around a BTC ATM machine an extra 30 minutes because hashes were coming through that were longer than 10 minutes.

not really luck.. in short if i hashed 1 number a minute and wanted an average 10 minute hash time.. each hash would be a number between 0 and 20..
10 times it would average below 10 minutes.. 10 times it would average over 10 minutes.. but on average.. you will get a 10 minute hashtime when repeated the process a few thousand times..

its not lucky that a block is found in 1 minute or unlucky if it too 19 minutes.. its all based on maths, not luck. so its just a standard feature of randomness that some take alot of time some take very little time.

but i do laugh that you complain about 30 minutes, whilst a western union takes much longer. and then for instance trying to get paypal or apple pay to transfer money to your bank and then to a FIAT ATM... even longer..

Franky.. why have I never forgotten your account ?  Oh I am too lazy.

Hitting a hash is analogous to a lottery where every hash is an entry.  It is luck as much as averages as much as math.  When I'm expecting the 6 confirms to take an hour and they take 1.5 hours, I got unlucky.

I don't use Western Union as an ATM.  I have received payments from WU and when I show up it doesn't take over an hour.  Oddly the ATM fixed it by having your xfer go to an account before you show up but their solution has me leaving some random amount under $20 USD in the account that didn't fit their fiat dispersal denominations.  Typical BTC solution !  SMH
ranochigo
Legendary
*
Offline Offline

Activity: 3038
Merit: 4420


Crypto Swap Exchange


View Profile
December 28, 2014, 10:16:43 AM
 #43

Litecoin is faster.
If you need to send money quick: use not bitcoin
And much more volatile than Bitcoins. Alot of merchants uses Bitcoin payments only, not litecoin. Due to the fact that most merchant services which companies prefers offers only Bitcoin payments. When using Bitpay, they use special algronithm to determine the risk of a transaction being a double spend.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
picolo
Hero Member
*****
Offline Offline

Activity: 1022
Merit: 500



View Profile
December 28, 2014, 10:35:35 AM
 #44

I'm so tired of seeing this complaint on block times.

If you are one of the complainers, then here's an experiment I want you to perform and then explain to me how it is possible:

Transfer some bitcoin to your blockchain.info wallet and watch/listen for how long it takes to get there. That's right-- It takes about 5 seconds until you hear the *Beep*. Now think for a second, how did they do that? If they aren't waiting for the entire 10 minute block confirmation time, then how do they know money was sent?

Any merchant can use this method to see a transaction propagating through a majority of the nodes! This whole "10 minute" thing is given way too much importance because it doesn't matter for 99% of transactions. It's just something that people can focus on to complain about because they don't understand this. You can see any transaction on the network nearly instantly.

So the problem must be with the wallet you are using if you can't see an instantaneous transaction. So, rather than complaining about 10 minutes confirmation time which frankly doesn't matter in 99% of situations, then the solution is to get your wallet to support the same technology that blockchain.info is using to SHOW the transaction occurring in near-realtime. Not to complain about 10 minute block times.

And you could argue that double-spends could make this method irrelevant, but if you are THAT concerned for the particular transaction, then go ahead and wait for the full confirmation. But that level of verification is a very small % of the time. Not many people want to steal a $5 cup of coffee bad enough to do a double spend on it. And yes, I'd wait for a few confirmations if I was transferring 100 BTC.

The point is: Block time doesn't matter for 99% of transactions. And for the 1% where it might matter (bigger purchases), 10-30 minutes is an acceptable waiting period!


A Misconception:
I think that the complaints about the block confirmation time stem from a misconception of what is happening with credit cards, which causes a person not to compare apples to apples:  Your credit card and debit transactions are not instantly confirmed either. At stores these transactions are given credibility "immediately" but still take 3-5 days to actually move through the payment processors between bank accounts. 3-5 days is WAY slower than 10-30 minutes for a block confirmation if you want to compare apples to apples. The problem is people aren't comparing apples to apples when they compare 10 minute block times with credit card transactions. The credit card transactions aren't "confirmed" either at this point. The payment processor is simply fronting the money (just like blockchain.info shows the transaction instantly) while the transaction goes through. These credit card payment processors are basing this method on the same logic that blockchain.info uses to instantly display transactions: It's the fact that most transactions aren't fraudulent. And who wastes their time trying to defraud a system to steal a $5 cup of coffee?



Correct comparisons:
Bitcoin purchase = appears within seconds on the network
Credit card purchase = appears to be completed within seconds
(TIE)

Bitcoin money is ACTUALLY transferred = 10 minute average time
Credit card money is ACTUALLY transferred = 3-5 days (or longer)*
(BITCOIN wins)

*If I remember correctly, Andreas Antonopoulos said in one of his videos that credit card transactions aren't settled for up to 30 days. Now how does that compare to 10 minutes?  Compare apples to apples.


- - - - - - - - - - - - - - - -


Lastly, from satoshi's own mouth on the subject of verifying fast payments:

Besides, 10 minutes is too long to verify that payment is good.  It needs to be as fast as swiping a credit card is today.
See the snack machine thread, I outline how a payment processor could verify payments well enough, actually really well (much lower fraud rate than credit cards), in something like 10 seconds or less.  If you don't believe me or don't get it, I don't have time to try to convince you, sorry.
http://bitcointalk.org/index.php?topic=423.msg3819#msg3819




You are right and a small Bitcoin transfer is usually safe without waiting for the confirmation anyway.
funtotry
Sr. Member
****
Offline Offline

Activity: 420
Merit: 250


Ever wanted to run your own casino? PM me for info


View Profile
December 28, 2014, 07:09:29 PM
 #45

I was talking about the main mining pool. I meant centralized - not mature. You are free to disagree though.
As I understand it, there are centralized mining farms, but not centralized mining pools. Miners on pools are free to jump to other pools. Mining farms don't mine on pools, but compete with them instead. Miners don't generally allow a pool to get too large. I realize that pools can conspire. As cypherdoc is fond of saying, it's not a fault with the Bitcoin protocol, it's a human choice.

True, but still looks pretty centralized to me. https://blockchain.info/pools. If a merchant connects to the top 5 pools, he has access to more than 51% of the total hashrate. I'm not criticizing the network, it's working as intended. I'm saying that it wouldn't take much for a merchant to accept 0-confirmation transactions while getting reasonable security.
In this case the merchant would not have control over the pools. They would only have a connection to the nodes the pools broadcast from. If a merchant is broadcasting a double spend transaction to these nodes then others should notice as other nodes should know and understand the importance of these nodes and alert anyone relying on a transaction of the possibility of a double spend attempt

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!