Just setup a fresh linux vm in under 10 minutes, syncing now.
Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-22-generic x86_64)
#!/bin/bash
curl -sSL https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.6-x86_64-unknown-linux-gnu.tar.gz -o crown.tgz
tar xzf crown.tgz --no-anchored crownd crown-cli --transform='s/.*\///'
sudo mv crownd crown-cli /usr/bin/
rm -rf crown*
fully synced in less than 30
{
"version" : 120061,
"protocolversion" : 70040,
"walletversion" : 61000,
"balance" : 10000.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 1250390,
"timeoffset" : 0,
"connections" : 12,
"proxy" : "",
"difficulty" : 13494045.78497791,
"testnet" : false,
"keypoololdest" : 1486869903,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,
"errors" : ""
}
Sat Feb 11 22:49:38 EST 2017
Found the fix and the issue for the hot throne, nothing too major and I can release a client fix for it shortly. Going to talk to the team to see if they would like to make a release for it or not, but it will not require everyone to update. to put everyones mind at ease
https://github.com/Crowndev/crowncoin/tree/fix-hot-throneAlright guys just going to put this out here. If you find an issue with something and your certain your config is okay. Then check the Dash github.
https://github.com/dashpay/dash and type a short statement explaining the issue. With the last one being "hot node" if you search that you'll see that there was a PR merged into dash 0.12.1.x to fix the issue with hot nodes.
It's a bit easier on me, since I to try and recreate and track the issue before I consider it an issue. If someone points me right toward the fix it's much easier to get implemented at a quicker pace