Quote from: allcrypt on February 21, 2014, 04:49:39 PM

Quote from: moleculecoin on February 21, 2014, 10:44:52 AM

Quote from: allcrypt on February 16, 2014, 04:47:59 PM

Quote from: merrykate on February 16, 2014, 12:27:38 PM

ATO wallet in the China trading platform is not what you say, it is also the quark algorithm, please check data, can solve the problem

Ok, please stop with the quark algorithm crap. The algo used to mine/validate the coin has NOTHING to do with how the wallet speaks via RPC calls.

The wallet is broken, it does not handle RPC calls correctly. Until that is fixed, it cant be on the exchange.

How old are you? The wallet is not broken. Both the daemon and the Qt wallet compile fine in my environment, repeatedly without any issues. There is a bug with the Qt wallet with the pindexfirst error, but this should not effect what you are doing.

Can you describe in more detail exactly what your issue is with the json RPC interface? Are you getting an error message? Are you sure you built it correctly?

With all due respect, if you are having this much trouble building Atom and your first reaction is to spout off without QA'ing your stuff, I don't know that I would trust your exchange. Do you have any professional development experience?

Because you'not not reading.

I ALSO got it to compile and run correctly. I never complained about that. You keep posting about it's algorithim, which has NOTHING to do with the RPC interface.

Yes I'm sure I built it correctly. It compiles. It downloads the blockchain. It sends and receives coins. The RPC does not work. I know the server's RPC works because it works with 27 other wallets. Atom is the one that doesnt work. The same RPC calls that work in all 27 other wallets does NOT work with atom. The wallet returns an error.

I love how this has turned into my team not QA'ing OUR software. TWENTY SEVEN other wallets work. Atom does not. Yes, obviously our fault. Want the error? Here's the error. Fix your crappy wallet.

Error connecting to wallet ATO while polling exception 'Exception' with message 'Incorrect response id (request id: 1, response id: )' in /[path removed]/jsonRPCClient:143 Stack trace: #0 /[path removed]/poller(14): jsonRPCClient->__call('getinfo', Array) #1 /[path removed]/poller(14): jsonRPCClient->getinfo() #2 {main}

Your wallet did not respond to a simple getinfo call. All twenty seven other wallets do.

I have a shitty attitute because from the beginning I described the error, and I was told to load the blockchain, or told that it has to do with the algorithm, and now told that it's MY code not being QA'ed and us having no development experience.

From someone who does not even understand the error we are having. You have a wallet that has an error in it, that you never bothered to fix, that needs to have a blockchain file loaded to even get it to sync, yet you blame ME for another bug in your wallet.

At the end of the day, we have an exchange to run with piles of coins that have working wallets. Fix the wallet, or, just don't be on the exchange. Simple as that.

Just so you know, the people who have replied with silly troubleshooting suggestions such as quark/blockchain etc. Are not atomcoin developers, just fans, most of which are not perfect english speakers. The atomcoin dev is 'moleculecoin'. I am sure we can all just take a step back and fix the issue