Open Rav3nPL opened 7 years ago
I do realize, that activating SW under 95% is risky. Maybe when this code roll it get so much support, that reaching this limit will be possible.
bitpay has apparently abandoned development of the bitcore/insight stack
This has sound logic. There is an outstanding pull request here: #43 Rebase bitcore patches to 0.14.x.
I was wrong in the previous comment; it seems bitpay is doing bitcore-related work again, but moving from bitcoind to bcoin (a javascript implementation). See https://github.com/bitpay/bitcore/tree/next , it's pretty active.
I am not sure how stable and usable that is, I don't want to speak for bitpay, I haven't tried the /next branch
We forked bitpay bitcore bitcoin core (o_O) here
https://github.com/satoshilabs/bitcoin
and here is Bitcoin ABC (= Bitcoin Cash = Bcash) with the patches
As for now, I found logic behind your code as best way to increase block size. Moving max block size regulation to protocol level, away from human hands is only good option to make it once and for very long time. Block size limit need to be raised as predicted by Satoshi, and SegWit is making major step forward to scalability in micro-transctions and upgrade transaction script code.
Core code for SegWit activation should be lowered to 75% and when reached, adaptive block size should be also activated.
Combining SegWit and ABS make Bitcoin open for much wider adoption than choosing from one of those two.
Currently Core SegWit activation on 95% is impossible to reach, and BU block size regulation logic is bad from beginning, not mention bug/s found in it.
I hope that you can make your code up and running in short time, to help end this crisis.