Topic: Re: [AXIOM] AxiomMemHash, Schnorr Sigs Implemented, APOS 3.0, AXH 2.0 Proposed - page 27. (Read 204903 times)
August 13, 2015, 10:36:58 PM
Congrats on being added to cryptsy.
August 13, 2015, 10:34:16 PM
The next high POW/POS period begins in 6 weeks and we ask the GPU mining crowd to also share their code with the rest of the AXIOM community and keep our coin strong.
You tried to make a coin GPU-resistant, but it seems that you are not able to do it? Hmm.. In this case please make an official release of GPU miner.
We don't have a GPU miner, there are a few users with their own private miners.
August 13, 2015, 10:31:01 PM
The next high POW/POS period begins in 6 weeks and we ask the GPU mining crowd to also share their code with the rest of the AXIOM community and keep our coin strong.
You tried to make a coin GPU-resistant, but it seems that you are not able to do it? Hmm.. In this case please make an official release of GPU miner.
August 13, 2015, 10:24:02 PM
Dev is probably waiting for everyone to dump on his buy walls so that he can later come out and say "I'm still here!" 
what I find interesting is that there's no buy support but people refuse to dump at low prices.
what I find interesting is that there's no buy support but people refuse to dump at low prices.
August 13, 2015, 06:13:07 PM
dump 
August 13, 2015, 06:09:54 PM
Well, I guess I should now try to complete the material on http://www.learncpp.com/.
However, I suspect even after completing the material, I won't be any help at all.
However, I suspect even after completing the material, I won't be any help at all.
August 13, 2015, 06:02:56 PM
What about the whitepaper and roadmap ? You are in touch whit dev and don't even report what he said about this ? Or did he just threw those miners at your mail without further explanations ?
What he means in a sugar coated way is that the dev is gone and since he is not the dev himself he is looking for devs from the community to help him. Until then it is status quo. Best case scenario is that a dev/devs step up in the next month or so before the next high block reward to sort out POS issues as well as make the algorithm more resistant to GPU miners.
That's how it looks like but I want confirmation on this.
Well, he hasn't formally quit and was very excited about the project. While the AXIOM marketcap grew, he communicated less and less each day. He promised a whitepaper last Monday, the last we heard from him was Friday. He couldn't sleep properly and woke up with lumps on his neck, supposedly. His accounts haven't been online since. This is all we know and we're working to keep the project healthy while we wait for more information.
So let me see if I have this correct.
New wallet that does not say mandatory (hard fork). So if that is the case then anyone who is using these "possible" exploited staking wallets can keep on using them.
Dev not responding. Is he Mr. Spread because we are still looking for him also.
August 13, 2015, 06:01:10 PM
This isn't Isolated to the newest wallet. Just tried the newest one because the previous one had the same problem.
August 13, 2015, 05:59:22 PM
Will I need to open ports on my firewall? If so does someone have that information?
I wouldn't trust any pre-compiled wallet that NEEDS the user to expose their computer.
Remember, you're trusting a dev that has cut off all communication and failed to provide the source code for his "updates". If this isn't a red flag for you then I'd like to inform you that you have a recently deceased Nigerian prince relative that has left you a $10,000,000 inheritance! All I need is for you to send your life savings to an un-named bank account in a conflict country to cover "processing" fees, after that your money will be sent!
Windows is starting to close ports on the firewalls during updates. Some previously working coins have experienced problems during updates.
Understand your concern.
August 13, 2015, 05:56:57 PM
Yes this has to be said too. Those miners are untrustable sadly :-(
August 13, 2015, 05:50:11 PM
Will I need to open ports on my firewall? If so does someone have that information?
I wouldn't trust any pre-compiled wallet that NEEDS the user to expose their computer.
Remember, you're trusting a dev that has cut off all communication and failed to provide the source code for his "updates". If this isn't a red flag for you then I'd like to inform you that you have a recently deceased Nigerian prince relative that has left you a $10,000,000 inheritance! All I need is for you to send your life savings to an un-named bank account in a conflict country to cover "processing" fees, after that your money will be sent!
August 13, 2015, 05:31:02 PM
Installed the axiom-qt-staketest-optimized-staking-test2.zip On a win7 32bit & 64bit system(s).
Added nodes
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
addnode=162.222.181.215
addnode=176.9.59.110
addnode=93.157.25.130
addnode=104.236.231.72
addnode=158.181.253.55
addnode=187.74.206.189
addnode=72.92.19.54
addnode=24.56.61.247
addnode=89.212.140.63
addnode=46.101.23.149
addnode=68.41.180.163
addnode=46.72.126.178
addnode=193.198.102.32
addnode=161.53.40.94
addnode=192.52.166.80
addnode=104.238.133.29
addnode=197.89.64.51
addnode=122.107.182.65
addnode=82.236.68.185
addnode=5.9.72.102
addnode=212.45.26.38
addnode=104.238.133.29
addnode=197.89.64.51
addnode=104.197.49.247
addnode=104.197.64.168
addnode=130.211.74.245
addnode=104.155.34.235
addnode=107.167.189.225
0 Active Connections to the Network.
Going to give it a few more hours...
Will I need to open ports on my firewall? If so does someone have that information?
Thank you for any help as just picked up some AXIOM.
Added nodes
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
addnode=162.222.181.215
addnode=176.9.59.110
addnode=93.157.25.130
addnode=104.236.231.72
addnode=158.181.253.55
addnode=187.74.206.189
addnode=72.92.19.54
addnode=24.56.61.247
addnode=89.212.140.63
addnode=46.101.23.149
addnode=68.41.180.163
addnode=46.72.126.178
addnode=193.198.102.32
addnode=161.53.40.94
addnode=192.52.166.80
addnode=104.238.133.29
addnode=197.89.64.51
addnode=122.107.182.65
addnode=82.236.68.185
addnode=5.9.72.102
addnode=212.45.26.38
addnode=104.238.133.29
addnode=197.89.64.51
addnode=104.197.49.247
addnode=104.197.64.168
addnode=130.211.74.245
addnode=104.155.34.235
addnode=107.167.189.225
0 Active Connections to the Network.
Going to give it a few more hours...
Will I need to open ports on my firewall? If so does someone have that information?
Thank you for any help as just picked up some AXIOM.
August 13, 2015, 05:26:41 PM
Ok thanks maybe a burnout and a goal settled too high.
August 13, 2015, 05:24:39 PM
What about the whitepaper and roadmap ? You are in touch whit dev and don't even report what he said about this ? Or did he just threw those miners at your mail without further explanations ?
What he means in a sugar coated way is that the dev is gone and since he is not the dev himself he is looking for devs from the community to help him. Until then it is status quo. Best case scenario is that a dev/devs step up in the next month or so before the next high block reward to sort out POS issues as well as make the algorithm more resistant to GPU miners.
That's how it looks like but I want confirmation on this.
Well, he hasn't formally quit and was very excited about the project. While the AXIOM marketcap grew, he communicated less and less each day. He promised a whitepaper last Monday, the last we heard from him was Friday. He couldn't sleep properly and woke up with lumps on his neck, supposedly. His accounts haven't been online since. This is all we know and we're working to keep the project healthy while we wait for more information.
August 13, 2015, 05:18:33 PM
AFAIK it was not stated that the lead dev is gone but rather has poor communication with other team members.
For the sake of the community I hope so. If the lead dev was still there, why would errm, coin management, ask for community help? I am disappointed and upset to be honest because Axiom had the promise of adding some valuable contributions to the crypto body of knowledge in the area of GPU resistance.
August 13, 2015, 05:15:41 PM
AFAIK it was not stated that the lead dev is gone but rather has poor communication with other team members.
August 13, 2015, 05:11:52 PM
What about the whitepaper and roadmap ? You are in touch whit dev and don't even report what he said about this ? Or did he just threw those miners at your mail without further explanations ?
What he means in a sugar coated way is that the dev is gone and since he is not the dev himself he is looking for devs from the community to help him. Until then it is status quo. Best case scenario is that a dev/devs step up in the next month or so before the next high block reward to sort out POS issues as well as make the algorithm more resistant to GPU miners.
That's how it looks like but I want confirmation on this.
It has been posted 3 times in bold and black above. What more confirmation do you want? Change your strategy to long term meaning a few months as at this point the coin seems to be in the same boat as several of the other "CPU" coins. Alternatively move on and come back after the next high reward phase as with inflation added after that phase the price should be around half of now due to the lack of backing by a better GPU resistant algorithm and POS3.0 which would have been a differentiating factor. Had the POS3 been developed or algorithm changed as has been waited on by the community, it would have been a different matter. The community was waiting on a knifes edge for news to either way and the news that was posted confirmed why there was a delay. Perhaps someone from the community will step up, or perhaps not.
August 13, 2015, 05:07:06 PM
What about the whitepaper and roadmap ? You are in touch whit dev and don't even report what he said about this ? Or did he just threw those miners at your mail without further explanations ?
What he means in a sugar coated way is that the dev is gone and since he is not the dev himself he is looking for devs from the community to help him. Until then it is status quo. Best case scenario is that a dev/devs step up in the next month or so before the next high block reward to sort out POS issues as well as make the algorithm more resistant to GPU miners.
That's how it looks like but I want confirmation on this.
August 13, 2015, 05:01:48 PM
What about the whitepaper and roadmap ? You are in touch whit dev and don't even report what he said about this ? Or did he just threw those miners at your mail without further explanations ?
What he means in a sugar coated way is that the dev is gone and since he is not the dev himself he is looking for devs from the community to help him. Until then it is status quo. Best case scenario is that a dev/devs step up in the next month or so before the next high block reward to sort out POS issues as well as make the algorithm more resistant to GPU miners.
It has now turned into a long term project and with no imminent improvements on the cards, it would be best to sit back and stake and focus attention elsewhere for a few months.
August 13, 2015, 05:01:39 PM
AXIOM Update August 13
There has been a lack of communication from our lead technology and algorithm developer. We share the same frustrations as the community, and expected work to be completed at a quicker pace.
Before cutting off contact two weeks ago, the lead dev played around with various exploits and succeeded in fixing some and shared some of his findings with us. The AXIOM team was given compiled optimized wallets to test around the time we made the POS 3.0 announcements. We never received the source code to these optimized wallets.
For this reason, we have decided to release two of the optimized miners that were compiled by the lead developer. We hope to work with the incredibly motivated AXIOM community to continue building the project and harden the Proof of Stake protocol against such “optimizations” as these. We suspect the developer does not want to fix POS insecurities, and we invite the community to join us in our efforts to secure POS exploits in the #axiomcrypto channel on the Freenode IRC network.
The first manipulates a POS variable and a weight check in wallet.cpp to cause coins to split and stake more often than a normal wallet.
https://bitbucket.org/AxiomCryptocurrency/axiom/downloads/axiom-qt-optimized-staking.zip
The second was delivered to us with much less of an explanation. It contains the above edits and also skips a CPU intensive “check” phase in POS. We aren’t sure exactly what this wallet is doing, but it seems to stake more often.
https://bitbucket.org/AxiomCryptocurrency/axiom/downloads/axiom-qt-staketest-optimized-staking-test2.zip
We are NOT certain what these wallets will do the network. We expect the POS difficulty to raise. If there are any network or blockchain problems we are equipped to hardfork and resolve any issues. Whatever happens, it will be interesting.
We are looking for more community involvement to aid us in reaching our development goals. This isn’t the end of the line, and with the help of the community, we can finish the project and revolutionize the Proof of Stake system by patching all possible exploits. The next high POW/POS period begins in 6 weeks and we ask the GPU mining crowd to also share their code with the rest of the AXIOM community and keep our coin strong.
More news soon.
Jump to: