This is quite interesting; I certainly did not anticipate that there would be a correlation with the past attack. This is why people should definitely stay away from both Classic and BU. They are trying to manipulate people into joining them by creating a false sense of urgency. They start complaining about bad user experience when in-fact they're the ones who caused it in the first place. We're at ~14k unconfirmed transactions now; seems to be slowly improving.
Jesus, this graph looks like the FTIR spectrum of chymotrypsin. Bad memories.
It goes even further, albeit my machine started to act sluggish (this one is not suitable for such) so I stopped there.
lauda you are truely failing your core shilling.
its not a debate about core vs classis, .. its about 2mb that CORE could and SHOULD include..
put it another way if capacity does not need to be increased then there is no reason for you to defend segwit as the needed tool for capacity growth because your own argument that capacity doesnt need increasing also means that segwit is not needed as a solution to capacity increase. so anyone spouting out that segwit is great for the needed capacity growth must be saying that capacity growth is needed..
try to use logic next time.
2mb debate has been going on since summer 2015.. and guess what. classic and BU was not even invented/envisioned or proposed then. so just stop trying to turn the capacity debate into a "us vs them" political debate.
2mb should be included in core along with the 12 other implementations. there is no battle for control because ultimately no one, including core... no one should have control of the code
