Circulating Supply: 618,704,945,976 M

I wish that your word will not happen. Depositories of XMR and other cryptocurrencies, plus the 24/7 markets of ingame item "new" M vs. the currencies, plus the market making provided by Coinshop (and others - just use SELLBUY/BUYSELL according to HH SirJacket instruction), serve the important role of
effortless linking of ingame value with the outside world (aka "real world").

We are not factually valued $100,000,000 (or anything), unless you can exchange your ingame value to outside world value of your choice, with a few clicks, while smoking cigar in a jacuzzi of your choice. I will expand this statement soon due to the reason of difficulty with typing lengthy just now.

Thanks Twiggy!

Next week!

it was an oversight in a special case of block validity checking. I had all the complicated pax deposit/withdraw totals matched up with pending cross chain swaps but there was a test for a special 2 vout coinbase as we use the second vout for the price feed data.

So it was testing for this special case properly, but the default path of the 2 vout coinbase (which cant be any pax tx) was set to ok, instead of error.

totally my oversight, and the case where you spend all your effort on the difficult part and dont check for the simplest exeptions to the simplest case. I will take a 1 million KMD responsibility for this and contribute that much to a cryptox make good fund. I believe the long delay from our request to stop deposits and when it was finally done was a contributing factor that made it go as big as 3.5 mil, but with 1 million KMD, that means at least one third of all the cryptox KMD can be made real.

this combined with the 25 BTC to make cryptox whole and I think we have most of the solution

I will use personal KMD for the 1 million contribution to the makegood fund.

invoking the slippery slope fallacy?

the fear of centralised control vs hyperinflation via malicious exploit, hardly seems a reason to fear big brother fucking with our chain.

https://en.wikipedia.org/wiki/History_of_bitcoin

Quote
On 6 August 2010, a major vulnerability in the bitcoin protocol was spotted. Transactions weren't properly verified before they were included in the transaction log or blockchain, which let users bypass bitcoin's economic restrictions and create an indefinite number of bitcoins. On 15 August, the vulnerability was exploited; over 184 billion bitcoins were generated in a transaction, and sent to two addresses on the network. Within hours, the transaction was spotted and erased from the transaction log after the bug was fixed and the network forked to an updated version of the bitcoin protocol. This was the only major security flaw found and exploited in bitcoin's history.


The highlighted portion is essentially what has happened. The difference is that bitcoin knew about it for over a week, while we didnt find out about it until the attack was under way. Also, I announced in realtime block 235300, which is the stopping of a chain.

If there is a bug in the future that allows to totally bypass the coin emission, then we will fix that to. You can count on that.

I support the roll back.  Arguments of blockchain immutability are irrelevant here as the attackers actions rendered the blockchain mutable

I think you have made your point multiple times by now. They are rolling back the chain. Nothing can be done already. Just hope for the best ...

don't want to deal with this shit - i'm out.

So strange, 2 accounts are actively, I would even say desperately asking to make a deal with the attacker and 10-15 are saying naah, that's OK, let's do it.

The decision was made already. There is no need to ask how much he wants. He'll get nothing.

If other exchanges' wallets are not in maintenance right now, he'll probably be dumping there right now.

I don't see what all this fuss is about.
It's either you let the coin die with someone generating as much as he wants, and of cause let the devs go with all BTC's
or rollback 200 blocks when everyone here knows not to move anything.

200 blocks out of 235000 is nothing, especially when it was posted real-time.

There is no alternative. Restart at 235300.
Good job devs catching it as it is.

the attacker is generating half the blocks now. that is pace of 3 million KMD per hour and would be for another 6 hours or so. So we are looking at more like 25 to 30 million KMD. and most all of this was AFTER I announce the chain would be stopped and rolled back to that point.

not sure how this is different from the bug that allowed to create bitcoins. allowing such coin creation to be upheld is not any immutability, but a total violation of coin emission.

this is not a rollback to bail out some exchange that got hacked.

the attacker has generated another 27 blocks in the last hour and at this pace he would generate much more than 10 million KMD by the 236000 block with the original bugfix trigger.

It is a bug that was not found by a white hat, but by someone who repeatedly exploits the same bug over and over.

I did not block the first exploit of the bug, that can be considered a bounty. But beyond that, it is like handing in the same thing over and over again expecting to be paid for it.

I never said the code is the law. The miner reward has been stated to be 3 KMD per block, not 100003 KMD. It is a chain stoppage due to a critical bug. People have relied on 3 KMD per block as mining reward, so to allow 100003 KMD as a reward would violate things a lot more than stopping the chain at 235300.

I will use common sense for this. Also, in the future if there is some other critical bug that dramatically changes what everyone's understanding is, then I will likely fix it and stop the chain, etc.