That is a 300 post "dramatic" and "cancerous" thread about how Crowetic's did not behave the way it was expected. I did not find anything related to the issues of Burst. I do not recommend that reading to anyone.
I took a look at those forums, and only found discussion about the limit of 256 transactions in one block. And that the burst community hopes that it will be resolved by NXT and they will be able to port it. However, it may not be possible because the NXT code may change license.
What about the possible exploits of Burst mining system, which Crowetic mentioned? You say, he is not a dev, so some dev must understand it much better.
Quick response off the top of my head.
256 transactions per block is still a limit IIRC, changing that would require a fork. Nothing that can't be arranged though.
BURST does have a limited potential for a NaaS attack, though I believe NaaS attacks as currently described are purely in the realm of the theoretical.
In long discussions in the times past we concluded that there is only one somewhat realistic "exploit" possible. That exploit is generating nonces on the fly with a GPU (or a potential ASIC) instead of reading them off disk. In essence this is just straight up PoW mining.
HOWEVER, it was concluded that the "exploit" is so inefficient that it is much better just to mine normally. ENTIRE POINT of PoC is the tradeoff, it was not conceived as a bullet-proof system against such "gaming" attempts, just something that is more efficient if mined normally.
IMO, most likely explanation of the current network state is that Bitladen is back with all the joys that brings
Naturally, if Bitladen or anyone else has new info to share I would be very interested in hearing it.
