Gone already

Sounds like a proper party

Cheers Glen, you're a star.

And Linus - another gent - epic fellas.

Cheers Linus. As discussed offline, we will work to get the wallet source compiled and ask the community/users to download the updated wallets, specify the new checkpoints in the conf file, and either start with an empty blockchain (probably easier if you're not technical - just delete the blockchain directoy from app data but be careful not to delete your keys file where your coins are stored) or run the updated wallet with -resync in the parameter line (i.e. in the shortcut).

All exchanges, pools and users need to make note of this and ensure we are no longer mining on the compromised (i.e. hacked) blockchain.

No, leave them there. At this time, moving the coins around only worsens the chances of you getting them back. The coins on Yobit (if they are already confirmed) are safe. The coins on Nova are safe too in the sense that they are not going anywhere. Access to them and the ability to trade them will follow the (hoped for) successful rebuild of the blockchain we are currently working on.

Edit to add - I do not recommend anybody attempts to transfer coins out of Nova. They won't go anywhere and you risk losing them. Just sit tight.

Stop spamming proper threads with this crap. Or, in the unlikely event you are actually serious, check the OP muppet.

*** FORCED BLOCKCHAIN FORK - UPDATE ***

Statement from the SocialCoin Dev:

This evening, with the affable guys at Nova Exchange, we have identified a blockchain fork of SOCC at approx 1pm on Saturday, July 15th (I guess we should be flattered that the coin evidently is deemed of value sufficient to warrant an attack). This explains current wallet sync and account lock issues, both locally and on exchanges. It also explains the intense activity on the blockchain this afternoon, as the attackers activated their fork today.

The long and short of this is, as follows (none of this will news to the attackers, hence stating what we are going to do doesn't tell people anything they don't already know):

1. A checkpoint has been added to the source code, which will now be recompiled. This we are working on with a view to completion ASAP.
2. The updated source code will be used to reboot two nodes for the coin and kick off the blockchain to the height just prior to the attack.
3. We are obtaining the block hashes impacted (I am not revealing the number of impacted blocks at this time) with the intention of manually adding those to the blockchain once the two nodes in #2 cease their sync.
4. From there, several options are available to us. And these are currently being evaluated. The underlying principle here is the need to ensure:

    a. Users do not have to re-download the wallet
    b. Users do not have to run special commands in order to continue using SOCC

That's all I am going to say for now. More info soon but lack of comms does not equate to lack of activity so please bear that in mind.

We will work to get the SOCC blockchain back to 100% ASAP and the aim is to ensure that we're back to 100% capability by close on Monday 24th, perhaps sooner.

Thanks.

To say your assistance with this is appreciated is putting it mildly! Thank you.

Block explorer now back to 4979, datestamp July 15th.

The strange coincidence is that one of the (original) nodes seems to have gone offline this afternoon. The timing of that is too bizarre for my liking so looking at that first.

The hosted node will be checked for this. I will be looking into this so if I don't respond either here or on Slack, that is the reason why. Will still be around though

Well one scenario is that somebody threw a massive rented rig at the blockchain, which kicked over the block at the time, then hoovered up the remainder for an hour or so. Then the resultant 20k coins they amassed have since been sent to an exchange, which may have caused a concern - not sure. Still checking on it.

All this is on the Slack. But will update there and here when we know more.

Right now I'm more interested in the block activity this afternoon and in ensuring the blockchain is all present and correct.

As per the white paper (the link on the website for which I need to change as it first requires Google sign-in it would seem), we are shortly to release mobile wallets for testing, plus have the coin mentioned in a UK magazine.

Point taken on $SOCC and I'll start using it. We seem to have raced through hundreds of blocks today, possibly orphaned blocks on one pool and failed confirms on Nova so will be looking at this and will advise if anything strange is found.

Yes sorry, white paper and dev intro vid indeed are available via www.social-coin.co.uk

Apologies for not updating the thread, I've been looking at ways this evening of trying to speed up the blockchain. Will update OP now also.

Yes 21.00 CET this evening.

I was aware that they'd reduced the cost of a listing, but not that they'd changed also to a donation model. Will have a look.

This should be fine now given the blockchain activity overnight.

Good spot, edited the OP.