Quote from: Biomech on April 22, 2015, 08:33:54 PM

Quote from: richiela on April 22, 2015, 06:55:56 PM

Quote from: coinsolidation on April 22, 2015, 02:38:21 AM

Quote from: richiela on April 21, 2015, 09:56:25 PM

Quote from: Biomech on April 21, 2015, 08:32:18 PM

Quote from: richiela on April 21, 2015, 07:14:33 PM

Looks like the coin has forked again... Dev, can you please provide a bootstrap? We have disabled the wallet until we are back on the correct fork.

thanks
richie@bittrex

I can't do it today, as I am up to my eyeballs, but I can make you a bootstrap. It's been on my to do list anyway.

However, I'm not seeing any forking with the new client. Can you give us some details, please?

I've deleted the chain and currently resyncing from scratch, so I don't have the exact block number anymore, but our blockchain basically started rejecting blocks with too little proof.

new best=a7cb18858ca68f1f34eb7c08def0ceed4e790549c1560ba6e2e643d484038f1e height=1072687

looks like multiple clients are stuck in multiple places

gmccoin getpeerinfo| grep hei
   "startingheight" : 1070497,
   "startingheight" : 1070306,
   "startingheight" : 1091630,
   "startingheight" : 1073298,
   "startingheight" : 1073298,

gmccoin getblockhash 1073283
c269a09a04d3b7a57da235a1a569ea0e520b0fc5164990c8792c2ad94c6b731c

It synced up to here and stopped again... If a solution isn't found I am delisting the coin. I have spent a better part of 4 weeks trying to get this back online and healthy.

richie

Are you running version .0.9.4 or higher?

If not, you WILL have issues. I currently have three daemons running on two servers, all with no issues, all synced from zero. One is the block explorer at http://gmc.cryptocloudhosting.org:3001/, the other is the daemon for the pool at gmc.cryptocloudhosting.org/GMC/public, both of which can be publicly viewed. My personal wallet as well, syncs without issue. If the version number is correct, then I really don't know. I'm making a bootstrap very soon (later today) and will see to it that you have the link. But it should sync from zero without issue, other than it will occasionally freeze in the ~500,000 range, in which case restarting the daemon cures it. It might do that two or three times before fully syncing, but that's the ONLY issue I've had, and frankly haven't seen that since we got the client generally released last week.

I appreciate your efforts, and we'll do our damnedest to resolve it. If you'd like to communicate with me directly, send me a PM and I will give you my Skype ID. You might also want to contact Coinsolidation, as he did the recoding.

EDIT: Try commenting out your addnodes and putting this line in : connect=gmc.cryptocloudhosting.org:40002
That's the Block Explorer's daemon.

EDIT 2: Bootstrap is done, being tested right now. As soon as I'm certain all is well with it, I'll put a link up, and have Shavers update the OP.

"version" : 90400,
"protocolversion" : 70005,
"walletversion" : 60000,

running the latest version as far as i can tell. I'm resynced again, and in line with the blockexplorer. Will reopen wallet and market. I've added you as a node ... Let's see if it will stay synced.

Thanks,
richie@bittrex