He's likely talking about comments made by crowtec (sp?) shortly before they dropped out of BURST.
Yeah this. What happened there and why did they drop out of Burst?
Rico, yes please do enlighten us. I know I may have made some mistakes in my comments but I would welcome be thankful of any comments that would correct those mistakes.
It would also be to the benefit of the people who come to the thread. Ty.
Certainly you refer to this exit post from crowetic:
https://bitcointalk.org/index.php?topic=1323657.msg19868944#msg19868944So to make some things clear:
- Crowetic is no developer and has never been. I do not say this to discredit him in any way, it's a simple fact he also stated himself many times. He was sysadmin and he had (maybe paid) developers to look into things. So I would see him as kind of "facilitator", but not developer.
- He is one man. So when you said "There were some developers who said..." you have blown things out of proportion. No developer and not plural.
- Even Crowetic stated - and I quote: "I fully believe the algo is able to be exploited". Now while this shows a strong belief, it is nothing else than that: a belief.
Crowetic believed many other things in his "Exit post", which were partially true (like the network not being able to handle the max num of transactions without forking
at the time of his post) and some which were not true because as a non-dev he had not enough insight into these matters.
Again, I would like to state that all of this is in no way meant to discredit him. It's only meant as a clarification, so that "Word of mouth" doesn't start to skew the facts more and more.
There were no developers, not even a single one who said that BURST is broken to the core. There was one non-dev guy who said he believes that.
Ok?
Now he also said he does believe some other things, which have proven to be untrue. Like BURST could only be repaired when written anew "from scratch up" and the similar.
That was provably untrue, because BURST today has already rock solid wallets/nodes - if you happen to use the right version.
https://explore.burst.cryptoguru.org/tool/observe (the number of valid nodes was somewhere in the single-digit percentage when Crowetic wrote his post)
If you look at the changes necessary to make BURST stable and being able to cope with max-TXs capacity, it was not that much. You just had to know/find where to apply your patch.
Nevertheless, in the meantime much more work happened on the BURST core. We actually started to make fundamental changes - which Crowetic also called for - to the code base to make it fit for future requirements. So the situation is not like "Maybe its better to give the PoCC more time to fix the core problems..."
The situation is much more such, that the PoCC and the remaining core devs have already fixed the problems that plagued BURST in July and are now already en route to implement things Crowetic wouldn't even have hoped for 3 months ago. Like DB independece, multiple DB backends which did require
significant changes to the underlying infrastructure.
We are running a permanent TestNet and the wallet there is - intentionally - beaten rigorously. Because of this we have fixed errors and problems Crowetic (and others) weren't even aware of!
As problems of stability become a thing of the past, new paths open up for developing functionality and infrastructure. We are entering the "age of emancipation", where the BURST code base starts to be better in certain aspects than the original (and present) NXT code base. And this trend will continue - as we did already announce in our 1st announcement
We will change this and we will change it fast, because
even NXT has not the development capacities we are bringing to the
table right now.
Is there much work to do? YES! Is some magic ultra-rocket science needed? NO! Just plain old good software engineering, done by people with the skills, experience and dedication.
That's all it takes for now.
Of course, we do have some magic ultra-rocket science available when needed.
