Bitcoin Forum
January 18, 2020, 09:11:16 PM *
News: Latest Bitcoin Core release: 0.19.0.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 [346] 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 ... 872 »
  Print  
Author Topic: [ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B  (Read 1155342 times)
boomboom
Hero Member
*****
Offline Offline

Activity: 1045
Merit: 518



View Profile
March 13, 2017, 04:39:39 AM
 #6901

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

1579381876
Hero Member
*
Offline Offline

Posts: 1579381876

View Profile Personal Message (Offline)

Ignore
1579381876
Reply with quote  #2

1579381876
Report to moderator
"Bitcoin: mining our own business since 2009" -- Pieter Wuille
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1579381876
Hero Member
*
Offline Offline

Posts: 1579381876

View Profile Personal Message (Offline)

Ignore
1579381876
Reply with quote  #2

1579381876
Report to moderator
1579381876
Hero Member
*
Offline Offline

Posts: 1579381876

View Profile Personal Message (Offline)

Ignore
1579381876
Reply with quote  #2

1579381876
Report to moderator
1579381876
Hero Member
*
Offline Offline

Posts: 1579381876

View Profile Personal Message (Offline)

Ignore
1579381876
Reply with quote  #2

1579381876
Report to moderator
tclo
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile
March 13, 2017, 04:43:05 AM
 #6902

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
Hero Member
*****
Offline Offline

Activity: 1045
Merit: 518



View Profile
March 13, 2017, 04:43:37 AM
 #6903

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
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile
March 13, 2017, 04:45:07 AM
 #6904

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
Sr. Member
****
Offline Offline

Activity: 401
Merit: 250


View Profile
March 13, 2017, 04:46:39 AM
 #6905

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
Legendary
*
Offline Offline

Activity: 1176
Merit: 1090


View Profile WWW
March 13, 2017, 04:49:21 AM
 #6906

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.


http://www.digitalcatallaxy.com/report2015.html
100+ page annual report for SuperNET
bv68bot
Full Member
***
Offline Offline

Activity: 144
Merit: 100


View Profile
March 13, 2017, 04:49:37 AM
 #6907

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
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile
March 13, 2017, 04:49:43 AM
 #6908


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
Full Member
***
Offline Offline

Activity: 144
Merit: 100


View Profile
March 13, 2017, 04:52:53 AM
 #6909

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
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
March 13, 2017, 04:54:31 AM
 #6910

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 Offline

Activity: 364
Merit: 250


move that crypto


View Profile
March 13, 2017, 04:57:16 AM
 #6911

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?

MoveCrypto for Komodo Notary
https://komodoplatform.com/
cebb
Hero Member
*****
Offline Offline

Activity: 545
Merit: 500


View Profile
March 13, 2017, 04:57:48 AM
 #6912

is that the same bug as Zcoin had ?

u are freaking kidding me  Angry

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
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
March 13, 2017, 05:00:23 AM
 #6913

is that the same bug as Zcoin had ?

u are freaking kidding me  Angry

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
Hero Member
*****
Offline Offline

Activity: 545
Merit: 500


View Profile
March 13, 2017, 05:02:35 AM
 #6914

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
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
March 13, 2017, 05:04:12 AM
 #6915

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
Hero Member
*****
Offline Offline

Activity: 545
Merit: 500


View Profile
March 13, 2017, 05:04:43 AM
 #6916

is that the same bug as Zcoin had ?

u are freaking kidding me  Angry

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.
cebb
Hero Member
*****
Offline Offline

Activity: 545
Merit: 500


View Profile
March 13, 2017, 05:07:16 AM
 #6917

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

Stupidity? I dont think so.
Greed? Absolutely yes. Isn't that the whole point of investing in cryptos including bitcoin? Do you have some other motives? If you want a Do nothing approach you will feel better in Litecoin than KMD.
jl777
Legendary
*
Offline Offline

Activity: 1176
Merit: 1090


View Profile WWW
March 13, 2017, 05:17:19 AM
 #6918

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.


http://www.digitalcatallaxy.com/report2015.html
100+ page annual report for SuperNET
gulachov
Member
**
Offline Offline

Activity: 111
Merit: 10


View Profile
March 13, 2017, 05:17:53 AM
 #6919

Makes me laugh looking at the explorer now, so much desperate moves. LOL

You should've just contact devs white-hat. I am confident most of the people here will approve what devs are doing. And as JL said, it's technically stopping entire system, not rolling it back.
boomboom
Hero Member
*****
Offline Offline

Activity: 1045
Merit: 518



View Profile
March 13, 2017, 05:22:49 AM
 #6920

We all know that immutability is the golden rule of blockchains, believing in that doesn't make you a troll.

Rollback once, shame on you ...
Rollback twice ... there wont be one, crypto die hards wont be around ... I thought SuperNET was champion of decentralisation?

Edit, sorry to sound critical jl777, I've been a big supporter of SN since forever, just shocked at how fast rollback is invoked when better options exist.

Pages: « 1 ... 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 [346] 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 ... 872 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!