DynamicPimp
Newbie
 Offline
Activity: 45
Merit: 0
|
 |
March 13, 2017, 04:12:54 AM |
|
If we don't roll back we are only devaluing the whole ecosystem...How many coins do we think he/she got?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
No Gods or Kings. Only Bitcoin
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
cebb
|
|
March 13, 2017, 04:18:54 AM |
|
An attacker has taken advantage of an exploit and is generating coins. We made a new version that would stop this at 236000 but the attacker ramped things up to levels that will force us to rollback the chain to 235300.
Please do not do any transactions until we get a new version out that solves this.
more details after this attack is over
Attacker found a bug, let him keep the coins as a reward. Rollback is last resort, unless he got 5% of coin supply or more, rollback is far worse outcome. Remember BTER hack ... no rollback from NXT devs was right decision then, and is right descision for komodo now. Hacker did a service finding bug ... let him keep the coins, please! Edit: Komodo classic would be a disaster! There wont be Komodo classic. Komodo is a work in developmnent. No one has got the resources enough to keep the original komodo chain (komodo classic) working. Even if someone tries to launch komodo classic it will be DOA because the hacker will generate unlimited amount of coins on that older chain. Rollback is a must and there will be only one komodo. |
|
|
|
|
gulachov
Member
Offline
Activity: 111
Merit: 10
|
|
March 13, 2017, 04:20:08 AM |
|
If we don't roll back we are only devaluing the whole ecosystem...How many coins do we think he/she got?
I did not count, but about 5-6 millions. I have a suggestion for the devs. For the first year KMD is out, we can predict maximum amount of KMD in the system (discounting not claimed or not converted BTCD). We can also get total supply out of the block explorer. How hard would it be to compare the difference each block and hook it up to a Big Red Alarm? |
|
|
|
|
|
NotMyFarm
|
|
March 13, 2017, 04:36:51 AM |
|
is that the same bug as Zcoin had ? u are freaking kidding me  anything Z related seems to turn into crap |
|
|
|
|
boomboom
|
|
March 13, 2017, 04:39:39 AM |
|
If we don't roll back we are only devaluing the whole ecosystem...How many coins do we think he/she got?
If an equivalent amount is burnt from the dev premine it's basically paying the attacker a bug bounty from dev funds, all other investors are no worse off. Rollback is thermonuclear option, it can KILL komodo and SuperNET today! Paying a bounty to a guy who found dangerous bug is well worth it IMO |
|
|
|
|
|
tclo
|
|
March 13, 2017, 04:43:05 AM |
|
If we don't roll back we are only devaluing the whole ecosystem...How many coins do we think he/she got?
If an equivalent amount is burnt from the dev premine it's basically paying the attacker a bug bounty from dev funds, all other investors are no worse off. Rollback is thermonuclear option, it can KILL komodo and SuperNET today! Paying a bounty to a guy who found dangerous bug is well worth it IMO KMD was headed down the Coinmarketcap list already. This will probably bump it out of the Top 50, but maybe it was inevitable. Although some of that selling was probably the hacker, dumping coins. |
|
|
|
|
|
boomboom
|
|
March 13, 2017, 04:43:37 AM |
|
Rollback is a must.
Rollback will kill Komodo and SuperNET, we all know that, we're not too BIG to fail like Ethereum was. Think carefully @jl777! |
|
|
|
|
|
tclo
|
|
March 13, 2017, 04:45:07 AM |
|
Rollback is a must.
Rollback will kill Komodo and SuperNET, we all know that, we're not too BIG to fail like Ethereum was. Think carefully @jl777! Bittrex says the wallet is shut down for for the "hard fork", so I don't think there is any more discussion to be had and it's a done deal. |
|
|
|
|
|
CryptoSporidium
|
|
March 13, 2017, 04:46:39 AM |
|
Rollback is a must.
Rollback will kill Komodo and SuperNET, we all know that, we're not too BIG to fail like Ethereum was. Think carefully @jl777! Bittrex says the wallet is shut down for for the "hard fork", so I don't think there is any more discussion to be had and it's a done deal. Could be hard fork to fix bug, rollback is suicide ... |
|
|
|
|
jl777 (OP)
Legendary
Offline
Activity: 1176
Merit: 1132
|
|
March 13, 2017, 04:49:21 AM |
|
This was a bug in the code, actually it was code that was missing and allowed a vout to be created that wasnt constrained. It is closer to the billions of bitcoins bug.
I announced the block that will be rolled back to, pretty much in realtime, so it is more a stopping the chain at 235300 than rolling back. of course a few hundred blocks were generated during the time to make the fix. so yes, technically it is a rollback of a few hours, of the blocks that happened after 235300 was announced.
Let us not make a political circus out of this. It was a bug that was abused.
The attack started about 36 hours ago during the weekend. We detected it about 6 hours ago and had a fix that would go into effect at 236000. At that point the attacker would have had coins, but it would have been absorbable.
Then the attacker must have seen that things will be cutoff at 236000 and he went wild. He started a high frequency attack and started to move funds, even some z-transactions.
There were 15 blocks prior to 235300 with the illicit KMD in vout1 and the new version prevents any block with any tx that spends any of these 15 as invalid. Unfortunately, this will require a resync of the chain as the local DB has invalid blocks in it and even with the -rewind, komodod will be complaining.
If you are running native komodod, you need to update and resync. delete the usual blockchain files and komodostate in the ~/.komodo folder. Make sure to not delete your wallet.
The simplest is to leave the illicit KMD in the utxo where they are, frozen. So there wont be any dilution due to this.
|
|
|
|
|
bv68bot
|
|
March 13, 2017, 04:49:37 AM |
|
If we don't roll back we are only devaluing the whole ecosystem...How many coins do we think he/she got?
If an equivalent amount is burnt from the dev premine it's basically paying the attacker a bug bounty from dev funds, all other investors are no worse off. Rollback is thermonuclear option, it can KILL komodo and SuperNET today! Paying a bounty to a guy who found dangerous bug is well worth it IMO +1 This is the way guys, burn same amou t attacker got from dev funds! Rollback will never be forgotten, but a bug bounty ... no one would remember in 6 months. |
|
|
|
|
|
tclo
|
|
March 13, 2017, 04:49:43 AM |
|
Could be hard fork to fix bug, rollback is suicide ...
Ok good point there. I don't know anything about rollbacks, except with ETH, but it does seem like a bad idea, generally. |
|
|
|
|
|
bv68bot
|
|
March 13, 2017, 04:52:53 AM |
|
This was a bug in the code, actually it was code that was missing and allowed a vout to be created that wasnt constrained. It is closer to the billions of bitcoins bug.
I announced the block that will be rolled back to, pretty much in realtime, so it is more a stopping the chain at 235300 than rolling back. of course a few hundred blocks were generated during the time to make the fix. so yes, technically it is a rollback of a few hours, of the blocks that happened after 235300 was announced.
Let us not make a political circus out of this. It was a bug that was abused.
The attack started about 36 hours ago during the weekend. We detected it about 6 hours ago and had a fix that would go into effect at 236000. At that point the attacker would have had coins, but it would have been absorbable.
Then the attacker must have seen that things will be cutoff at 236000 and he went wild. He started a high frequency attack and started to move funds, even some z-transactions.
There were 15 blocks prior to 235300 with the illicit KMD in vout1 and the new version prevents any block with any tx that spends any of these 15 as invalid. Unfortunately, this will require a resync of the chain as the local DB has invalid blocks in it and even with the -rewind, komodod will be complaining.
If you are running native komodod, you need to update and resync. delete the usual blockchain files and komodostate in the ~/.komodo folder. Make sure to not delete your wallet.
The simplest is to leave the illicit KMD in the utxo where they are, frozen. So there wont be any dilution due to this.
A rollback for komodo now becomes the Dash 'premine' troll fest forever though, is it worth it jl777? Rollback violates core crypto prinicipal, I think only do for catastrophic loss, like DAO. |
|
|
|
|
|
NotMyFarm
|
|
March 13, 2017, 04:54:31 AM |
|
This was a bug in the code, actually it was code that was missing and allowed a vout to be created that wasnt constrained. It is closer to the billions of bitcoins bug.
I announced the block that will be rolled back to, pretty much in realtime, so it is more a stopping the chain at 235300 than rolling back. of course a few hundred blocks were generated during the time to make the fix. so yes, technically it is a rollback of a few hours, of the blocks that happened after 235300 was announced.
Let us not make a political circus out of this. It was a bug that was abused.
The attack started about 36 hours ago during the weekend. We detected it about 6 hours ago and had a fix that would go into effect at 236000. At that point the attacker would have had coins, but it would have been absorbable.
Then the attacker must have seen that things will be cutoff at 236000 and he went wild. He started a high frequency attack and started to move funds, even some z-transactions.
There were 15 blocks prior to 235300 with the illicit KMD in vout1 and the new version prevents any block with any tx that spends any of these 15 as invalid. Unfortunately, this will require a resync of the chain as the local DB has invalid blocks in it and even with the -rewind, komodod will be complaining.
If you are running native komodod, you need to update and resync. delete the usual blockchain files and komodostate in the ~/.komodo folder. Make sure to not delete your wallet.
The simplest is to leave the illicit KMD in the utxo where they are, frozen. So there wont be any dilution due to this.
you are nutz do NOT roll back - does not matter how many blocks !! this is ETH and the bailout all over again ! do NOT be greedy - let run as is - and burn supply after !!! (should have learned from Zcoin mistakes !!) |
|
|
|
MoveCrypto
Sr. Member
Offline
Activity: 364
Merit: 250
move that crypto
|
|
March 13, 2017, 04:57:16 AM |
|
This was a bug in the code, actually it was code that was missing and allowed a vout to be created that wasnt constrained. It is closer to the billions of bitcoins bug.
I announced the block that will be rolled back to, pretty much in realtime, so it is more a stopping the chain at 235300 than rolling back. of course a few hundred blocks were generated during the time to make the fix. so yes, technically it is a rollback of a few hours, of the blocks that happened after 235300 was announced.
Let us not make a political circus out of this. It was a bug that was abused.
The attack started about 36 hours ago during the weekend. We detected it about 6 hours ago and had a fix that would go into effect at 236000. At that point the attacker would have had coins, but it would have been absorbable.
Then the attacker must have seen that things will be cutoff at 236000 and he went wild. He started a high frequency attack and started to move funds, even some z-transactions.
There were 15 blocks prior to 235300 with the illicit KMD in vout1 and the new version prevents any block with any tx that spends any of these 15 as invalid. Unfortunately, this will require a resync of the chain as the local DB has invalid blocks in it and even with the -rewind, komodod will be complaining.
If you are running native komodod, you need to update and resync. delete the usual blockchain files and komodostate in the ~/.komodo folder. Make sure to not delete your wallet.
The simplest is to leave the illicit KMD in the utxo where they are, frozen. So there wont be any dilution due to this.
you are nutz do NOT roll back - does not matter how many blocks !! this is ETH and the bailout all over again ! do NOT be greedy - let run as is - and burn supply after !!! (should have learned from Zcoin mistakes !!) How is this different from when Bitcoin was in beta and they did a hardfork to fix the bug that allowed someone to generate millions of BTC? How much KMD was transacted on the chain since block 235200 anyways? Maybe about a dozen non-miner, non-attacker transactions? |
|
|
|
|
cebb
|
|
March 13, 2017, 04:57:48 AM |
|
is that the same bug as Zcoin had ? u are freaking kidding me anything Z related seems to turn into crap Zcoin is doing very good at the moment. The bug was fixed ASAP and the damage was contained. ZCOIN is at 0.03BTC/XZC at the moment. Not bad for a coin whose price was 0.0004BTC/XZC when the bug was found. In fact the bug discovery nailed the reason for downtrend in coins price and lead to a massive rally of 900% post bug fixing. |
|
|
|
|
|
NotMyFarm
|
|
March 13, 2017, 05:00:23 AM |
|
is that the same bug as Zcoin had ? u are freaking kidding me anything Z related seems to turn into crap Zcoin is doing very good at the moment. The bug was fixed ASAP and the damage was contained. ZCOIN is at 0.03BTC/XZC at the moment. Not bad for a coin whose price was 0.0004BTC/XZC when the bug was found. In fact the bug discovery nailed the reason for downtrend in coins price and lead to a massive rally of 900% post bug fixing. Do not fall for it they are only up as they have some huge chinese MLM guy behind them throwing more money than ideas u really wanna end up like that good luck eh (there is more important things than $$ in starting a coin like this - value will follow trust !!!) |
|
|
|
|
cebb
|
|
March 13, 2017, 05:02:35 AM |
|
This was a bug in the code, actually it was code that was missing and allowed a vout to be created that wasnt constrained. It is closer to the billions of bitcoins bug.
I announced the block that will be rolled back to, pretty much in realtime, so it is more a stopping the chain at 235300 than rolling back. of course a few hundred blocks were generated during the time to make the fix. so yes, technically it is a rollback of a few hours, of the blocks that happened after 235300 was announced.
Let us not make a political circus out of this. It was a bug that was abused.
The attack started about 36 hours ago during the weekend. We detected it about 6 hours ago and had a fix that would go into effect at 236000. At that point the attacker would have had coins, but it would have been absorbable.
Then the attacker must have seen that things will be cutoff at 236000 and he went wild. He started a high frequency attack and started to move funds, even some z-transactions.
There were 15 blocks prior to 235300 with the illicit KMD in vout1 and the new version prevents any block with any tx that spends any of these 15 as invalid. Unfortunately, this will require a resync of the chain as the local DB has invalid blocks in it and even with the -rewind, komodod will be complaining.
If you are running native komodod, you need to update and resync. delete the usual blockchain files and komodostate in the ~/.komodo folder. Make sure to not delete your wallet.
The simplest is to leave the illicit KMD in the utxo where they are, frozen. So there wont be any dilution due to this.
+1 to the decision to roll back. Dont listen to trolls here. They may be sockpuppet of the attacker. Rolling back chain few hours is no big deal. Those not happy with the Dev's decision can move on. |
|
|
|
|
|
NotMyFarm
|
|
March 13, 2017, 05:04:12 AM |
|
This was a bug in the code, actually it was code that was missing and allowed a vout to be created that wasnt constrained. It is closer to the billions of bitcoins bug.
I announced the block that will be rolled back to, pretty much in realtime, so it is more a stopping the chain at 235300 than rolling back. of course a few hundred blocks were generated during the time to make the fix. so yes, technically it is a rollback of a few hours, of the blocks that happened after 235300 was announced.
Let us not make a political circus out of this. It was a bug that was abused.
The attack started about 36 hours ago during the weekend. We detected it about 6 hours ago and had a fix that would go into effect at 236000. At that point the attacker would have had coins, but it would have been absorbable.
Then the attacker must have seen that things will be cutoff at 236000 and he went wild. He started a high frequency attack and started to move funds, even some z-transactions.
There were 15 blocks prior to 235300 with the illicit KMD in vout1 and the new version prevents any block with any tx that spends any of these 15 as invalid. Unfortunately, this will require a resync of the chain as the local DB has invalid blocks in it and even with the -rewind, komodod will be complaining.
If you are running native komodod, you need to update and resync. delete the usual blockchain files and komodostate in the ~/.komodo folder. Make sure to not delete your wallet.
The simplest is to leave the illicit KMD in the utxo where they are, frozen. So there wont be any dilution due to this.
+1 to the decision to roll back. Dont listen to trolls here. They may be sockpuppet of the attacker. Rolling back chain few hours is no big deal. Those not happy with the Dev's decision can move on. and stupidity and greed win again wtf |
|
|
|
|
cebb
|
|
March 13, 2017, 05:04:43 AM |
|
is that the same bug as Zcoin had ? u are freaking kidding me anything Z related seems to turn into crap Zcoin is doing very good at the moment. The bug was fixed ASAP and the damage was contained. ZCOIN is at 0.03BTC/XZC at the moment. Not bad for a coin whose price was 0.0004BTC/XZC when the bug was found. In fact the bug discovery nailed the reason for downtrend in coins price and lead to a massive rally of 900% post bug fixing. Do not fall for it they are only up as they have some huge chinese MLM guy behind them throwing more money than ideas u really wanna end up like that good luck eh (there is more important things than $$ in starting a coin like this - value will follow trust !!!) I dont need luck. I can identify opportunities like I did with Zcoin and currently looking at 600% gains on my Zcoin. The rally will not stop here. it will continue till the new Algo MTP is launched. waiting for 0.08 XZC/BTC before I sell. and I wont have to wait too long for that price. maybe a few weeks. |
|
|
|
|
|
