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

[americanpegasus]

Didn't the original Developer use AEON as an acronym ?
I think the "E" stood for "electronic"but I can't recall what the others stood for

Anonymous Electronic O? Note

[1714182537]

1714182537

[1714182537]

1714182537

[1714182537]

1714182537

[1714182537]

1714182537

[1714182537]

1714182537

[onemorexmr]

Didn't the original Developer use AEON as an acronym ?
I think the "E" stood for "electronic"but I can't recall what the others stood for

Anonymous Electronic O? Note

Omni?
https://en.wikipedia.org/wiki/Omni

Omni is a Latin prefix meaning "all" or "every". Omni may also refer to:

[bangomatic]

the acronym is posted on the OP, right under the logo.

[onemorexmr]

the acronym is posted on the OP, right under the logo.

LOL just noticed it ;-)
thank you for the heads up

[smooth]

Didn't the original Developer use AEON as an acronym ?
I think the "E" stood for "electronic"but I can't recall what the others stood for

The acronym always seemed a bit contrived to me, more likely a backronym, but I don't really know.

[adhitthana]

Although my interests are primarily in the area of blockchain technology and experimental improvements to the cryptonote protocol, I invite others to join the project and work on other items such as a GUI wallet (though we can likely adapt existing GUI wallets from other cyptonote coins), mobile wallets, marketing, etc.

I have created a new donation address for the project. The amount of donations received will have some influence on the pace of work, largely because it allows me to gauge the interest of the community in a credible way, and I'm less interested in working on something that no one cares about.

How is this all going? I did make a donation previously and am happy to donate more if appropriate. Where are we at?

Thanks

[smooth]

Although my interests are primarily in the area of blockchain technology and experimental improvements to the cryptonote protocol, I invite others to join the project and work on other items such as a GUI wallet (though we can likely adapt existing GUI wallets from other cyptonote coins), mobile wallets, marketing, etc.

I have created a new donation address for the project. The amount of donations received will have some influence on the pace of work, largely because it allows me to gauge the interest of the community in a credible way, and I'm less interested in working on something that no one cares about.

How is this all going? I did make a donation previously and am happy to donate more if appropriate. Where are we at?

Thanks

I've posted updates on the donation balance regularly, including noting specific donations when I noticed them. If I missed yours, I apologize for that. Of course, I can't tell where the donations are coming from, only the timing and amount. In addition we get periodic mined blocks both from the seed node servers which are solo mining and from people using the --donate option to solo mine for the project (which also helps decentralize the network -- which by the way is critically important at the moment).

Current donation balance:

balance: 458368.890250628707, unlocked balance: 458368.890250628707

[adhitthana]

All good Smooth. I had a lot of Aeon trapped on Poloniex and you were very helpful assisting me transfer them. And 100% trustworthy, so I donated a small amount. Keep up the good work

[saddambitcoin]

Trying to sync the 0.9.6 aeond for the first time, the daemon keeps getting killed for some reason...any ideas?

Then I start it up again and I have to start syncing the blockchain from 0.

I'm also running bitmonerod on this machine, so maybe its too much for it to handle at the same time?

Code:

2015-Dec-03 23:40:32.289786 [P2P2]CHECKPOINT PASSED FOR HEIGHT 540000 <94e19cf9d5a16ae90f67c321f8376b87da21d6d6c2cb0957b9ab558dca66c1dc>
Killed

edit: After starting over, the daemon gets killed at the same point, just after the checkpoint for 540000.

[smooth]

Trying to sync the 0.9.6 aeond for the first time, the daemon keeps getting killed for some reason...any ideas?

Then I start it up again and I have to start syncing the blockchain from 0.

I'm also running bitmonerod on this machine, so maybe its too much for it to handle at the same time?

Code:

2015-Dec-03 23:40:32.289786 [P2P2]CHECKPOINT PASSED FOR HEIGHT 540000 <94e19cf9d5a16ae90f67c321f8376b87da21d6d6c2cb0957b9ab558dca66c1dc>
Killed

edit: After starting over, the daemon gets killed at the same point, just after the checkpoint for 540000.

That seems like out of memory (Linux "OOM killer"). You can try the pruning branch which uses somewhat less. You can also try adding a bit of swap on your system. If the shortfall isn't too large, swap will help without performance being too terrible. Installing the dphys-swapfile package on Ubuntu will manage swap automatically for you, not sure if there is a non-manual swap solution on other distros.

[saddambitcoin]

Thanks smooth.

I had 4G of swap already, but I'm trying again now with 6G! Let's go!

[smooth]

Thanks smooth.

I had 4G of swap already, but I'm trying again now with 6G! Let's go!

Did you try the pruning branch? If you are that close, the savings from pruning should be more than enough make it work.

[saddambitcoin]

hashrate: 0.1579
hashrate: 0.3158

is that normal?

mining monero on the same machine i'd be getting like 30-40 H/s

Did you try the pruning branch? If you are that close, the savings from pruning should be more than enough make it work.

Is it on your github? I didn't see any links to it on the front page, so I just went with the main source.

[nioc]

hashrate: 0.1579
hashrate: 0.3158

is that normal?

mining monero on the same machine i'd be getting like 30-40 H/s

Did you try the pruning branch? If you are that close, the savings from pruning should be more than enough make it work.

Is it on your github? I didn't see any links to it on the front page, so I just went with the main source.

My HR for Monero is 35 H/s and for Aeon it's 86 H/s for a modern Pentium dual core non AES-NI

(running both cores)

[saddambitcoin]

Nevermind, my hashrate just exploded! Maybe I wasn't fully synced earlier.

hashrate: 77.1579

[smooth]

Nevermind, my hashrate just exploded! Maybe I wasn't fully synced earlier.

hashrate: 77.1579

Make sure you are fully utilizing your cache. This may require more threads than Monero, depending on your core count and cache size, and whether hyperthreads are supported.

Don't expect great efficiency without AES-NI though. Still, better than nothing.

[smooth]

Did you try the pruning branch? If you are that close, the savings from pruning should be more than enough make it work.

Is it on your github? I didn't see any links to it on the front page, so I just went with the main source.

Sorry, finding it is slightly obscure since it is officially just a test release. It has gotten quite a bit of testing though, perhaps enough to promote it to a link on the first page. You can skip step 1 if you just want to sync from scratch. The file copy is only needed to convert an existing blockchain file.

Pruning (aka Light Full Node) test release

This release optionally prunes the blockchain by dropping no-longer-needed information once it is processed and verified by your node. This reduces both memory and storage requirements, and perhaps more importantly reduces the rate at which both increase over time. With pruning enabled, the daemon continues to function as a full node on the network in nearly every way. I will be posting a FAQ to answer some other questions about the details of the pruning functionality.

Please test, especially if you have a smaller memory configuration. Very small memory configurations (<2 GB? -- I'm not sure) won't work with this, but if you have something that has been barely able to run the daemon previously, this should improve your performance quite a bit. Certainly some smaller-memory systems (at a minimum 3-4 GB of RAM, if not smaller) should be able to successfully run a node now. I'm not sure if any 32-bit operating systems can handle it, although it is possible.

Since converting an existing blockchain requires enough RAM to at least load it first, resyncing from scratch with the --pruning option may be a better option for smaller-memory systems until pruned bootstraps become available.

Instructions:

1. Copy your blockchain.bin file to blockchain-pruned.bin in the same location. The daemon uses different files to store the pruned and unpruned versions of the blockchain. Once testing is complete if you want to delete the unpruned blockchain to free up disk space that is fine, but I don't recommend it right away EDIT: there have been some issues with compatibility of the .bin files so I recommend backing up all of those files before using a test release.

2.

git clone https://github.com/iamsmooth/aeon light-node
cd light-node
git checkout light-node
make etc.

3. Start node with the --pruning option. You should get a message at startup about the blockchain being pruned (this is done using the blockchain-pruned.bin file; your original blockchain.bin file is unchanged).

4. Exit node to save the pruned blockchain and reset RAM usage.

5. Start node again with the --pruning option.

6. If any problems occur you can switch back to unpruned (start daemon without --pruning)

Report any issues (or even if no issues)

Limitations: a pruned node can not be used to rescan or restore a wallet that is older than the pruning period (10 000 blocks, or about 28 days). Also, if a pruned node is disconnected from the network for more than the duration of this pruning period, it will potentially not be able to recover on its own, and will need to be resynced from scratch or with a bootstrap. The second restriction is fixable and can be addressed later. Otherwise it should be functionality complete.

Neither this test release nor the pruning feature is recommended for important nodes such as pools, exchanges, etc. Please continue to use the standard version at this time for those purposes.

Thanks for testing!

[LucyLovesCrypto]

I read somewhere that Aeon plans to use the Monero db code once it is finalized and released. Are there any short term development goals for Aeon right now? Or are we essentially waiting on the Monero db to port to Aeon before more development continues?

I have used both 9.6 and the pruning branch and am happy with the results. Keep up the great work!

[smooth]

I read somewhere that Aeon plans to use the Monero db code once it is finalized and released. Are there any short term development goals for Aeon right now? Or are we essentially waiting on the Monero db to port to Aeon before more development continues?

I have used both 9.6 and the pruning branch and am happy with the results. Keep up the great work!

The primary current short term goal is merging the Cryptonote reference GUI (which in turn is based on Bitcoin-Qt). It is mainly going slowly due to limited development time. It won't be held up waiting for the DB merge, nor vice versa. There are also some other blockchain and wallet improvements I have lined up to go into new releases but aren't enough to motivate a new release on their own yet.

[Arux]

Min difficulty increased to 10k at http://52.8.47.33:8080

my bandwith is limited and with fixed diff as low as 2k, bill was growing too much.
but i'm not sure that low fixed diff is the guilty, the api was draining a lot of bandwith too, the refresh rate of the front-end is now lowered at 30s. i will see how it's possible to lower min diff according to bandwith consumption.