Somehow, I forgot to post bootstrap.dat links --

I order to import via bootstrap.dat, you must place the file within your client's data storage directory.

Windows default: %APPDATA%/Xencoin
*nix default: ~/.xencoin
OS-X default: ~/Library/Application Support/Xencoin

When the client is started, it will auto-detect bootstrap.dat and import the blockchain.

When I tested this on both client versions I have, it worked without issue - but the older 0.6.3.x clients are slow as sin on import - most likely from lack of optimizations on SSE/SCRYPT that newer clients have (among other issues). 

When import is complete, bootstrap.dat is renamed bootstrap.dat.old (or something to that effect) - it can then be deleted.

Files are stored at Mega, in two archive formats - 7Zip (windows) and a gzipped tarball (*nix/OS-X)

xencoin-bootstrap-20150322.7z: https://mega.co.nz/#!YIZE3LZA!qBn37YIpBSyMlJFb6ZOrY0ObnHGVK4TM01G1f-J-Fr4
xencoin-bootstrap-20150322.tar.gz: https://mega.co.nz/#!tI5jVAjC!9qDn_rSg1AcNFXS4iDA8sZrJxWSDLWSh2QxQ6frDAb4

Updated source available at https://bitbucket.org/Hobbyistpool/rabbitcoin

Added Checkpoints, Updated client name, Updated CLIENT_VERSION_MINOR.

Differences can be found here https://bitbucket.org/Hobbyistpool/rabbitcoin/commits/839e7b5538821553dbc7b627ffd078ccbb647d5f?at=master

Hope to have Windows/Mac wallets soon.

That is the risk we all take without a DEV and a properly checkpointed client.  I'm in the process of switching back to the old chain.

Appears Doge had a similar problem https://github.com/dogecoin/dogecoin/issues/250

Is there a block explorer for the old chain?   it appears https://prohashing.com/explorer/Rabbitcoin is on the new chain.

The community needs to agree on what is the official chain.

1st chain
            (1400000,  uint256("0xe7330bf983cebb0f921079f774e22af2032b367162427bda37c9dba9acfa41ce"))
            (1420000,  uint256("0xadea4fc3a47702cc7a109047ca76054875e54d06b5e5876094d9e0ead73c5fac"))
2nd chain
            (1400000,  uint256("0x33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074"))
            (1420000,  uint256("0x5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6"))

Yes, The pool was on another fork and behind in block count.  I re-synced it last night/today and it's joined the other nodes below at Current height 1450594.

        "addr" : "115.236.88.86:17020",
        "addr" : "204.11.237.233:38721",
        "addr" : "98.115.147.74:17020",
        "addr" : "122.233.243.196:17020",

The chain I was on was causing DB exceptions during reorgs. This chain appears stable. 

My apologies for any lost coins caused by the other chain. 

Can someone sanity check the following block hashes?

rabbitcoind getblockhash 1400000
33b81cf2473bfb10ee6b0defb3bb68971dafef7249cb97985036fcfff6136074

rabbitcoind getblockhash 1420000
5f1dac3cbbc606053cf44d7cf762d26c1c0cbfddb7b337ba70bc1e5ea8ec0bb6

rabbitcoind getblockhash 1450594
b0f6550c9bde9b7b8e2c8a045a500b8cf9d3334166313ebf4db9853c27f35b06

 

Did you add the seed nodes in the sample config found on the first page of this thread?