Create account

replied 57d
Fnuller15
lowering the blocktime really doesn't mean anything as u would need to wait for more confirms for the same certainty. also the blocksize limit/scalability would have to b replanned tooBCH's frequent slow blocks is the outcome of low relative hashrate and swing mining.

This can only be solved with a hashing algorithm change.As I see it, the BCH community is too close minded currently to make this change. This hinders functionality and adoption.Somewhat of a workaround would be to refine 0-conf adoption/acceptance. By default, the probability of double-spending decreases with the time passing between blocks.So it would be rather easy to make it good enough for most point of sale usecases.

Overall, it's a rather overblown issue affecting the crippled btc network.
Fnuller15
replied 57d
For some usecases, one confirmation of a 2.5 min block will be sufficient although is is technically not as secure as a 10 min block. 1 conf will signal that the payment is now settled
Fnuller15
replied 57d
I tend to agree. We will probably have to change hashing algorithm if we keep loosing hasrate vs BTC.