Cause the latest difficulties for some delegates to sync with the main chain,
I decided to run a
chain server on my
VPS in Greece to make it easier for all of you to download the right chain without the risk to sync on a minority fork
and much
much faster !
chain server details: 185.25.22.21:1375To sync from this chain server, first locate your
config.json file. This file will be located in the
BitShares data directory, which is placed in these locations by default:
Windows: %APPDATA%/BitShares(Try going to Start->Run and opening %APPDATA%, then open the BitShares folder)
Mac: ~/Library/Application Support/BitShares (Open a Finder window and press Command-Shift-G, then paste in the path)
Linux: ~/.BitShares
In this folder, find the
config.json file and open it with your preferred text editor (Mac users may use TextEdit and Windows users may use Notepad). In this file, find the chain_servers list, which is located by default immediately after the
default_peers list. If you do not see
chain_servers in your
config.json, your
config.json was created by an old version of BitShares. Delete
config.json and restart your client, then open it again. If there is still not a
chain_servers section, update your BitShares client.
When you have found the
chain_servers section in your
config.json, modify that section to add chain server as follows:
"chain_servers": ["185.25.22.21:1375"],When finished, there should only be one
chain_servers line (ignore the chain_server section) and make sure that this line looks like the one above and ends with a comma. Save your changes and close
config.json. The next time you start your client, it should sync from the new chain server before connecting to the P2P network.

originaly first time Nathan published a chain server...
https://github.com/BitShares/bitshares/wiki/Using-Chain-Servers