[ANN] AEON: Scalable, private, mobile-friendly cryptocurrency

[MoneroMooo]

Is everything OK with http://aeonpool.mooo.com ?

I mining on pool 3 hours and still my pending balance is 0.

Hashrate is OK, and on my miner is also everything OK.

The 60 block maturation rate now takes about 4 hours, instead of the previous 1 hour, due to the larger block target after the fork. So balance updates are delayed further. Similarly, you will get balance increases for about 4 hours after you stop mining, as the block you mined for mature. If you still haven't got anything in a couple hours, let me know, but I think it's all working fine at the moment.

[smooth]

Is everything OK with http://aeonpool.mooo.com ?

I mining on pool 3 hours and still my pending balance is 0.

Hashrate is OK, and on my miner is also everything OK.

The 60 block maturation rate now takes about 4 hours, instead of the previous 1 hour, due to the larger block target after the fork. So balance updates are delayed further. Similarly, you will get balance increases for about 4 hours after you stop mining, as the block you mined for mature. If you still haven't got anything in a couple hours, let me know, but I think it's all working fine at the moment.

Maybe add a stat for immature shares?

[smooth]

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.

To test:

git clone https://github.com/iamsmooth/aeon aeon_ip_banning
cd aeon_ip_banning
git checkout ip_banning
make
etc.

Start the node. After a few minutes the bad nodes should be banned (a message will show up in blue) and the errors should stop.

Because this is a test version, the bans are not stored to the p2pstate file, but in a future release version they will be. So bans will be lost if you restart the node, but they're relearned pretty quickly.

Please let me know how it works and if you observe any issues!

[MoneroMooo]

Maybe add a stat for immature shares?

That'd require non trivial Javascript code I think. And either continuous recalculation from scratch, or getting the pool to work out which blocks it found were reorganized away to remove those shares that were tentatively added. Just not worth it.

[smooth]

Maybe add a stat for immature shares?

That'd require non trivial Javascript code I think. And either continuous recalculation from scratch, or getting the pool to work out which blocks it found were reorganized away to remove those shares that were tentatively added. Just not worth it.

Yeah I see what you mean. Plus blocks being reorged away isn't even permanent since another reorg could put them back. So definitely complicated to deal with.

[Phantas]

Is everything OK with http://aeonpool.mooo.com ?

I mining on pool 3 hours and still my pending balance is 0.

Hashrate is OK, and on my miner is also everything OK.

The 60 block maturation rate now takes about 4 hours, instead of the previous 1 hour, due to the larger block target after the fork. So balance updates are delayed further. Similarly, you will get balance increases for about 4 hours after you stop mining, as the block you mined for mature. If you still haven't got anything in a couple hours, let me know, but I think it's all working fine at the moment.

OK, thank you.
Now, I see pending balance

[Phantas]

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.

To test:

git clone https://github.com/iamsmooth/aeon aeon_ip_banning
cd aeon_ip_banning
git checkout ip_banning
make
etc.

Start the node. After a few minutes the bad nodes should be banned (a message will show up in blue) and the errors should stop.

Because this is a test version, the bans are not stored to the p2pstate file, but in a future release version they will be. So bans will be lost if you restart the node, but they're relearned pretty quickly.

Please let me know how it works and if you observe any issues!

Nice.
It's working 

[imihal44]

can someone explain me what this error means while i trying to sync my wallet,i download newest and blockchain....using win 8.1 64 bit
http://imgur.com/WuGC398

[smooth]

can someone explain me what this error means while i trying to sync my wallet,i download newest and blockchain....using win 8.1 64 bit
http://imgur.com/WuGC398

Assuming you are indeed using the current version, that means your node was connected to another node that wasn't using the current version, so it got disconnected.

In short it is not a problem for you.

[nioc]

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

[Arux]

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/04082015
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

[nioc]

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/04082015
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

[Arux]

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/04082015
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

the pool is too small to be accurate. the pool hashrate is the average of shares accepted. but the difficulty is retargeted permanently. (if the difficulty is to low, you send a lot of shares but it will never validate a block, to high, you will never send shares so no block too.)
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.

[smooth]

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.

Windows binary built by Arux available here:

https://github.com/iamsmooth/aeon/releases/tag/ip_ban_test1

Please test and report any issues.

[aerbax]

I can report that the Linux version with IP Banning is working great!  Thank you!

[aerbax]

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....

[smooth]

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....

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

[aerbax]

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....

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.

[smooth]

Now I see. The previous block was indeed 30+ minutes:

2015-Aug-06 02:33:39.193663 [P2P2]+++++ BLOCK SUCCESSFULLY ADDED
id:     <c4702ca19c3d15821cb5ca59b4f9b9c26c473861320b9d21f5c8303abeafd425>
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.

[smooth]

I have added Linux binaries built by Arux to the release page: https://github.com/aeonix/aeon/releases/tag/v0.9.0.0