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

Erm, it's showing on both.

http://monerochain.info/tx/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

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

Erm, it's showing on both.

http://monerochain.info/tx/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

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

Pretty suspicious that he already knows how to solve this 

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.

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.

Go away sock puppet.

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.

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

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

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

Why do you keep throwing good money after bad? Monero developers have confirmed their incompetence numerous times, and you still continue investing in XMR. I understand that you’ve put a lot of effort and money in it but you should not be tied up to the sunk costs.

It seems that you've been lured into thinking that Monero is going to the moon when actually it is doomed. I think you should rethink your commitment before you've lost even more.

Actually you don't know what's really going on with the coin. "B" part is alive but has few miners on it. How will you merge two parts?

Why do you keep throwing good money after bad? Monero developers have confirmed their incompetence numerous times, and you still continue investing in XMR. I understand that you’ve put a lot of effort and money in it but you should not be tied up to the sunk costs.

It seems that you've been lured into thinking that Monero is going to the moon when actually it is doomed. I think you should rethink your commitment before you've lost even more.

Why do you keep throwing good money after bad? Monero developers have confirmed their incompetence numerous times, and you still continue investing in XMR. I understand that you’ve put a lot of effort and money in it but you should not be tied up to the sunk costs.

It seems that you've been lured into thinking that Monero is going to the moon when actually it is doomed. I think you should rethink your commitment before you've lost even more.

Now I realize what was the reason for the mid-move turn back at 510 and the quite strong selling towards 400, which was not supported by fundamentals or anything.

The attackers have taken a short position during the decline (causing the decline), and when they run out of coins, the price also stopped declining. When it started going up, it was the time to attack.

Now if the holders sell their coins so that the price drops to below 400, without corresponding buyers except the attackers, then the attackers have won financially, fleecing the community. (The community has also won, because the bug was fixed and attack repelled.)

I pledge 1000 XMR to the devs for their ongoing good work, and BTC100 will be used to buy moneros in the exchange without further warning if I deem that the scamattackers are about to get too fat a profit from their attack.

Your wallet should sync to the correct fork if I correctly understand what fluffypony has said. If you're concerned about ending up on the wrong fork then back up your blockchain file before starting to sync.

Actually you don't know what's really going on with the coin. "B" part is alive but has few miners on it. How will you merge two parts?

I haven't yet synced AT ALL and am before the faulty blocks and the fork point (I don't have it running now). I want to make sure I get on the right fork when I sink: how can I do that?

2014/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.