[XMR] Monero - A secure, private, untraceable cryptocurrency

[nakaone]

CZ status update on boolberry:

https://bitcointalk.org/index.php?topic=577267.msg8668185#msg8668185

Pretty suspicious that he already knows how to solve this 

trying to induce a brotherwar is far more suspicous.

it makes absolutely no sense to disrespect bbr from xmrs standpoint and vice versa - that is probably the only argument I share with james

[1714790384]

1714790384

[wachtwoord]

I'd check ChainRadar first, as they are on the correct chain: http://chainradar.com/xmr/blocks

If it's not there, then yes, you need to re-download the blockchain, and then delete your wallet.bin (not the .bin.keys) and reopen it as normal. simplewallet will recreate that cache from the wallet creation date onwards, and since you never sent anything on the current chain your coins will still be there.

Erm, it's showing on both.

http://monerochain.info/tx/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

http://chainradar.com/xmr/transaction/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

Yes, both chains obviously accepted your transaction. This has nothing to do with on which chain you are.

To check on which chain you are check your chain height and compare it with monerochain.info and chainradar.com

[xulescu]

I'd check ChainRadar first, as they are on the correct chain: http://chainradar.com/xmr/blocks

If it's not there, then yes, you need to re-download the blockchain, and then delete your wallet.bin (not the .bin.keys) and reopen it as normal. simplewallet will recreate that cache from the wallet creation date onwards, and since you never sent anything on the current chain your coins will still be there.

Erm, it's showing on both.

http://monerochain.info/tx/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

http://chainradar.com/xmr/transaction/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

Different chains, different height. The bad fork is stuck around 202650 and the good fork is now around 202990

Edit: ninja'd

[kbm]

CZ status update on boolberry:

https://bitcointalk.org/index.php?topic=577267.msg8668185#msg8668185

Pretty suspicious that he already knows how to solve this 

trying to induce a brotherwar is far more suspicous.

it makes absolutely no sense to disrespect bbr from xmrs standpoint and vice versa - that is probably the only argument I share with james

i agree, insinuating that the devs of bbr had a hand in this attack is pretty low life with out any facts..

CZ is an excelent dev so it is not so hard to believe that he could find a solution so fast.

Stop strawmanning.

So, i have time to calmly research the problem.

[jeezy]

CZ status update on boolberry:

https://bitcointalk.org/index.php?topic=577267.msg8668185#msg8668185

Pretty suspicious that he already knows how to solve this 

trying to induce a brotherwar is far more suspicous.

it makes absolutely no sense to disrespect bbr from xmrs standpoint and vice versa - that is probably the only argument I share with james

Nowhere he says he knows how to solve it. He just says he will watch the chain and implement a workaround if he sees suspicious acitivity aiming towards a fork.

[ShroomsKit_Disgrace]

My gut! This will be MOON (with capital letters) for boolberry!

Monero devs should act as fast as possible.

[rpietila]

Noobish question: Does all this new information mean that this "tx-fork bug" only caused a simple -not very enduring- fork? That's all it did? If so, is that a major problem, or simply something that can be fixed easily?

Sometimes noobish questions are the best.

[fluffypony]

Noobish question: Does all this new information mean that this "tx-fork bug" only caused a simple -not very enduring- fork? That's all it did? If so, is that a major problem, or simply something that can be fixed easily?

Yes - BUT it could happen again, so getting to the root of the problem is essential.

[Atrides]

Hi All,

To speedup download of blockchain, I have prepared torrent file with right blockchain (onyl linux 64bit):

print_block 202614
block_id: <c29e3dc37d8da3e72e506e31a213a58771b24450144305bcba9e70fa4d6ea6fb>

Available diff 202974

2014-Sep-04 12:19:19.532192 BH: 202974, DIFF: 1256699629, HR: 20944993 H/s

Torrent file:
http://dwarfpool.com/static/xmr/monero-blockchain-202974.torrent

md5sum

Code:

2bbc74cf91dad9944707e57851e84a9b

[aikklond]

Ok serious question how can we be sure no additional harm was made during the attack?


When Feathercoin was attacked back in the day the developers did not realise the damage done for several hours....

Maybe some more research should take place before proceeding...

[bangersdad]

Hi Guys,

first off - thanks Fluffypony for sorting things out.

so i started simplewallet and it gets stuck on block 202650 - so i did not enter my password in wallet window.

should i enter my password to see if my coins are there?

so do i download blockchain.bin into monero directory and then start simplewallet again?

please i am not that technical.

[wachtwoord]

My gut! This will be MOON (with capital letters) for boolberry!

Monero devs should act as fast as possible.

Zoidberg admitted to having the same weakness in Boolberry.

[Atrides]

I'd check ChainRadar first, as they are on the correct chain: http://chainradar.com/xmr/blocks

If it's not there, then yes, you need to re-download the blockchain, and then delete your wallet.bin (not the .bin.keys) and reopen it as normal. simplewallet will recreate that cache from the wallet creation date onwards, and since you never sent anything on the current chain your coins will still be there.

Erm, it's showing on both.

http://monerochain.info/tx/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

http://chainradar.com/xmr/transaction/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

Chainradar on the right:
http://chainradar.com/xmr/block/202614

Monerochain on the wrong:
http://monerochain.info/block/ed4eea6109a1b662cf4a3bb372ed4bdee588160b0ac371c2ad78c5e603b8f2ac

[klee]

My gut! This will be MOON (with capital letters) for boolberry!

Monero devs should act as fast as possible.

Zoidberg admitted to having the same weakness in Boolberry.

So conspiracists now will say that he deliberately left it as is so they will not get suspicious of BBR attacking XMR

lol

I want to see rpietila commenting on this because he claimed that BBR may be behind the attack.

So what now Risto? You take it back or you adopt the above idea?

Paranoia mode ON in this forum..

[kbm]

My gut! This will be MOON (with capital letters) for boolberry!

Monero devs should act as fast as possible.

Zoidberg admitted to having the same weakness in Boolberry.

So conspiracists now will say that he deliberately left it as is so they will not get suspicious of BBR attacking XMR

lol

I want to see rpietila commenting on this because he claimed that BBR may be behind the attack.

So what now Risto? You take it back or you adopt the above idea?

Paranoia mode ON in this forum..

The strawman continues:

I take back all statements that may be understood as "attacking" BBR or its dev.

[Quicken]

My gut! This will be MOON (with capital letters) for boolberry!

Monero devs should act as fast as possible.

Zoidberg admitted to having the same weakness in Boolberry.

you forgot to mention the part where he says he can mitigate an attack because it takes so long and that a solution has already be thought of.

CZ didn't say he has a solution. He said he could implement a workaround:

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.

[wachtwoord]

My gut! This will be MOON (with capital letters) for boolberry!

Monero devs should act as fast as possible.

Zoidberg admitted to having the same weakness in Boolberry.

you forgot to mention the part where he says he can mitigate an attack because it takes so long and that a solution has already be thought of.

CZ didn't say he has a solution. He said he could implement a workaround:

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.

Yes, Zoidberg doesn't even say he know what the problem is. He just said it takes a while and he can mitigate it. The Monero devs can do the same thing (for example limit the number of transactions in a block temporarily or whatever).

XMR and BBR are in the same situation here.

[smooth]

Let's give the coin vs. coin sniping a rest for a while.

We're all working on addressing the issue.

[kbm]

Let's give the coin vs. coin sniping a rest for a while.

We're all working on addressing the issue.

I agree.

Answering these questions legitimately, will only let your words be used against you. This is a blatant strawman attack, financially motivated and executed technically with a blockchain spam attack. Nothing less than an act of terrorism.

Anyone giving any unconfirmed details is part of it at this point.

[GreekBitcoin]

Hey guys, good morning! Oh shi-



https://www.youtube.com/watch?v=DMSHvgaUWc8