Quote from: elbandi on February 23, 2015, 05:27:23 PM

Quote from: SCSY2.0 on February 23, 2015, 04:45:58 PM

They are not forks they just need to update to the newest wallet. I am contacting them today in regards to this.

Nope, they are different fork. fork began here:

Quote

http://www.multifaucet.tk/index.php?blockexplorer=SCSY&block=103018
Block hash: 47f6c522c82e01a174405e6c64b195741da76ed891dd976e15ed4c31f2b6785e
http://www.multifaucet.tk/index.php?blockexplorer=SCSY&block=103019
Block hash: efc55b251de8af5c180a33d74e63b0df2e4073e06da396367a56e3f2a7b50654

Quote

# ./securitycoind getblockhash 103018
47f6c522c82e01a174405e6c64b195741da76ed891dd976e15ed4c31f2b6785e
# ./securitycoind getblockhash 103019
9f0e7d863a0ac8fdfa9f90e3b6d284e5bfad6b1550f8ca07febbe153ea268585

CCex has been advised 2 times by me on Skype and one time by SCSY2.0 on twitter and he didnt reply yet.
Block Explorer's owners too. Bittrex owners are the only who replied in 2 hours.

Keeping this a part, i know there was a fork. Indeed, we anticipated the release of v2.1 of the wallet due to this. Fork happened on Suprnova. One fork 2 weeks ago on CoinMiners too. But the blockchain is safe, i used protocol versioning and keyparing to exclude old wallets or wrong forks from the main chain.. We just need to reach a stable net because after those forks and wallet updates not all people updated the wallet. As proof, take a look at the network infos of Multifaucet.......What probably happened there? Multifaucet owner didnt updated his wallet..one of his peers too.. well, they have been excluded through protocol versioning and keypairing, but they were still able to connect one with the other.. well, we have PoS so.. boom.. block created ..but it's not properly a fork.

However, official block height is 104,941 - 7a519be0348903312ae68f9207a80cf0e9028fd8c3ee7f03792245d5523bff55
I hope CCex will reply asap to our requests.

Quote from: gavrilo77 on February 23, 2015, 09:08:26 PM

I cant set up trade with API keys. Every time it says Api configuration was unsuccesful

API configuration works properly.. check if you did all right and be sure to not add extra characters (like spaces).