Author

Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1493. (Read 4670622 times)

kbm
member
Activity: 84
Merit: 10
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:

Quote from: risto
I take back all statements that may be understood as "attacking" BBR or its dev.
legendary
Activity: 1498
Merit: 1000
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..
hero member
Activity: 658
Merit: 500
Admin of DwarfPool.com


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
legendary
Activity: 2324
Merit: 1125
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.
full member
Activity: 227
Merit: 100
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.
legendary
Activity: 1148
Merit: 1000
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...
hero member
Activity: 658
Merit: 500
Admin of DwarfPool.com
Hi All,

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

Quote
print_block 202614
block_id: <c29e3dc37d8da3e72e506e31a213a58771b24450144305bcba9e70fa4d6ea6fb>

Available diff 202974
Quote
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

donator
Activity: 1274
Merit: 1060
GetMonero.org / MyMonero.com
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.
donator
Activity: 1722
Merit: 1036
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.

legendary
Activity: 952
Merit: 1000
Yeah! I hate ShroomsKit!
My gut! This will be MOON (with capital letters) for boolberry!

Monero devs should act as fast as possible.
legendary
Activity: 1237
Merit: 1010
CZ status update on boolberry:

https://bitcointalksearch.org/topic/m.8668185
Pretty suspicious that he already knows how to solve this  Roll Eyes

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.
kbm
member
Activity: 84
Merit: 10
CZ status update on boolberry:

https://bitcointalksearch.org/topic/m.8668185
Pretty suspicious that he already knows how to solve this  Roll Eyes

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.

Quote from: CZ
So, i have time to calmly research the problem.
sr. member
Activity: 263
Merit: 250


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
legendary
Activity: 2324
Merit: 1125


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
hero member
Activity: 742
Merit: 500
CZ status update on boolberry:

https://bitcointalksearch.org/topic/m.8668185
Pretty suspicious that he already knows how to solve this  Roll Eyes

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
full member
Activity: 198
Merit: 100
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?
full member
Activity: 200
Merit: 100


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
donator
Activity: 1274
Merit: 1060
GetMonero.org / MyMonero.com
My transaction this morning is showing up there. So just to clarify, I've sent coins on the wrong chain, I need to re-down the blockchain from scratch, rescan the wallet and the coins i sent on the erroneous chain will re-appear?
Sorry to be noobish, I woke up to this drama and haven't yet got past the coffee and hangover stage.

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.
full member
Activity: 200
Merit: 100

The blockexplorer is stuck on the fork :
http://monerochain.info/


My transaction this morning is showing up there. So just to clarify, I've sent coins on the wrong chain, I need to re-down the blockchain from scratch, rescan the wallet and the coins i sent on the erroneous chain will re-appear?
Sorry to be noobish, I woke up to this drama and haven't yet got past the coffee and hangover stage.

Yes that's correct. Make backups of your wallet before you do anything.
Thanks man, on it.
member
Activity: 87
Merit: 10

Go away sock puppet.

I thought about that... And I agree with @Cheesus

Why does this not surprise me? Let me think....hmm. Umm.

Oh yeah, that's right! Because you are both BCN shills?







I was waiting for someone to post this! No doubt Hexah will just ignore this blatant evidence of anti-XMR shilling as he has done every time in the past.
Jump to: