Bitcoin Forum
March 19, 2024, 09:22:28 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 295 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 ... 878 »
  Print  
Author Topic: [ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B  (Read 1191645 times)
cebb
Hero Member
*****
Offline Offline

Activity: 545
Merit: 500


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

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

Posts: 1710840148

View Profile Personal Message (Offline)

Ignore
1710840148
Reply with quote  #2

1710840148
Report to moderator
1710840148
Hero Member
*
Offline Offline

Posts: 1710840148

View Profile Personal Message (Offline)

Ignore
1710840148
Reply with quote  #2

1710840148
Report to moderator
Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1710840148
Hero Member
*
Offline Offline

Posts: 1710840148

View Profile Personal Message (Offline)

Ignore
1710840148
Reply with quote  #2

1710840148
Report to moderator
1710840148
Hero Member
*
Offline Offline

Posts: 1710840148

View Profile Personal Message (Offline)

Ignore
1710840148
Reply with quote  #2

1710840148
Report to moderator
1710840148
Hero Member
*
Offline Offline

Posts: 1710840148

View Profile Personal Message (Offline)

Ignore
1710840148
Reply with quote  #2

1710840148
Report to moderator
jl777 (OP)
Legendary
*
Offline Offline

Activity: 1176
Merit: 1109


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

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
 #6883

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: 1068
Merit: 523



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

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

Activity: 111
Merit: 10


View Profile
March 13, 2017, 05:31:02 AM
 #6885

I suspect the answer, but wouldn't hurt to ask. Would it be fare to use ICO funds to buy up equal amount of KMD attacker dumped (if any)?
Sam123
Hero Member
*****
Offline Offline

Activity: 980
Merit: 502


View Profile
March 13, 2017, 05:32:49 AM
 #6886

Agreed. Let's not make it political. There was a bug. Rollback is the best option.
boomboom
Hero Member
*****
Offline Offline

Activity: 1068
Merit: 523



View Profile
March 13, 2017, 05:34:37 AM
 #6887

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.



10M is a big bounty, but rollback is worse imo, but that's just my opinion. I respect your call James, just think you'll regret it later if it ends up damaging SuperNET fatally, which it easily can. Trolls will be attached like barnacles to this 'rollback' forever now. I'm not selling though
cebb
Hero Member
*****
Offline Offline

Activity: 545
Merit: 500


View Profile
March 13, 2017, 05:37:10 AM
 #6888

I suspect the answer, but wouldn't hurt to ask. Would it be fare to use ICO funds to buy up equal amount of KMD attacker dumped (if any)?

2639 BTC were raised. At ICO price of 1 KMD = 0.00012909 BTC, If 10 million KMDs are generated by hacker that amounts to 1290 BTC.

Of cource the above calcs are approximates but still half of the Raised BTC will be gone. Not a good option.
cebb
Hero Member
*****
Offline Offline

Activity: 545
Merit: 500


View Profile
March 13, 2017, 05:39:47 AM
 #6889

On a side note, what a good day in crypto. All the alts are rising. Lets fix the bug and join the rally that has taken all good alts by storm.
jl777 (OP)
Legendary
*
Offline Offline

Activity: 1176
Merit: 1109


View Profile WWW
March 13, 2017, 05:42:56 AM
 #6890

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.



10M is a big bounty, but rollback is worse imo, but that's just my opinion. I respect your call James, just think you'll regret it later if it ends up damaging SuperNET fatally, which it easily can. Trolls will be attached like barnacles to this 'rollback' forever now. I'm not selling though
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.


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

Activity: 632
Merit: 250



View Profile
March 13, 2017, 05:43:50 AM
 #6891

People, please use 2FA on your exchange accounts. Somebody was trying to login my account but i have 2FA, so they failed.

.
PROTECTING YOUR PRIVACY
WITH BITCOIN'S HASHRATE






.
POWERS SuperNET
TECHNOLOGY
.
░░░░░░░░░▀▀▀█████████
░░░░░░░░░░░░░░░████████
░░░░▄███████▄░░░░████████
░░░░███████████░░░░██████
░░░▀███████████░░░░████░░
███▄░░░░░░░░░░▀████░░░███░░██
█████▄▄▄▄▄▄▄▄▄▄▄████░░░██░░██
█████████████▄░░████░░░░░
░░█████████████░░█████
░░░░█████████▀░░░██████▌
░░░░░░░▀▀▀▀░░░░▄████████▌
░░░░░░░░░░▄▄▄▄███████
SuperNET.org
hansen.ng
Sr. Member
****
Offline Offline

Activity: 632
Merit: 250



View Profile
March 13, 2017, 05:45:15 AM
 #6892

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.



10M is a big bounty, but rollback is worse imo, but that's just my opinion. I respect your call James, just think you'll regret it later if it ends up damaging SuperNET fatally, which it easily can. Trolls will be attached like barnacles to this 'rollback' forever now. I'm not selling though
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.


I vote rollback.

.
PROTECTING YOUR PRIVACY
WITH BITCOIN'S HASHRATE






.
POWERS SuperNET
TECHNOLOGY
.
░░░░░░░░░▀▀▀█████████
░░░░░░░░░░░░░░░████████
░░░░▄███████▄░░░░████████
░░░░███████████░░░░██████
░░░▀███████████░░░░████░░
███▄░░░░░░░░░░▀████░░░███░░██
█████▄▄▄▄▄▄▄▄▄▄▄████░░░██░░██
█████████████▄░░████░░░░░
░░█████████████░░█████
░░░░█████████▀░░░██████▌
░░░░░░░▀▀▀▀░░░░▄████████▌
░░░░░░░░░░▄▄▄▄███████
SuperNET.org
bv68bot
Full Member
***
Offline Offline

Activity: 144
Merit: 100


View Profile
March 13, 2017, 05:45:37 AM
 #6893

I suspect the answer, but wouldn't hurt to ask. Would it be fare to use ICO funds to buy up equal amount of KMD attacker dumped (if any)?

2639 BTC were raised. At ICO price of 1 KMD = 0.00012909 BTC, If 10 million KMDs are generated by hacker that amounts to 1290 BTC.

Of cource the above calcs are approximates but still half of the Raised BTC will be gone. Not a good option.

Why not make a deal with hacker, he keeps 2M and returns 8M, and then no rollback.

@hacker, you must be reading, you're going to get nothing with a rollback, make an offer
cebb
Hero Member
*****
Offline Offline

Activity: 545
Merit: 500


View Profile
March 13, 2017, 05:46:48 AM
 #6894

Rollback is the only option. And lets not worry about KMD Classic. Because that classic chain will have billions of KMD by end of week. 99% of them owned by the attacker. Good luck joining that chain.
CoollerOne
Member
**
Offline Offline

Activity: 69
Merit: 10


View Profile
March 13, 2017, 05:48:14 AM
 #6895

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

Activity: 1068
Merit: 523



View Profile
March 13, 2017, 05:49:32 AM
 #6896

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.



10M is a big bounty, but rollback is worse imo, but that's just my opinion. I respect your call James, just think you'll regret it later if it ends up damaging SuperNET fatally, which it easily can. Trolls will be attached like barnacles to this 'rollback' forever now. I'm not selling though
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.




That's too much for a bounty, but rollback is too much,

Time to make a deal with the attacker, otherwise everybody loses here ...

Open a dialogue ...
cebb
Hero Member
*****
Offline Offline

Activity: 545
Merit: 500


View Profile
March 13, 2017, 05:49:47 AM
 #6897

I suspect the answer, but wouldn't hurt to ask. Would it be fare to use ICO funds to buy up equal amount of KMD attacker dumped (if any)?

2639 BTC were raised. At ICO price of 1 KMD = 0.00012909 BTC, If 10 million KMDs are generated by hacker that amounts to 1290 BTC.

Of cource the above calcs are approximates but still half of the Raised BTC will be gone. Not a good option.

Why not make a deal with hacker, he keeps 2M and returns 8M, and then no rollback.

@hacker, you must be reading, you're going to get nothing with a rollback, make an offer

You are overestimating the impact of rollback. No one is going to talk about in a week. it is not contentious like ETH hard fork.
boomboom
Hero Member
*****
Offline Offline

Activity: 1068
Merit: 523



View Profile
March 13, 2017, 05:52:41 AM
 #6898

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.

Rollback is crypto suicide though, even one block, the precedent can never be removed.

Do a deal, the hacker found a bug, he deserves a bounty, otherwise we all lose everything. Komodo will never reach potential if immutability is lost today.
jwiz168
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000



View Profile
March 13, 2017, 05:55:03 AM
 #6899

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.



10M is a big bounty, but rollback is worse imo, but that's just my opinion. I respect your call James, just think you'll regret it later if it ends up damaging SuperNET fatally, which it easily can. Trolls will be attached like barnacles to this 'rollback' forever now. I'm not selling though
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.




That's too much for a bounty, but rollback is too much,

Time to make a deal with the attacker, otherwise everybody loses here ...

Open a dialogue ...

Not everybody as long as you had never transacted KMD beyond the block that started being exploited, you will be fine.
CoollerOne
Member
**
Offline Offline

Activity: 69
Merit: 10


View Profile
March 13, 2017, 05:56:29 AM
 #6900

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.
Pages: « 1 ... 295 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 ... 878 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!