 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
|
I received a modified wallet source for Molecule from China with translations and I believe some graphic updates. I'm going through it now and will merge what I can before producing the new build.
Also I have received some developer donations and just wanted to say thank you for the support!
|
|
|
|
|
Been having some trouble with my build server. Once it is resolved I'll get the wallet update built.
|
|
|
|
|
Just wanted to post an update, I will drop an updated wallet tonight. I was going to drop it yesterday but was waiting on an email response with some possible additions. I got a list of Chinese nodes that I will put a few into the wallet, should improve the experience for users in Asia.
Also some website updates coming.
|
|
|
|
|
I will look into it. Thanks for the data.... It really should not be bombing out on checkpoints though........ hopefully it is something like a copy/paste issue.
|
|
|
|
|
If anybody has any requests for the QT wallet update, please post here.
Also, I know that we have a HUGE, MASSIVE amount of Chinese users of Molecule. According to BinTray there are over 4,500 downloads of the wallet from China. If you have DNS names for any reliable nodes in China, I can add them as seeds into the wallet. It would probably help connectivity.
|
|
|
|
|
I haven't experienced any issues like that. You could try running it with the -debug option and see if anything interesting is posted to the debug.log when you have the problem. My experience has generally always been very strong connectivity, stronger than other coins usually... I know there were a few hundred peers connected on one of the nodes when I checked yesterday (I have it upped over 125).
|
|
|
|
WOW
Thanks so much for doing all this work
Im glad everything has worked out! this is fantastic news!
No prob. I'll try to stay on top of the coin more, if that is what the community wants. It would be great to see the Atom users come together with ideas to build awareness of the coin. |
|
|
|
Also worked against atomd, Linux Mint 16. I pushed the updates for Atom v0.9.5.0 to git. https://github.com/moleculecoin/atomWon'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? I haven't made any updates to Molecule yet. For Atom, there should be no issue using the previously downloaded blockchain. There are a lot of checkpoints in there now, so if there were any issues you would get a sync error. If it ran for you without error, that means it successfully scanned and tested the blockchain. |
|
|
|
Also worked against atomd, Linux Mint 16. I pushed the updates for Atom v0.9.5.0 to git. https://github.com/moleculecoin/atomWon't get a chance to do the Windows build until a bit later. |
|
|
|
Was it a windows binary or linux? That might make a difference
Linux Mint 16, atom-qt wallet. |
|
|
|
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...  s = ServiceProxy("http://user:password@127.0.0.1:8375")Ex: >>> 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}]
>>>
|
|
|
|
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. |
|
|
|
|
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.
|
|
|
|
|
Hey guys. I will post an updated QT wallet soon.
Also, whoever "MOL Elites Club" from China is...I have been getting tons of e-mail forwards from you via the contact form on the website - the form is an auto-forward. Please PM me here or just post in the thread.
This coin still remains really popular in China. I never imagined it would have the popularity that it does. Just check the download stats on Bintray....every day its getting pulled by the hundreds.
Developer Donations Address:
K3LhXmZeougH7XUr1ppkKd15A53o6iBgmJ
|
|
|
|
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? |
|
|
|
|
Its been quiet, but some activity behind the scenes. I have been in contact with a lot of chinese and I supplied a bunch of coins to some Chinese for promotion over there. I've got a bunch of requests from them to work through and do a new wallet build. I figured I would give the coin some breathing room and let the incessant trolling and snipe attacks die down.
There has been consistent downloads of the wallet so there is still interest.
Things like games and services will come down to what the community wants to do and where they want to take it. I have had a ton of signups on the atom website, but no real participation it seems most are just lurking.
I need to work up a strategy to restart the engine on this and get it moving while ditching the trolls with the teenager act.
|
|
|
|
|
This could actually be a really valuable experiment. I don't know that anyone has tested this scenario yet in the wild. Maybe Quark comes closest, but not really the same. What happens when mining reaches the end and Tx operation takes over? Well, now we can find out... I like it.
|
|
|
|
The number of wallets are huge now. There are 91787 confirmations for my earliest record, so the active wallets may be about 100k, and the number is still growing quickly.
We are still waiting for an exchange...
sry but that was a bit funny XD the number of confirmation is not the number of users/wallets, its the blocknumber, every new found block in the chain confirms the blocks before ... Oh my naive understanding  Then where can we find how many active users/wallets?? Its decentralized and peer-to-peer, so there's no central monitoring place that can count that info... you can kinda judge by how many peers you are able to maintain connection to. Also, the download stats: https://bintray.com/atom/molecule/Molecule?from=statisticsThere's a LOT of downloads of this wallet. |
|
|
|
This coin is really going to be something special in 2014. I equate Unobtanium with Bentley Mulliner edition in my mind. I get in my Bentley and in my pocket I've got my Unobtanium black card. :-)  I don't have a lot of Unobtanium yet. Mining so far has only gotten me a couple of coins. Would like to get over 100 before this thing really rockets. I believe fyrstikken's prediction. This could be worth 8 BTC. It is all positioning. |
|
|
|
|
