The Mining Software disclosure? What's that?

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

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.

You accuse me of not really knowing what's going on and then in the next sentence you want to merge a dead chain? I'm sorry, but I can't take you seriously.

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.

Followed by: https://twitter.com/petertoddbtc/status/507410029306449920

"It'll be fine in the long run. #Bitcoin's had similar problems in the past after all, e.g. the "make Bitcoins out of thin air" bug."

Nice try, though.

That's utterly inane - we've made no protocol-level modifications that would cause this. If TFT's original modifications caused this and nobody noticed that has nothing to do with us.

He's correct - if we're vulnerable then the largest likelihood is that other CN coins are too.

It's also possible that one of them patched the vulnerability already, it's not like everyone talks across the fence and discusses this sort of thing.

I'm up and picking up from tacotime - just need 15 mins to orient myself.

So I happen to be around now, and you register Jung. Then someone else registers Jung1. Then Jung1982. Then Jung57. And eventually in a couple of years I have an address book that says that "Bob Simons is Jung27_AwesomeSauce"...so what have you really achieved? You're not negating the need to have address books.

There are ways to alias addresses, but this isn't one of them (see Zooko's triangle as an example of why this is a hard problem to solve).

Oh look, another sockpuppet.

It was an honest launch. I'm not going to do your homework again, but if you look at http://monerochain.info/charts/hashrate for the first 10 days it went from 936h/s to 8698h/s. At that initial stage (I've said this before) mining on one of my dedicated servers ran at around 11h/s, and an Amazon EC2 c3.8xlarge slice ran at just under 50h/s. That means that for the first 10 days you could own the network with 19 - 174 EC2 instances, certainly not infeasible or dodgy or scammy.

Also, TFT is not the "creator" by any measure of the term. The original CryptoNote developers (that wrote the original whitepaper and the initial reference implementation) can and do get our respect. However, when people are talking to us they want to know what *we* are doing, not what *was* done. The further we deviate from the reference code the more relevant our *current* work is.

You're welcome to go elsewhere if you don't like our "very strange and useless features".

Anotheranonlol, that is a very poor attempt at trolling. We all know what dga was saying about the post, because he clarified it here and it was clear in that very post -


Please try troll harder, you're an embarrassment to the troll fraternity.

He's not talking about Monero or he's utterly clueless. Per dga -

Hi guys - Jojatekok has just bounced this past us in #monero-dev, and we've helped him figure out the source of his GUI client's blockchain corruption. He's going to release a new version that will fix this - if you have had a corrupt blockchain you will need to redownload, but moving forward you should not have this happen again:)

Try 'pacman -S base-devel' - for some reason CMake isn't finding your GCC at all.

Have you got gcc 4.9+ installed?

When I was a child in primary school, maybe 10 or 11 years old, I remember we used to name-call and then taunt "I'm the rubber, you're the glue, whatever you say sticks to you!" Your response reminds me of that.

I don't really have time to participate in the back-and-forth, but I'd like to point out that I've been one of the regular editors of the Hidden Wiki since 2007. I hosted it myself for about 8 months when the official one went belly-up, and I still host a popular mirror of the current home (previously with Freedom Hosting, but I moved it on to my own tin a few months back). I've bought tons of stuff on the original SR (not drug related, never really been my scene), and I've been a regular on HackBB for ages. I have asked around, among some of the other editors on the Hidden Wiki as well as asking someone that works with Freedom Hosting, and as far as any of them can ascertain Bytecoin simply did not exist until earlier this year. I can personally attest to never having come across it in 2011 / 2012, despite still being an active Hidden Wiki editor during that time.

The hostility is because you came onto this thread and said "I read that the dev made that on purpose. Just wanted to inform you. I'm not and will Not be invested in your monero." That's pretty aggressive, I'm not surprised it invited hostility.

To quip the Godfather: "You don't ask with respect. You don't offer friendship. You don't even think to call us the core team. Instead, you come into our house on the day dga is to post his blog article, and you insult us about Monero."