Thanks to MoneroMooo who identified the bug in cpuminer-multi. I pushed the fix to my repo
Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 244. (Read 625666 times)
August 04, 2015, 12:13:02 PM
August 04, 2015, 11:45:42 AM
I was able to identify a half dozen bad nodes which when blocked cause virtually all of the errors to stop. I don't want to post IP addresses, but if you are having trouble with your log file getting too big and you are able to block IPs in a firewall, PM me and I'll send you the list.
Most errors now come from three IP addresses.
Two of them belong to Minergate and the other to some russian private pool.
Minergate is mining on his own invalid chain as you can see on their block explorer.
August 04, 2015, 11:30:02 AM
I am useing -a cryptonight-lite
Hmm. Maybe there is a bug in it. Did you try Wolfs?
No because of Arux's posting...............
use non-AES-NI on old cpu (else you will get a message 'cpu not supported")
That be LucasJones AFAIK. Wolf's non AES-NI never worked for me in the past.
Back to work I go, ohhhh
OK, I'll take a look at lucasjones and see I can find something. Check back later.
August 04, 2015, 11:24:56 AM
I am useing -a cryptonight-lite
Hmm. Maybe there is a bug in it. Did you try Wolfs?
No because of Arux's posting...............
use non-AES-NI on old cpu (else you will get a message 'cpu not supported")
That be LucasJones AFAIK. Wolf's non AES-NI never worked for me in the past.
Back to work I go, ohhhh
August 04, 2015, 11:16:29 AM
I am useing -a cryptonight-lite
Hmm. Maybe there is a bug in it. Did you try Wolfs?
August 04, 2015, 11:13:27 AM
I am useing -a cryptonight-lite
August 04, 2015, 11:05:53 AM
Make sure with the lucasjones miner you use -a cryptonight-lite
I think with the some of the others ones it is misspelled as cryptonight-light
If you use the wrong algorithm and send bad share the pool will likely ban you, although MoneroMooo said he had temporarily disabled banning.
I think with the some of the others ones it is misspelled as cryptonight-light
If you use the wrong algorithm and send bad share the pool will likely ban you, although MoneroMooo said he had temporarily disabled banning.
August 04, 2015, 11:04:29 AM
Yes all I get with the LucasJones miner is booooo for Moneromoo's pool and for Arux's I was getting booooo and now I get "Stratum connection failed: couldn't resolve host "http" (I have http://52.8.47.33 ) followed by :3333
August 04, 2015, 11:02:50 AM
> 10k after hard fork, anyway I like this project
50k+ with GUI. 
August 04, 2015, 10:57:09 AM
i5 cpu @3800Mhz on Wolf miner (-t 4) give ~480h/s.
Lucasjones miner don't work...
Lucasjones miner don't work...
August 04, 2015, 10:54:39 AM
I was able to identify a half dozen bad nodes which when blocked cause virtually all of the errors to stop. I don't want to post IP addresses, but if you are having trouble with your log file getting too big and you are able to block IPs in a firewall, PM me and I'll send you the list.
August 04, 2015, 10:53:08 AM
I totally forgot to answer your message, was too busy yesterday 
I've send you a PM now
Yes you do need 64-bit Windows for now, so if you only have 32 bit or have <4-6 GB of RAM you better just get someone to help you move the coins.
Download the Windows wallet (.ZIP file) using the link in the first post on this thread where it says "current release windows". Extract it. Download the blockchain bootstrap using the link in the first post of this thread. I don't remember where it goes on your computer, but you can find that on the last few pages.
Open a terminal window. Launch the node (anond.exe). Wait for it to finish syncing (shouldn't take too long -- but if it starts from block 0 and takes forever then you put the bootstrap in the wrong place). Launch simplewallet.exe --generate-new-wallet. It will give you a bunch of seed words, those are your backup, so write those down on a piece of paper (keep in a safe place). It will also give you an address. That's the address you give to Poloniex.
If you have any more questions, please post them. There are many helpful people on this thread.
Thanks again, I might have to download later from Polo with someones help. I'm glad that this will probably be possible after the fork. But I'll keep trying. My girlfriend is coming over and I'm sure if I tell he rwhat i'm trying to do she will say...crypto..what? huh? What is it?...come to dinner 
I'll pop back later
Great community here too. thanks
I've send you a PM now
Yes you do need 64-bit Windows for now, so if you only have 32 bit or have <4-6 GB of RAM you better just get someone to help you move the coins.
Download the Windows wallet (.ZIP file) using the link in the first post on this thread where it says "current release windows". Extract it. Download the blockchain bootstrap using the link in the first post of this thread. I don't remember where it goes on your computer, but you can find that on the last few pages.
Open a terminal window. Launch the node (anond.exe). Wait for it to finish syncing (shouldn't take too long -- but if it starts from block 0 and takes forever then you put the bootstrap in the wrong place). Launch simplewallet.exe --generate-new-wallet. It will give you a bunch of seed words, those are your backup, so write those down on a piece of paper (keep in a safe place). It will also give you an address. That's the address you give to Poloniex.
If you have any more questions, please post them. There are many helpful people on this thread.
I'll pop back later
Great community here too. thanks
August 04, 2015, 10:23:50 AM
Reminder that if you are either CPU or GPU mining with the new algorithm you will probably want to retune the settings to maximize your performance.
The new algorithm uses 1 MB per thread instead of 2 MB so if your CPU has 3 MB of cache (a common number for mainstream i5 CPUs) you can switch from 1 thread to 3 threads! Of course hardware and performance varies, so try your own and see.
The new algorithm uses 1 MB per thread instead of 2 MB so if your CPU has 3 MB of cache (a common number for mainstream i5 CPUs) you can switch from 1 thread to 3 threads! Of course hardware and performance varies, so try your own and see.
August 04, 2015, 10:20:58 AM
Hard fork
Everything is working properly. There are a significant number of nodes that are not updated and get repeatedly dropped, which generates logs messages in aeond.log. Take care that this file does not grow too large and fill up your disk.
Since these are error messages, there is currently no log-level setting to turn them off. If the number of bad nodes doesn't decrease soon I will put out a patch to suppress these messages.
Everything is working properly. There are a significant number of nodes that are not updated and get repeatedly dropped, which generates logs messages in aeond.log. Take care that this file does not grow too large and fill up your disk.
Since these are error messages, there is currently no log-level setting to turn them off. If the number of bad nodes doesn't decrease soon I will put out a patch to suppress these messages.
Are the people running the bad nodes also seeing error messages? If they aren't reading this thread, do they know that the hard fork occurred?
Yes they will get big red error messages.
August 04, 2015, 10:04:25 AM
Hard fork
Everything is working properly. There are a significant number of nodes that are not updated and get repeatedly dropped, which generates logs messages in aeond.log. Take care that this file does not grow too large and fill up your disk.
Since these are error messages, there is currently no log-level setting to turn them off. If the number of bad nodes doesn't decrease soon I will put out a patch to suppress these messages.
Everything is working properly. There are a significant number of nodes that are not updated and get repeatedly dropped, which generates logs messages in aeond.log. Take care that this file does not grow too large and fill up your disk.
Since these are error messages, there is currently no log-level setting to turn them off. If the number of bad nodes doesn't decrease soon I will put out a patch to suppress these messages.
Are the people running the bad nodes also seeing error messages? If they aren't reading this thread, do they know that the hard fork occurred?
August 04, 2015, 09:57:50 AM
my pool seems not OK for now.
i'm investigating
[edit] false alarm, shares are counted
i'm investigating
[edit] false alarm, shares are counted
August 04, 2015, 09:55:54 AM
Hard fork
Everything is working properly. There are a significant number of nodes that are not updated and get repeatedly dropped, which generates logs messages in aeond.log. Take care that this file does not grow too large and fill up your disk.
Since these are error messages, there is currently no log-level setting to turn them off. If the number of bad nodes doesn't decrease soon I will put out a patch to suppress these messages.
Everything is working properly. There are a significant number of nodes that are not updated and get repeatedly dropped, which generates logs messages in aeond.log. Take care that this file does not grow too large and fill up your disk.
Since these are error messages, there is currently no log-level setting to turn them off. If the number of bad nodes doesn't decrease soon I will put out a patch to suppress these messages.
August 04, 2015, 09:52:22 AM
http://52.8.47.33:8080 switched on on POW algo.
warning: miner Wm..............................................................D2w2qy, you must switch you miner! your shares are not counted
warning: miner Wm..............................................................D2w2qy, you must switch you miner! your shares are not counted
August 04, 2015, 09:14:26 AM
Additionally, the difficulty will go up, so the pool settings will have to adapt too as it does (mostly starting diff I guess).
Yes the difficulty on the coin will instantly go up by a factor of 8 IIRC. I have no idea how long the pool software will take to adapt to that.
August 04, 2015, 09:09:13 AM
I just disabled banning on my pool, and will reenable it some time after the fork. This should let people switch a bit before or after without issues caused by temporary bad hashes.
Additionally, the difficulty will go up, so the pool settings will have to adapt too as it does (mostly starting diff I guess).
Additionally, the difficulty will go up, so the pool settings will have to adapt too as it does (mostly starting diff I guess).
Jump to: