To whoever holds these addresses:
Wmt2443c7[...]
You've been using an old miner since the fork. Please update. You're hashing for nothing.
WmsM331a[...]
At least one of your rigs is hashing with an old miner and is hashing for nothing.
Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 241. (Read 625666 times)
August 06, 2015, 06:06:47 PM
August 06, 2015, 03:46:37 PM
Claymore GPU Miner NsGpuCNMiner
don't work anymore on http://aeonpool.mooo.com/ and http://52.8.47.33:8080/
only work on minergate ?
mining on minergate is valid or not ?
don't work anymore on http://aeonpool.mooo.com/ and http://52.8.47.33:8080/
only work on minergate ?
mining on minergate is valid or not ?
Claymore has not been updated. He said he will probably do it, but has not given a schedule.
Probably yes, but not right now because I don't have any free time currently 
Minergate has said they are in the process of updating. For now you will need to use either NVIDIA GPUs or CPU at http://aeonpool.mooo.com/ and http://52.8.47.33:8080
August 06, 2015, 03:39:49 PM
August 06, 2015, 03:39:30 PM
Claymore GPU Miner NsGpuCNMiner
don't work anymore on http://aeonpool.mooo.com/ and http://52.8.47.33:8080/
only work on minergate ?
mining on minergate is valid or not ?
don't work anymore on http://aeonpool.mooo.com/ and http://52.8.47.33:8080/
only work on minergate ?
mining on minergate is valid or not ?
August 06, 2015, 09:32:02 AM
Hello,
does anybody know, is it possible to find bootstrap for Windows-x64 at any respectable place, not @ Mega?
does anybody know, is it possible to find bootstrap for Windows-x64 at any respectable place, not @ Mega?
August 06, 2015, 04:39:12 AM
Thanks smooth (and Arux for the win bins!)
What about unbanning the offending peers? Will the bans have some automatic expiration time, or is there some manual process by which one can clear the active bans? I'm thinking that some expiration time would be reasonable, as the ideal situation is that all those peers eventually get upgraded, though I'm assuming these are not malicious nodes.
What about unbanning the offending peers? Will the bans have some automatic expiration time, or is there some manual process by which one can clear the active bans? I'm thinking that some expiration time would be reasonable, as the ideal situation is that all those peers eventually get upgraded, though I'm assuming these are not malicious nodes.
Yes the bans automatically expire after 24 hours (but if the peer continues to misbehave it will just get banned again quickly). Again that could vary based on the severity of the offense but for now the simple approach should be good enough.
EDIT: one of my test nodes has been running the ip banning version for 24 hours and I see that the unbanning does work.
August 06, 2015, 04:37:38 AM
Thanks smooth (and Arux for the win bins!)
What about unbanning the offending peers? Will the bans have some automatic expiration time, or is there some manual process by which one can clear the active bans? I'm thinking that some expiration time would be reasonable, as the ideal situation is that all those peers eventually get upgraded, though I'm assuming these are not malicious nodes.
What about unbanning the offending peers? Will the bans have some automatic expiration time, or is there some manual process by which one can clear the active bans? I'm thinking that some expiration time would be reasonable, as the ideal situation is that all those peers eventually get upgraded, though I'm assuming these are not malicious nodes.
August 06, 2015, 04:29:27 AM
EDIT: Patience pays off 
Just seen the following message:
2015-Aug-06 10:08:00.568484 [P2P7]Ip xxx.xxx.xxx.xxx blocked.
Just seen the following message:2015-Aug-06 10:08:00.568484 [P2P7]Ip xxx.xxx.xxx.xxx blocked.
Yes that is exactly what is supposed to happen. Multiple offenses are required to get banned. (In the future I may modify this to depend on the severity of the offense; some DoS attack patterns may justify immediate banning.)
The peers vary in how rapidly they reconnect. I think this is a function of the size of each node's peer candidate list (since the p2p code only tries to connect to one candidate at a time, if their list is large it will take them a while to cycle back around to your node). So they will get banned after a somewhat different delay.
After about 20-30 minutes it seems all of the bad peers are banned.
August 06, 2015, 04:07:16 AM
Windows binary built by Arux available here:
https://github.com/iamsmooth/aeon/releases/tag/ip_ban_test1
Please test and report any issues.
https://github.com/iamsmooth/aeon/releases/tag/ip_ban_test1
Please test and report any issues.
@smooth,
I'm running these now to see how the IP banning is working on Windows.
After a couple of minutes running the daemon, I've seen the offending peers getting dropped a couple of times, but so far, they look to be coming back. Could you briefly describe what to expect when this version encounters a bad peer?
Such as:
- Bad peer connects and sends invalid blocks, get's dropped.
- After X connect/drop cycles for a given bad peer, the IP is banned for Y amount of time.
EDIT: Patience pays off
Just seen the following message:2015-Aug-06 10:08:00.568484 [P2P7]Ip xxx.xxx.xxx.xxx blocked.
August 06, 2015, 03:20:02 AM
I have added Linux binaries built by Arux to the release page: https://github.com/aeonix/aeon/releases/tag/v0.9.0.0
August 05, 2015, 10:19:21 PM
Now I see. The previous block was indeed 30+ minutes:
2015-Aug-06 02:33:39.193663 [P2P2]+++++ BLOCK SUCCESSFULLY ADDED
id:
PoW: <234f65de2b2ee219d684a9a10f59aad1be0ac96d52ba176a1128d16a23000000>
HEIGHT 592615, difficulty: 63505131
That's quite a long time (8x the target!), but I guess that will happen from time to time.
2015-Aug-06 02:33:39.193663 [P2P2]+++++ BLOCK SUCCESSFULLY ADDED
id:
PoW: <234f65de2b2ee219d684a9a10f59aad1be0ac96d52ba176a1128d16a23000000>
HEIGHT 592615, difficulty: 63505131
That's quite a long time (8x the target!), but I guess that will happen from time to time.
August 05, 2015, 10:17:08 PM
Is something going on with the network?
Both mining pools report the last block was found about 30+ minutes ago and I'm also not seeing new blocks on my client. However, my miner (minerd) is indicating new blocks....
Both mining pools report the last block was found about 30+ minutes ago and I'm also not seeing new blocks on my client. However, my miner (minerd) is indicating new blocks....
Don't know what is going on with the pool display but my node shows
2015-Aug-06 03:04:39.692797 [P2P8]+++++ BLOCK SUCCESSFULLY ADDED
id: <2217cfabdcb6f523757789add220658091877b1d981278b98b1d3073e2a0944a>
PoW: <69ea073c9d8130b836d3608a93978c219e4e2f4033ffb7991b9f3cb623000000>
HEIGHT 592616, difficulty: 63608659
2015-Aug-06 03:11:27.597922 [P2P9]+++++ BLOCK SUCCESSFULLY ADDED
id: <4ca0b6733cdac5e61f2ee2a4aa2d17b79cb4e12ac09e15c0748f6d81a0bc3db4>
PoW: <27009fdbd9342a17bb6e2f1a49abe98f7507c98e19cd1449578d502f08000000>
HEIGHT 592617, difficulty: 63668084
Seems normal to me
I was just about to edit my post and strikethough it...
Whatever it was, it just passed. The pools updated and noted that the last block was ~8 minutes old (it was up to 35 minutes) - although I *know* that I had refreshed the page less than 8 minutes ago (I also tried from another machine in a different location - both showed 35 minutes.)
Anyhoo, false alarm. My apologies.
August 05, 2015, 10:12:58 PM
Is something going on with the network?
Both mining pools report the last block was found about 30+ minutes ago and I'm also not seeing new blocks on my client. However, my miner (minerd) is indicating new blocks....
Both mining pools report the last block was found about 30+ minutes ago and I'm also not seeing new blocks on my client. However, my miner (minerd) is indicating new blocks....
Don't know what is going on with the pool display but my node shows
2015-Aug-06 03:04:39.692797 [P2P8]+++++ BLOCK SUCCESSFULLY ADDED
id: <2217cfabdcb6f523757789add220658091877b1d981278b98b1d3073e2a0944a>
PoW: <69ea073c9d8130b836d3608a93978c219e4e2f4033ffb7991b9f3cb623000000>
HEIGHT 592616, difficulty: 63608659
2015-Aug-06 03:11:27.597922 [P2P9]+++++ BLOCK SUCCESSFULLY ADDED
id: <4ca0b6733cdac5e61f2ee2a4aa2d17b79cb4e12ac09e15c0748f6d81a0bc3db4>
PoW: <27009fdbd9342a17bb6e2f1a49abe98f7507c98e19cd1449578d502f08000000>
HEIGHT 592617, difficulty: 63668084
Seems normal to me
August 05, 2015, 10:05:52 PM
Is something going on with the network?
Both mining pools report the last block was found about 30+ minutes ago and I'm also not seeing new blocks on my client. However, my miner (minerd) is indicating new blocks....
Both mining pools report the last block was found about 30+ minutes ago and I'm also not seeing new blocks on my client. However, my miner (minerd) is indicating new blocks....
August 05, 2015, 09:23:20 PM
I can report that the Linux version with IP Banning is working great! Thank you!
August 05, 2015, 08:49:01 PM
IP banning - test release
I have an experimental branch with IP banning, which I adapted from Boolberry. It maintains a score for each peer and ones that are repeatedly disconnected are temporarily banned. This should address the issue of frequent error messages from non-upgraded peers. It will also be useful going forward to help protect the network from misbehaving or malicious nodes.
I have an experimental branch with IP banning, which I adapted from Boolberry. It maintains a score for each peer and ones that are repeatedly disconnected are temporarily banned. This should address the issue of frequent error messages from non-upgraded peers. It will also be useful going forward to help protect the network from misbehaving or malicious nodes.
Windows binary built by Arux available here:
https://github.com/iamsmooth/aeon/releases/tag/ip_ban_test1
Please test and report any issues.
August 05, 2015, 09:48:52 AM
On my piece of shit machine all I have ever used as a miner was the LucasJones one. As the new version for Aeon had a bug and the fix has not been binaried for an idiot like me, I have been using Wolf's non AES-NI version. I mine with both of my cores and although that maxes it out on either LJ or Wolf, using Wolf makes even displaying web pages excruciatingly slow, maybe 1 minute to open BCT.
Looking forward to the new LucasJones binaries.
Edit: while using my comp with only one core it works but it is an even more pathetic HR
i updated lucasjones binary with the fix here https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04082015Looking forward to the new LucasJones binaries.
Edit: while using my comp with only one core it works but it is an even more pathetic HR
cpuminer-lucasjones-with-cryptonight-light-w64-05082015.zip file should work now.
(there was a defect with the ancient file named cpuminer-lucasjones-with-cryptonight-light-w64-04082015.zip)
you can give it a try.
I haven't said it publicly as i guessed wolf's binaries was enough
Thank you. It's working! and I can use my comp at the same time!!
BTW I don't know if the HR for your pool is correct on your home page. I don't see how I can have 1/2 the total HR out of 3 miners
with a lot a miners, that's not a problem. the average is good.
but no worries! with less of 300h/s (no typo, less of 0.3kh/s) the pool found two blocks since the fork. it's very very lucky. i hope it continues.
August 05, 2015, 09:13:13 AM
On my piece of shit machine all I have ever used as a miner was the LucasJones one. As the new version for Aeon had a bug and the fix has not been binaried for an idiot like me, I have been using Wolf's non AES-NI version. I mine with both of my cores and although that maxes it out on either LJ or Wolf, using Wolf makes even displaying web pages excruciatingly slow, maybe 1 minute to open BCT.
Looking forward to the new LucasJones binaries.
Edit: while using my comp with only one core it works but it is an even more pathetic HR
i updated lucasjones binary with the fix here https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04082015Looking forward to the new LucasJones binaries.
Edit: while using my comp with only one core it works but it is an even more pathetic HR
cpuminer-lucasjones-with-cryptonight-light-w64-05082015.zip file should work now.
(there was a defect with the ancient file named cpuminer-lucasjones-with-cryptonight-light-w64-04082015.zip)
you can give it a try.
I haven't said it publicly as i guessed wolf's binaries was enough
Thank you. It's working! and I can use my comp at the same time!!
BTW I don't know if the HR for your pool is correct on your home page. I don't see how I can have 1/2 the total HR out of 3 miners
August 05, 2015, 08:42:15 AM
On my piece of shit machine all I have ever used as a miner was the LucasJones one. As the new version for Aeon had a bug and the fix has not been binaried for an idiot like me, I have been using Wolf's non AES-NI version. I mine with both of my cores and although that maxes it out on either LJ or Wolf, using Wolf makes even displaying web pages excruciatingly slow, maybe 1 minute to open BCT.
Looking forward to the new LucasJones binaries.
Edit: while using my comp with only one core it works but it is an even more pathetic HR
i updated lucasjones binary with the fix here https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04082015Looking forward to the new LucasJones binaries.
Edit: while using my comp with only one core it works but it is an even more pathetic HR
cpuminer-lucasjones-with-cryptonight-light-w64-05082015.zip file should work now.
(there was a defect with the ancient file named cpuminer-lucasjones-with-cryptonight-light-w64-04082015.zip)
you can give it a try.
I haven't said it publicly as i guessed wolf's binaries was enough
August 05, 2015, 07:51:34 AM
On my piece of shit machine all I have ever used as a miner was the LucasJones one. As the new version for Aeon had a bug and the fix has not been binaried for an idiot like me, I have been using Wolf's non AES-NI version. I mine with both of my cores and although that maxes it out on either LJ or Wolf, using Wolf makes even displaying web pages excruciatingly slow, maybe 1 minute to open BCT.
Looking forward to the new LucasJones binaries.
Edit: while using my comp with only one core it works but it is an even more pathetic HR
Looking forward to the new LucasJones binaries.
Edit: while using my comp with only one core it works but it is an even more pathetic HR
Jump to: