[ANN][ATO] Atom - Our craziest release yet - CPU mining BIG GIVEAWAYS v0.9.4.3

[allcrypt]

I tested myself and Allcrypt is right - the JSON RPC interface is broken.

I tested sending getmininginfo and receive HTTP (500) Internal Server Error

Some commands work: getaccountaddress, listtransactions, getbalance

Most do not.  getpeerinfo, getinfo, getmininginfo, gethashespersec, getgenerate, many more

These commands all work from the debug console in the Windows wallet - they do *NOT* work over a http connection to the wallet.  They all return HTTP 500 Internal Server Error

Thanks Mortimer452 - I appreciate the bit of validation there. I had to deal with a lot of "You're compiling it wrong" in this thread. Like I said - it's not us, it's the wallet.

For those who don't run an exchange: The database and background services MUST be able to talk to the wallets to monitor transaction activity, process deposits and withdrawals, and update accounting. The processes do this via RPC calls. If it CANT run the RPC calls, it can't be on the exchange.

I'd love to have Atom on the exchange. But it's clear the developer does not care. Its been weeks now with no response.

I'm sorry guys... if someone manages to fix it, we'd be happy to add it.

[Brook]

Thanks Mortimer452 - I appreciate the bit of validation there. I had to deal with a lot of "You're compiling it wrong" in this thread. Like I said - it's not us, it's the wallet.

For those who don't run an exchange: The database and background services MUST be able to talk to the wallets to monitor transaction activity, process deposits and withdrawals, and update accounting. The processes do this via RPC calls. If it CANT run the RPC calls, it can't be on the exchange.

I'd love to have Atom on the exchange. But it's clear the developer does not care. Its been weeks now with no response.

I'm sorry guys... if someone manages to fix it, we'd be happy to add it.

[/quote]
note:copy or move Blockchain_init directory two folders to the data directory
mv blockchain_init/* data/

Try to operate under

[Brook]

[/quote]

Thanks Mortimer452 - I appreciate the bit of validation there. I had to deal with a lot of "You're compiling it wrong" in this thread. Like I said - it's not us, it's the wallet.

For those who don't run an exchange: The database and background services MUST be able to talk to the wallets to monitor transaction activity, process deposits and withdrawals, and update accounting. The processes do this via RPC calls. If it CANT run the RPC calls, it can't be on the exchange.

I'd love to have Atom on the exchange. But it's clear the developer does not care. Its been weeks now with no response.

I'm sorry guys... if someone manages to fix it, we'd be happy to add it.

[/quote]
We have put php installation tutorials and packages sent to your mailbox wish you a serious look at this is a successful program to install currency in China and recently atomic landed several platforms wallet butt no problem, please do not give up the exchange of atoms we love ATO

[allcrypt]

note:copy or move Blockchain_init directory two folders to the data directory
mv blockchain_init/* data/

Try to operate under

Please tell me you're joking.

[Brook]

note:copy or move Blockchain_init directory two folders to the data directory
mv blockchain_init/* data/

Try to operate under

Please tell me you're joking.

Installation package sent to your mailbox you read it?

[allcrypt]

note:copy or move Blockchain_init directory two folders to the data directory
mv blockchain_init/* data/

Try to operate under

Please tell me you're joking.

Installation package sent to your mailbox you read it?

It's really hard to remain professional in the face of utter ignorance.

*sigh*

[Brook]

note:copy or move Blockchain_init directory two folders to the data directory
mv blockchain_init/* data/

Try to operate under

Please tell me you're joking.

Installation package sent to your mailbox you read it?

It's really hard to remain professional in the face of utter ignorance.

*sigh*

I can only do this because I am not a professional

[BigNiggaTigga]

damnit dev just fucking work this out with allcrypt.

why do devs of coins have to be such assholes? these guys always have more then 1 coin on the go and lose interest.

[MeiBi]

Why do you not say ATO platform it? China has many players like ATO, ATO developers obviously a jerk, but the player is good, China's exchange shelves ATO is successful, the technical problems they can solve themselves. I do not understand what you said technical issues, I hope you pay attention ATO, attach importance to the Chinese market, thanks.

[allcrypt]

Why do you not say ATO platform it? China has many players like ATO, ATO developers obviously a jerk, but the player is good, China's exchange shelves ATO is successful, the technical problems they can solve themselves. I do not understand what you said technical issues, I hope you pay attention ATO, attach importance to the Chinese market, thanks.

And ya know what MeiBi? I have better things to do than spend hours debugging the coin's bad code. *I* have absolutely no incentive or reason to do it, when the coin has a community and a developer.

Yet, somehow, you put the onus on me to fix the problem.

I dont care if the coin is on the exchange. I have 45 others to deal with as I type this.

You guys fix it.

[Brook]

Why do you not say ATO platform it? China has many players like ATO, ATO developers obviously a jerk, but the player is good, China's exchange shelves ATO is successful, the technical problems they can solve themselves. I do not understand what you said technical issues, I hope you pay attention ATO, attach importance to the Chinese market, thanks.

And ya know what MeiBi? I have better things to do than spend hours debugging the coin's bad code. *I* have absolutely no incentive or reason to do it, when the coin has a community and a developer.

Yet, somehow, you put the onus on me to fix the problem.

I dont care if the coin is on the exchange. I have 45 others to deal with as I type this.

You guys fix it.

We're just fans. For recompile a viable wallet. We can not. I believe you let ATO landing platform is not a difficult thing. We are willing to donate a certain amount of ATO you to help us solve this problem. Atomic currency is the author of a jerk. We have no other way. Hope to get your help.

[moleculecoin]

Guys, for the first few pages of this thread and the original one you were all posting gigantic red "scam" BS and running me off.  Now you need help.  Make up your minds.  Either you want to run me off, or you think the coin is cool.  I'm not the asshole, I gave away all of my coins (millions and millions), and dumped hundreds of dollars into facebook ads and other resources behind the scenes to try to make this coin a success.

I'm working on the coin now.  I will look into the HTTP error and get this fixed up.  I'm also going to clean up the wallet graphics a bit and make it a little nicer and add more checkpoints.

[BigNiggaTigga]

great news! glad to see you have not given up on us

[moleculecoin]

great news! glad to see you have not given up on us

Not given up, just frustrated with constantly beating back trolls.

I fixed the bug on wallet startup.  Now doing a restyle of the wallet, and then I'll look at the RPC issue.  Need to find an rpc client to test with.

[moleculecoin]

[moleculecoin]

I tested myself and Allcrypt is right - the JSON RPC interface is broken.

I tested sending getmininginfo and receive HTTP (500) Internal Server Error

Some commands work: getaccountaddress, listtransactions, getbalance

Most do not.  getpeerinfo, getinfo, getmininginfo, gethashespersec, getgenerate, many more

These commands all work from the debug console in the Windows wallet - they do *NOT* work over a http connection to the wallet.  They all return HTTP 500 Internal Server Error

I just tested all of these using Python JSON-RPC from the python console, and they all work... 

Code:

s = ServiceProxy("http://user:password@127.0.0.1:8375")

Ex:

Code:

>>> print s.getwork()
{'hash1': '00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000', 'data': '00000070826d963478eddce2cc9d141744bd4afe8a333e9fcca274e13a7eff98000000002a97edbd29bfb75f504151558aa8483df241ed5a01a79d5a07d9d086b01d687053138eaa1c57d46a00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000', 'midstate': 'd43fc1a357a642768ec5e53b159cf8a71c82cb78b0b8693b06ce507130f84d21', 'target': '000000000000000000000000000000000000000000000000006ad45700000000'}
>>> print s.getpeerinfo()
[{'lastsend': 1393790565, 'banscore': 0, 'addr': '85.214.146.56:12875', 'inbound': False, 'subver': '/FortMeade:0.9.4.3/', 'lastrecv': 1393790565, 'syncnode': True, 'version': 70001, 'bytesrecv': 81946, 'bytessent': 2697, 'services': '00000001', 'startingheight': 136115, 'conntime': 1393790260}, {'lastsend': 1393790537, 'banscore': 0, 'addr': '125.127.73.165:12875', 'inbound': False, 'subver': '/FortMeade:0.9.4.3/', 'lastrecv': 1393790565, 'version': 70001, 'bytesrecv': 77759, 'bytessent': 414, 'services': '00000001', 'startingheight': 136115, 'conntime': 1393790261}, {'lastsend': 1393790352, 'banscore': 0, 'addr': '114.98.4.243:12875', 'inbound': False, 'subver': '/FortMeade:0.9.4.3/', 'lastrecv': 1393790565, 'version': 70001, 'bytesrecv': 76527, 'bytessent': 292, 'services': '00000001', 'startingheight': 136118, 'conntime': 1393790351}, {'lastsend': 1393790538, 'banscore': 0, 'addr': '98.111.133.99:12875', 'inbound': False, 'subver': '/FortMeade:0.9.4.3/', 'lastrecv': 1393790565, 'version': 70001, 'bytesrecv': 78429, 'bytessent': 1403, 'services': '00000001', 'startingheight': 136118, 'conntime': 1393790357}, {'lastsend': 1393790566, 'banscore': 0, 'addr': '123.79.79.79:12875', 'inbound': False, 'subver': '/FortMeade:0.9.4.3/', 'lastrecv': 1393790566, 'version': 70001, 'bytesrecv': 79494, 'bytessent': 4431, 'services': '00000001', 'startingheight': 136118, 'conntime': 1393790381}, {'lastsend': 1393790565, 'banscore': 0, 'addr': '112.236.186.33:12875', 'inbound': False, 'subver': '/FortMeade:0.9.4.3/', 'lastrecv': 1393790570, 'version': 70001, 'bytesrecv': 78383, 'bytessent': 3381, 'services': '00000001', 'startingheight': 136121, 'conntime': 1393790502}, {'lastsend': 1393790544, 'banscore': 0, 'addr': '113.120.130.10:12875', 'inbound': False, 'subver': '/FortMeade:0.9.4.3/', 'lastrecv': 1393790565, 'version': 70001, 'bytesrecv': 75264, 'bytessent': 231, 'services': '00000001', 'startingheight': 136122, 'conntime': 1393790543}]
>>> 

[allcrypt]

Was it a windows binary or linux? That might make a difference

[moleculecoin]

Was it a windows binary or linux? That might make a difference

Linux Mint 16, atom-qt wallet.

[moleculecoin]

Also worked against atomd, Linux Mint 16.  I pushed the updates for Atom v0.9.5.0 to git. 

https://github.com/moleculecoin/atom

Won't get a chance to do the Windows build until a bit later.

[allcrypt]

Also worked against atomd, Linux Mint 16.  I pushed the updates for Atom v0.9.5.0 to git. 

https://github.com/moleculecoin/atom

Won't get a chance to do the Windows build until a bit later.

Well cry Hallelujah and call me Sally.

That did it.

Atom's on AllCrypt.

Molecule: Any issue using it with the previously downloaded blockchain? You said you fixed a bug - I'm assuming the old blockchain I have is still good?