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.

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.

Frankly, I'm not aware of anything to prevent the exchanges front running the market. It would be profitable and very hard to prove, therefore it is probably happening.

You sound like a religious tard.

I got also in touch with HitBtc, urging them to stop withdrawals and trading. Further, I offered my time to help the Monero devs. I also decided to keep the options markets open so you can still hedge (although I am afk for the next 6 hours mostly).

Das war der Pump, nun kommt der Dump. Bis Ende des Jahres wird der Coin von seinem Hoch ungefähr 95% verlieren. Wie so ziemlich jeder Coin bisher. Ich sehe keinen Grund, warum das bei NLG anders sein sollte. Fähige Entwickler gab es schon viele - hat noch nie geholfen.

I have $0 in BTCD and yet I am still interested in the SuperNET project

Kind of odd that seandaniel was very active on the forums up until the 29th (which coincidentally is the date he got negative Trust). Then suddenly he lost all interest in posting. No new loan requests, nothing. I hope he's ok.

Hi

What is a loan you can provide based of my trust and history?

I tried other threads with no avail since lenders were awaiting for other loans to be paid first.

Purpose is an altcoin market entry. Anything under 0.25 I will not consider taking. Length is max 19 days for full assurance.
I will consider interest up to 20%.

Thank you

Please confirm I already send you payment here is confirmation

https://blockchain.info/address/1JWYj9wW8s2xRn4PPLeNRuiwEaWFxorefc

thanks for this favor feedback already given

This highlights the potential of crypto - it really is one of the last truly free markets on earth for innovators, innovation, trade and growth.
Really hope scammers/governments/regulators dont ruin the great potential of this ecosystem.

For your reference:

https://bitcointalk.org/index.php?topic=761968.0

I saw this one coming. I was the first to give him loans, but also the first to stop lending to him for too many red flags. Then several other lenders took the opportunity to loan to him once I stopped  . Either during or after his second loan with me, he:

1) stacked multiple loans, lied about it.
2) had a loan with BiPolarBob, long overdue, kept quiet about it until someone called him out.
3) started requesting large amounts in quick successions.
4) offered his forum account and LBC account as collateral.

https://bitcointalk.org/index.php?topic=701592.msg8308785#msg8308785
https://bitcointalk.org/index.php?topic=701592.msg8323803#msg8323803


Yes he had two successful loans with me, but I stopped because of those recent dodgy behaviors, and I got out in time. When someone starts offering their account as collateral or try to sell it, that should be the biggest hint to not deal. It could be dumped any time, or the new owner will scam you.