BCH Difficulty needs some kind of rethink.
Waiting hours between blocks is a deal-breaker.
There could be some kind of difficulty decrease after 15minutes ?
Surely someone has considered this....
Nice idea but not quite.
What needs to happen is if the block fails at ~15-20 minutes
Difficulty could ratchet down "ad-hoc" @ "one-off".
Continual manipulation invites havoc.
I think Avalanche might be the solution you're looking for. I'm not sure if instant blocks or altering difficulty would fix it
That would then be "continual manipulation".
If simply for a single 'immediate' block
then it would not necessarily be continual.
The idea is that block was late
'Acceptable Difficulty' would drop only for that one block ?
Yes - here there be dragons.
But still -we need to hammer this into the ground and fix it.
Slowly and very carefully.
BCH is 0-conf with like 27-28 responds before 1 conf or something
My vote would be to shorten block intervals dramatically, possibly to 1 minute or less. To not impact total coins created, also reduce issuance and increase block number @ halvings
Other coins have done this without suffering orphan problems. Vitalik wrote up a technical assessment of the tradeoffs and found shorter block intervals also improve security.
Avalanche should help with that.
Pre-consenus with Avalanch will accomplish what you want. Secure zero-conf transactions will remove the issues with waiting for long one-conf.
But will the exchanges and other services accept secure zero-conf transactions as secure or will they still wait for confirmation?
With time they will. pre-consensus is far from production, but it'll get there.
With time they will. pre-consensus is far from production, but it'll get there.
True - Avalanche does address the Zero-Conf issue,
but the problem is not Zero-Conf.
Credibility is built upon Reliability.
Occasional wayward blocks kill financial Credibility.
Normal variance, happens to any network. Why would it be a deal breaker?
The variance on BCH is can get pretty bad due to sharing SHA256 with Bitcoin and 3% of the price, recent example
1 block per minute on average 16 blocks
Normally, newbies have serious misconceptions when it comes to crypto transactions. You need to differentiate propagated/unconfirmed and n-times confirmed transactions.
It depends on the specific use-case whether 0-conf, 1-conf or 1+ conf transactions are acceptable or not.
An example where the 0-conf can become an issue is here on memo by reaching the 25 action limit, that limit can be increased in time, variance not an issue for 0-conf in general.
Block variance not a problem for any place and service that can accept 0-config, small and quick amounts works great for that. Only observation is that block variance is higher now.
Yes, but it's not so straightforward to implement. Search for bobtail on r/btc
