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

[MoneroMooo]

Due to the fork yesterday, the pool payments also got wonky.
There are a number of payments made by the pool yesterday and today which are not included in the correct chain, and thus miners did not receive these, but the pool does not know that, and the txes do not seem to have been reincluded in another block. This means I will have to go manually tally up all that the pool thinks was sent, but was not actually included on the main chain, and send manual payments to miners for that missing amount.

In the meantime, please use Arux's pool (http://52.8.47.33:8080/) or solo mining from the daemon.

Sorry for the inconvenience.

[MoneroMooo]

After some dread, I've restarted the pool publicly with 0.9.4.0 and it appears to be working well. It's found blocks already and made some more automatic payouts, and the blocks were accepted by smooth's daemon. So it looks like it's all back on track after reverting blockchain and daemon.

There's a silver lining though, Arux's pool now has 20 kH/s

I'll be doing the accounting for missing payments this afternoon.

[myagui]

Here are Win binaries for anyone interested.
Mind the usual cautionary notes as these are unofficial, community provided.

Stable Full Node Release: Aeon-Win-x64-0.9.4.0
Testing Light Node Release: Aeon-Win-x64-0.9.4.0-light-node

I haven't run either of these myself yet, but will switch to the updated light-node version shortly.
My previous Aeon release download links are now broken (purposefully), but if anyone needs one of those older versions let me know as I do have the files archived anyhow.

Do remember to read the release details from Smooth, quoted just below!
Cheers!

New version (0.9.4.0)

Mandatory if you are currently using 0.9.2.0 or 0.9.3.0

Recommended for all users

In order to avoid any future problems like the one that happened to MoneroMooo's pool, this release reverts the recent changes to optimize blockchain memory usage and remove stuck tx key images. It is very likely that one of these changes (possibly in connection with some existing bug) caused Mooo's blockchain to become corrupt. Those changes are also present in the pruning test so I recommend discontinuing the test until further notice.

The other recent improvements such as fixing the mining speed on Windows, anonymity improvements, transaction fee, dust reduction, etc. remain in this version.

You will need to download a bootstrap from before the 0.9.2.0-0.9.3.0 changes or resync. Your existing blockchain will be ignored. Resyncing should be significantly faster than before in most cases. The older bootstraps from OP will likely work thought they will require a bit of syncing.

The pruning test branch has been updated to 0.9.4.0, so if you are using that you will need to fetch the update and recompile or wait for a new community-provided build.

Other changes in this release

Optimize sync speed in checkpoint zone
Update seed node list

https://github.com/aeonix/aeon/releases/tag/v0.9.4.0

[muchoman]

Thank you for compiling, working fine.

aeond mem usage 4,5gb
blockchain size 2,97 GB (3 189 954 174 bytes)

[muchoman]

Can anybody compile for Linux too?

[myagui]

Seeing as release 0.9.4.0 also requires a full resync, though possibly aided by one of the bootstraps on the OP, I've sync'ed a full node on this version have a bootstrap to share. Please note that due to daily bandwidth limitations, this particular download link might not always be available.
If it becomes too complicated for me to host this file with the current provider (Dropbox), I'll see if I can work out an alternative one.

The bootstrap is current as of a couple hours ago, and can only be used in Windows x64 systems.
Aeon-Win-x64-bootstrap-2015-09-03

Cheers!

BTW: Smooth & Mooo, great job at spotting the issue so quickly, getting the pool back online, as well as the lightning speed at which the new releases were made available! Rock on! 

[Arux]

Chainradar is on the correct chain. I notice it only now.
Someone knows since how many times are they ?

[MoneroMooo]

Accounting is done. 481 AEON went missing in those txes that were mined on the wrong fork.
The relevant addresses for those have been found, and missing balances paid. Amusingly, it needed a single tx for all 16 miners:

http://chainradar.com/aeon/transaction/fa45c15cd76f73e6e1bbc401c8582646b3f07f23895a7715f3208f8426ec86dd

Payment ID: echo -n "aeonpool.mooo.com failed txes" | sha256sum

Sorry again for the trouble, and make sure to give Arux's pool some love too

[smooth]

Official Windows 64-bit binaries have been added to the 0.9.4.0 release page. These use boost 1.58. Thanks Arux!

https://github.com/aeonix/aeon/releases/tag/v0.9.4.0

[exciter0]

This can't come soon enough...

Development update
I'm also taking steps to address the mining decentralization, which I will be announcing soon.

all we need is another fork  

Code:

Network Hash Rate: 138.97 KH/sec

Our Pool  Hash Rate: 110.83 KH/sec

That's 80% of network hash!

[smooth]

Bittrex wallet transactions are unfrozen.

[Radouch]

http://aeonpool.mooo.com/ now:

Network
 Hash Rate: 125.87 KH/sec

Our Pool
 Hash Rate: 152.17 KH/sec

Can a pool have got a bigger hash rate than the network?

[myagui]

... Can a pool have got a bigger hash rate than the network?

Absolutely. The reason is that, the network hashrate is purely an estimation, based on the time that it took to find the last X blocks and their relative difficulty over that period.

In a similar sense, the pool hashrate is also just an estimation, since it is simply adding up the number of shares that it receives from miners over a certain period, and their relative share difficulty.

If you throw 100 KH/s at the pool right now, the pool stats will quickly update due to the massive influx of shares, while the network hashrate will take a good while longer to reflect the added hashrate, as the necessary sample data is much larger and the estimation takes much longer to settle after a drastic change.

Not sure I was able to come up with a half-decent description on this... Well, I tried 

[Radouch]

... Can a pool have got a bigger hash rate than the network?

Not sure I was able to come up with a half-decent description on this... Well, I tried 

You explained it so plainly that even I do understand :-) Thank you very much.

[aerbax]

I really wish some of the folks on Moo's pool would move over to Arux's.  If you're concerned about the pool not paying out as much, don't be.  Instead of getting lots of 1 AEON payouts, you'll get less frequent, but much higher payouts.  It works out to be just about the same.

[myagui]

I really wish some of the folks on Moo's pool would move over to Arux's.  If you're concerned about the pool not paying out as much, don't be.  Instead of getting lots of 1 AEON payouts, you'll get less frequent, but much higher payouts.  It works out to be just about the same.

I second this, and add the suggestion of trying out solo mining if using a high'ish-end CPU.
I'm still solo'ing on the daemon with a single i7 4770 and I think there has not been a single day that I don't hit at least one block.
Some days I get two, so, double-yay! 

[BoscoMurray]

I really wish some of the folks on Moo's pool would move over to Arux's.  If you're concerned about the pool not paying out as much, don't be.  Instead of getting lots of 1 AEON payouts, you'll get less frequent, but much higher payouts.  It works out to be just about the same.

+1

I've moved over myself

[whortonda]

I moved to Arux's pool after Moo's had the issue with the daemon and I haven't looked back.   In the long run, the payouts will theoretically be the same.

This is a great coin and community.  Really impressed.

[exciter0]

Beside miners, pool operators also have the responsibility to ensure the well being of the coin. If no measure are taken to prevent more than 50% hash,  it will undermine all the great features and the legitimacy of this coin.

This is not good, we have a single pool approaching 100% of the network hash rate. 

[smooth]

Beside miners, pool operators also have the responsibility to ensure the well being of the coin. If no measure are taken to prevent more than 50% hash,  it will undermine all the great features and the legitimacy of this coin.

What's your suggestion? Sincere question. I have some plans in the works but new ideas are always welcome especially if they can be implemented immediately.

Ultimately it comes down to how much the community members care about it, and it seems many don't. They just want to mine on one big pool and probably dump right away (I'm guessing here, of course, that if they wanted to hold longer term they'd care more about the legitimacy and such and not just mine on one big pool.)