[ANN][SOCC]: SocialCoin *** FORK COMPLETE ***

[SDHarley]

*** 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.

[Bitgenius777]

Suggestions:
We need a Slack community channel
We need a proper Facebook Group and Fanpage
We need an active Twitter account
We need active reddit, steemit, medium, twitter and youtube contributors
We need a proper functioning website
We need a proper written white paper
We need a proper bounty campaign thread and airdrop
We need a proper mining pool
We need maybe a github

Please, send me some coins from this project as a bounty for the suggestions  . Thank you so much!!! 

Follow me on twitter to get updates about this project: https://twitter.com/Ontologized

Dev please contact me for bounty proposals,

Wish you all the best,

[SDHarley]

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

[the-doctor]

My coins are on novaexchange and yobit should i do something?

[SDHarley]

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.

[T1230]

SDHarley socc is a beautiful coin, because you do not add it to coinexchange.io, Bittrex, Livecoin etc.

[linusdunkers]

Summary:
Someone has been mining SOCC on a private network since block 4964. When the official chain was at height 5147 they released a longer chain that was about 7300+ height causing a reorg och the chain (REORGANIZE). This caused the 183 blocks that had been found since block 4964 to be rolled back (orphaned, -1). This can be seen in the debug.log below:

Code:

2017-07-21 16:46:29 SetBestChain: new best=bc6e368398fca1b3964b74749f5b72844136d79045fe286755c0536f9003a2dd  height=5147  log2_work=52.822704  tx=9028  date=2017-07-21 16:45:36 progress=1.000000
2017-07-22 15:07:21 REORGANIZE: Disconnect 183 blocks; 0cb951727534c9071b15d7006b607685604ae944c45e9992b3a54781c2b25fd1..
2017-07-22 15:07:21 REORGANIZE: Connect 2236 blocks; ..9ef55f32c75070247f8d59fa484fa5af2aa39296becd68310fd7e5499079e8c1

I made a clone of the SOCC source code and added some checkpoints from the original chain:
https://github.com/novaexchange/SOCC

Later we managed to get two nodes to sync back on the original chain using the modified wallet with checkpoints.
Anyone can now get connected to the original chain using the modified wallet above and adding the following node:
addnode=217.175.119.126:18645

Once the mining catches up all nodes will automatically be "reorged" back to the original chain.

[SDHarley]

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.

[glen123]

hi !

just came back from Party and really sleepy . saw that Pool Mails flooding my Smartphone .

after a really needed sleep i will check tomorrow


So actual Pool in Maintenance .


Glen

[SDHarley]

Cheers Glen, you're a star.

And Linus - another gent - epic fellas.

[glen123]

ok, before Breakfast a compile

./socialcoind getinfo
{
    "version" : 1000000,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 1507.96374647,
    "blocks" : 5147,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 4344.25246804,
    "testnet" : false,
    "keypoololdest" : 1500010481,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""


with the newest SRC from nova incl checkpoints

will test pool soon

Glen
edit : just pointed 1GHS to break Block 5147 with this incr. high Diff 
4,344.25246804
Difficulty

we will see .
Cheers

[glen123]

Ohh, no cheers . To much beer and whisky yesterday
Hicks

Need a BIG mens  breakfast
Damned Headache :-)

[SDHarley]

Sounds like a proper party

[linusdunkers]

Now mining for block 5148 on http://gcpool.eu/p3349/public/
Pool Hash Rate right now is almost 14 GH/s and it should take about 20 minutes to find next block.

[SDHarley]

Gone already

[glen123]

linus

aehm 100 GHS ?

ok , lil Oversized . but OK .

 

100,106.24 MH/s

Pool Hashrate

[Sowik]

Would be easier just to upload the whitepaper to google docs and make it public so everybody can see it, some people including me don't like downloading stuff or don't have the Microsoft office tools on their PC.

[linusdunkers]

Haha, sorry, one 0 too much used 10 GH/s to find one more block and now about 5 GH/s to make diff go down slowly

linus

aehm 100 GHS ?

ok , lil Oversized . but OK .

 

100,106.24 MH/s

Pool Hashrate

[SDHarley]

Well if you're going to do a job, do it properly!

And point taken on white paper - we are busy with the blockchain repair currently though.

[SDHarley]

*** FORK UPDATE - RESOLUTION - INSTRUCTIONS - ACTION IMMEDIATELY***

Linux users - Compile the new wallet from source https://github.com/novaexchange/SOCC and ensure you delete your blockchain, before using the 'connect' command in your conf as detailed below.

Windows users

1) Delete your blockchain files in AppData\Roaming\Socialcoin

To get to this directory, as I'm sure you all know, use %appdata% in the run box, and open up the 'Socialcoin' directory.

DO NOT DELETE THE wallet.dat FILE
DO NOT DELETE THE socialcoin.conf file

All other files and folders should be deleted.

2) In socialcoin.conf file, add the following line AND DELETE PREVIOUS. This is critical, and without this addition and removing the blockchain, the fix will not work:

connect=217.175.119.126:18645

So your conf file should now look like this:

rpcuser=<your local wallet address>
rpcpassword=x
rpcallowip=127.0.0.1
rpcport=18646
port=18645
listen=1
server=1
connect=217.175.119.126:18645

MAKE SURE YOU DELETE ANY EXISTING ADDNODE LINES. Once we issue recompiled wallets, the old nodes can be added once again.

Note that the above is a temporary solution whilst we also work on issuing recompiled Windows wallets (I am away from home currently will get to this ASAP). This will be done ASAP but for now, removing the blockchain and mining with the above settings should work successfully. To aid mining, connecting to GCPOOL is the suggested solution as part of the resolution to this issue is mining the blockchain until the height exceeds the height of the hacked chain. Indeed, to secure the network properly we need people to start mining on this pool please.

Any questions, post them here.

Massive thanks to Linus on the Nova Exchange for his dev assistance in this. And to Glen on GCPOOL for clearing his hangover incredibly quickly and recompiling his pool

Cheers, Mark.