Yes, that's a legit concern. Any POS SW has to auto-upgrade as needed, the only issue I see comes if a merchant uses an abandoned SW and gets deprecated with a new HF.
Much easier, and better to do this fast HF upgrade cycles now, while the chain is still in fast development, and usage is low.
I sent in logs from the stress test. If the clients make changes and retest I hope they’re a little more specific in advance with what we should log and send in, like logging level
Stress test was user organized, developers did not take active role in it. Last minute, jtoomim tried to organize some sort of data collection. Hope next test will be more organized.
Hey Naomi. Have you considered getting the other side of the story? Chris Pacia seems pretty partisan in the whole matter and I'd be interested to hear a rebuttal of many of his claims
It could be very hard to find such a person. Do you have someone to suggest?
I don't think that's what anyone is claiming. The "remove of the limit" rhetoric acknowledges that miners wont try to propagate a block that has a high probability of getting orphaned.
But is it. I saw many times 'fidelity problem' and rhetoric 'remove the limit to show the chain can scale'. Remove the bottlenecks, that's the way to show haw the chain can scale.
Aright I'm with you there. Although there is the so called "fidelity effect" where you want to be able to show bigger buisinesses that this thing isn't going to choke under pressure
and just removing the limits is just a PR, or even outright lie, if one wants to use that as a proof that it won't choke. Software needs optimization, and removing the bottlenecks.
Aright I'm with you there. Although there is the so called "fidelity effect" where you want to be able to show bigger buisinesses that this thing isn't going to choke under pressure
Simply, software is not optimized and can not use hardware resources, even if limits are removed. There are many bottlenecks to be removed before we can show BCH won't choke.
Aright I'm with you there. Although there is the so called "fidelity effect" where you want to be able to show bigger buisinesses that this thing isn't going to choke under pressure
And BCH is not yet there - with current software implementations it will choke under >8M daily TX volume, no matter if the block limit is even removed, or not.
I'm not necessarily saying sustained volume at those levels but in a bull market you can get media hits that sebe usage into a frenzy. We don't want to screw the pooch at that time.
From 25,000 to 2.5M daily tx are two orders of magnitude. 100x. BCH as is can take any media hysteria in the short term (2 years). And easy fix of burst relay gets us to 8M daily tx.
It could be small rasp pi nodes which got knocked out. It would only be an issue if it hit the miners. Also, you can say that 75% of the nodes passed the test - Glass half full/empty?
I've been saying since 9/1 that the next stress test should be 10/1 and so forth. There were too many kinks to work out and real volume can come in very very quickly.
Re 'real volume'. It can, but that to happen is very unlikely. You have unrealistic expectation. Please look at things in perspective.
That >25% of ABC nodes got knocked down is highly concerning. No statement from ABC or miners as to why. BU nodes all held up. Maybe we do need to run more stress tests after all.
That >25% of ABC nodes got knocked down is highly concerning. No statement from ABC or miners as to why. BU nodes all held up. Maybe we do need to run more stress tests after all.
No statement from ABC? Why do you need it? It is not that ABC team run ALL those nodes. (BTW, it's 17%)
Do we know which BCH implementations did the best and which did the worst during the stress test? Tom Zander said Bitcoin ABC did the worst. How is performance gauged?
Only metric there is, is the fallout of 250 BC nodes at the time of the 'test' - https://cash.coin.dance/nodes/all. Maybe they were all low-end systems. I wouldn't make claims like Tom
All development groups agree on that schedule. Blaming ABC now is of no purpose. Also, SBI plans to use XRP for all those things you listed, with BCH only as settlement layer.
Major roadblock is ABC wants to hardfork every 6 months which means theyd have to patch all their software or possibly scrap entire projects. Also they're extremely suspicious of China
All development groups agree on that schedule. Blaming ABC now is of no purpose. Also, SBI plans to use XRP for all those things you listed, with BCH only as settlement layer.