Topic: [ANN][SOCC]: SocialCoin *** FORK COMPLETE *** - page 25. (Read 66109 times)

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

Cheers Glen, you're a star.

And Linus - another gent - epic fellas.

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

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.

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:


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 socc is a beautiful coin, because you do not add it to coinexchange.io, Bittrex, Livecoin etc.

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.

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

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

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,

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

https://github.com/novaexchange/SOCC
Clone of source-code, only change is added checkpoints for the "real blockchain".

You can see the changes in the latest commit:
https://github.com/novaexchange/SOCC/commit/043ef8ea507200dc57849971d5e32974adec11bf

We will try making our wallet reindex to the correct chain.

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

Ok, there have been a fork at block height 4965 and since we were at 7349 it seems like 2384 blocks has been rolled back.
http://blockexp.com:9996/block/67a58984c7d8c6dc7d00fcbd4490e65c185c281bf766ebf449c83380e25cd24c
http://blockexp.com:9996/block/0e5712d203779b952289c6e33e1643242f3ec2874166a19338574ebef39f1293

Anyone that has a backup of the "real blockchain"?

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.

Has there been a chain takeover? Or just a really long fork? Any dev that knows what is going on?

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