drawingthesun
Legendary
Offline
Activity: 1176
Merit: 1015
|
|
September 04, 2014, 08:59:05 AM |
|
Why?? There has been no attack on BBR. You are over reacting. I agree, it's premature to block coins even when we have no idea what part of the code is responsible and the true nature of the attack, it might be a purely monero specific flaw.
|
|
|
|
klee
Legendary
Offline
Activity: 1498
Merit: 1000
|
|
September 04, 2014, 09:04:17 AM |
|
Probably you both want more cheap BBR lol
|
|
|
|
windjc
Legendary
Offline
Activity: 2156
Merit: 1070
|
|
September 04, 2014, 09:09:57 AM |
|
Probably you both want more cheap BBR lol
No, actually, by freezing BBR you are going to get a bigger dump.
|
|
|
|
klee
Legendary
Offline
Activity: 1498
Merit: 1000
|
|
September 04, 2014, 09:17:16 AM |
|
Probably you both want more cheap BBR lol
No, actually, by freezing BBR you are going to get a bigger dump. Let's see how it unfolds..
|
|
|
|
TooDumbForBitcoin
Legendary
Offline
Activity: 1638
Merit: 1001
|
|
September 04, 2014, 09:17:53 AM |
|
Probably you both want more cheap BBR lol
No, actually, by freezing BBR you are going to get a bigger dump. Exhibit 1 - cognitive dissonance
|
|
|
|
Breasal
|
|
September 04, 2014, 09:37:33 AM |
|
|
|
|
|
superresistant
Legendary
Offline
Activity: 2156
Merit: 1131
|
|
September 04, 2014, 09:48:57 AM |
|
I think investors should consider the cryptonote flaw. All cryptonote devs should look at this issue. Exchanges should be ready to freeze anytime.
I'm getting ready to buy if a massive dump happen.
|
|
|
|
Breasal
|
|
September 04, 2014, 09:54:45 AM |
|
Sill waiting for CZ updates: ready to buy or sell based on facts
|
|
|
|
Breasal
|
|
September 04, 2014, 09:58:06 AM |
|
Sill waiting for CZ updates: ready to buy or sell based on facts
sell where? trading is frozen... BTC/BBR open at poloniex. XMR/BBR open at poloniex.
|
|
|
|
jl777
Legendary
Offline
Activity: 1176
Merit: 1134
|
|
September 04, 2014, 09:59:52 AM |
|
Hey, there is a serious flaw in cryptonote. XMR has been the first targeted. Is BBR ready for this ?
How do you know there is a flaw in cryptonote ? I just heard about a corrupted block in monero blockchain probably following an attack. until somebody (CZ!) that understands the tx processing solves how this was done, anybody that says they know this is applicable to all cryptonotes including BBR is not telling you the truth. Now I think it is safe to say that all the non-BBR cryptonotes have this vulnerability as they cut and paste this part of the code, but CZ specifically modified the block format and that code is adjacent to this, so even without knowing it he could have easily found and fixed a flaw. Especially if it is some overflow bug. so BBR is the only cryptonote with a chance to not be vulnerable to this flaw, but until we properly identify it, we can only guess. James You need to stop the bullshit, tacotime is as capable as zoidberg to fix this and identify the issue, I actually am on good terms with zoidberg now, as I realize he isn't making up pure crap, it's you. I used the word somebody. I put (CZ!) as I think he is capable of this. I dont know the XMR devs, there are so many I have no idea who is familiar with which part. I meant no disrespect by using the word "somebody". this is a crisis for all cryptonote and I am trying to help, so I am not sure why you are making swear words at me. James
|
|
|
|
jeezy
Legendary
Offline
Activity: 1237
Merit: 1010
|
|
September 04, 2014, 10:05:15 AM |
|
There has just been an update to the situation in the XMR thread: https://bitcointalk.org/index.php?topic=583449.msg8667761#msg86677612014/08/04 Attack: Update 1
Here's what we've ascertained thus far: the "bad block" occurred at 202612. Immediately thereafter there was 202613, which also has oddities, and then at 202614 the network forked. The "A" part of the network has "c29e3dc37d8da3e72e506e31a213a58771b24450144305bcba9e70fa4d6ea6fb" as the block hash on 202614, the "B" part of the network has "ed4eea6109a1b662cf4a3bb372ed4bdee588160b0ac371c2ad78c5e603b8f2ac" as the block hash on 202614. Ultimately the "A" part won, and is the current fork. The "B" part is dead and has not proceeded beyond block 202647.
Thus the good news is that the consensus code works, and only one fork has survived. The bad news is that those on the bad fork are not reorganising back to the fork, and that is something we will need to look at fixing in future - the consensus code is so aggressive that it refuses to believe that the peers on the "good" fork are correct.
To determine if you are on the good or the bad (dead) fork, you can check "diff" in your daemon window. If you are stuck on 202647 or thereabouts, you will need to delete your blockchain and sync from scratch. I strongly suggest using the blockchain bootstrap downloads from the OP, as those are on the correct fork. Please note that the Windows blockchain bootstrap download has not been checked and updated as yet, I will be doing so in the next few hours, so we have rolled back to a Windows blockchain from a few weeks back. The Linux and OS X blockchain bootstraps are fine.
The next step is to determine how, exactly, 202612 & 202613 managed to cause this, which is what we've been doing concurrently and will continue to do. You can use Monero with caution if you are on the main chain, we will continue to update as we proceed.
NB: no funds have been lost, and there will be no blockchain rollback. If you transacted on the dead fork it was only live for about 35 minutes, so chances are little happened of relevance. Once you are on the good fork you can re-sync your wallets and any funds you sent on the dead fork will reappear.
|
|
|
|
eddywise
Sr. Member
Offline
Activity: 253
Merit: 250
Let's Boolberry
|
|
September 04, 2014, 10:05:46 AM |
|
Stop attacking each other between BBR and XMR. They both the cryptonote and have some different. We should try to solve the bug now.
|
Boolberry : @eddywise DRK: XqTbkj1hpCWBpBSvbWtzBRu5PxzJ2KoA3F BTC: 1FZYvzY4cPLwwZmU8rGPM7xGYjfjiZUmuZ Once desperately want, now desperate to forget
|
|
|
F22Raptor
|
|
September 04, 2014, 10:12:10 AM |
|
After Jl777 join the community this coin have strong power again.happy to see thatt
|
|
|
|
ripplebtc
|
|
September 04, 2014, 10:13:41 AM |
|
Zoidberg is online now!
|
|
|
|
|
ripplebtc
|
|
September 04, 2014, 10:23:54 AM |
|
Did you read the info at Poloniex Balances page? Deposit: You MUST send your deposit using the Payment ID below, or it will not be credited.
|
|
|
|
crypto_zoidberg (OP)
|
|
September 04, 2014, 10:36:22 AM |
|
Good morning dear friends!
Just awakened by the call and findout news that Monero is under attack.
I'm started looking on it now, and, well, i have 2 news! Good one and bad one!
Bad news is that Boolbery also have this flaw. (Like every Cryptonote). Good news - that this attack need pretty long period of preparation, because to achive big amount of transactions per block attackers need to move median, it's a day or more. That means that even if i see that attack is starting i have enought time to update network with workaround rule, that won't let grow transactions count per block too much to fail. Exactly that's why we have alerts feature - in case of emergency i could update network pretty quickly!
So, i have time to calmly research the problem.
Zoidberg
|
|
|
|
tuanvtau
Full Member
Offline
Activity: 179
Merit: 100
Glow Like Dat
|
|
September 04, 2014, 10:39:56 AM |
|
Did you read the info at Poloniex Balances page? Deposit: You MUST send your deposit using the Payment ID below, or it will not be credited. did you see my payment id? Transaction id: bbb186545e7c6096148b12c15037a75008fd7dccfafc70505d3dba65c072a876, size: 796 bytes Payment id: e0196fdb756e63acc886012eb7c0a365ce692c77e4d08722d06f666271a6ec77 what wroong i have?
|
|
|
|
jl777
Legendary
Offline
Activity: 1176
Merit: 1134
|
|
September 04, 2014, 10:42:17 AM |
|
Good morning dear friends!
Just awakened by the call and findout news that Monero is under attack.
I'm started looking on it now, and, well, i have 2 news! Good one and bad one!
Bad news is that Boolbery also have this flaw. (Like every Cryptonote). Good news - that this attack need pretty long period of preparation, because to achive big amount of transactions per block attackers need to move median, it's a day or more. That means that even if i see that attack is starting i have enought time to update network with workaround rule, that won't let grow transactions count per block too much to fail. Exactly that's why we have alerts feature - in case of emergency i could update network pretty quickly!
Zoidberg
so this means BBR is safe as long as you see the attack preparation? do you think you can fix the flaw before an attack could be implemented? my understanding is this attack takes days and so it can be detected I have a feeling CZ will be able to fix the code so even with this attack, it just pushes the excess tx into the next block James DTS: before you start saying that my statement is disrespecting the XMR devs, plz dont. I just said what I thought CZ could do, nothing more nothing less.
|
|
|
|
3x2
Legendary
Offline
Activity: 1526
Merit: 1004
|
|
September 04, 2014, 10:43:52 AM |
|
Good morning dear friends!
Just awakened by the call and findout news that Monero is under attack.
I'm started looking on it now, and, well, i have 2 news! Good one and bad one!
Bad news is that Boolbery also have this flaw. (Like every Cryptonote). Good news - that this attack need pretty long period of preparation, because to achive big amount of transactions per block attackers need to move median, it's a day or more. That means that even if i see that attack is starting i have enought time to update network with workaround rule, that won't let grow transactions count per block too much to fail. Exactly that's why we have alerts feature - in case of emergency i could update network pretty quickly!
So, i have time to calmly research the problem.
Zoidberg
It means we are safe atm?
|
|
|
|
|