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

[smooth]

I think I located the problem with the Windows build. If someone wants to create a new binary from github HEAD, we can see if it fixed it.

[boolberry]

RT if you think @ShapeShift_io should add support for boolberry and aeon. Lots of #xmr community overlap so usage should be high #bbr #aeon
https://twitter.com/BBRcurrency/status/633951055781347328

[myagui]

Thanks smooth & nikos64 for your feedback also.

I'm unable to compile at this time, but if no1 reputable has come up with binaries in the meantime, I'll see if I can get setup to compile as well sometime next week. Cheers!

[Arux]

Arux's pool appears to be down. If you are using it you will want to switch somewhere

Front-end was down but core was always running. No shares were lost. Payments are OK.
Cheers.

(Internet onnections are quite impossible here )

[Hix]

Always happens when I don't look for a bit...
Should fix itself again as consolidated coins unlock.

As for a guide for pools, there's a comprehensive guide in the pool software's documentation itself.

You made manual payouts?

[MoneroMooo]

You made manual payouts?

Yes, I had to, as the balance on what I assume is your address was too large to get in a single tx when done by the pool itself, so I transferred manually in smaller chunks over a couple hours as coins unlocked. Hopefully without mistake

* MoneroMooo goes to consolidate again as a precaution

[bitl0ck]

Minergate pool is now back on track, you must use https://github.com/moneromooo/cpuminer-multi for all pools as AEON uses cryptonight-lite.

I think this should be on the main thread.

[Schild_]

Super quiet here... 

[smooth]

Any news? 

I am doing testing on pruning right now.

[Schild_]

Any news? 

I am doing testing on pruning right now.

Hehe. Multitasking Smooth

[Radouch]

I think I located the problem with the Windows build. If someone wants to create a new binary from github HEAD, we can see if it fixed it.

Tonight I somehow managed to compile from GitHub for Windows (not much easy for me, who never ever compiled anything on Windows... :-) ). With 0.9.1.1 binaries I have got hash rate about 80 H/s, with 0.9.2.0 binaries I've got up to 160 H/s.

So, good work, Smooth! :-)

If you believe me, you can download my binaries from cryptoradouch . tk /aeon/aeon0.9.2.win64.zip
(sorry, but bitcointalk believes this is a suspicious link - this is my VPS...)

EDIT:
Now binaries of aeon 0.9.2.0 for Win 64 compiled by me are available on Google Drive, maybe Bitcointalk will like it more:
https://drive.google.com/file/d/0B7aFZCwh53eNLWtuOTVITF9jcDg/view?usp=sharing

[VladimirN]

Super quiet here... 

holidays...

[myagui]

Super quiet here...  

holidays...

While on semi-holidays, I'm quietly acquiring a moderately larger position  

I'm really looking forward to test the newer version, largely to allow me the contribution of a solo mining daemon/node.
Will try to compile using the OP instructions tonight.

Edit: No luck at my 1st quick attempt at compiling. I eventually got binaries built, but there's some fatal error right at daemon start and it does not run at all. I'm pretty sure this is some issue with my build environment. I'll look into error messages and further troubleshooting when I get a break.

Edit #2: Just in case someone can easily point me in the right direction, here's the error I have when launching the daemon self-compiled:

Code:

2015-Aug-23 12:15:25.431831 aeon v0.9.2.0(@VERSION@)
2015-Aug-23 12:15:25.432832 Module folder: C:\Users\-removed-\aeon\build\src\Release\aeond.exe
2015-Aug-23 12:15:25.435836 Initializing p2p server...
2015-Aug-23 12:15:25.437837 ERROR c:\users\-removed-\aeon\src\p2p\net_node.inl:110 Exception at [node_server::init_config], what=unsupported version
2015-Aug-23 12:15:25.440839 ERROR c:\users\-removed-\aeon\src\p2p\net_node.inl:273 Failed to init config.
2015-Aug-23 12:15:25.442841 ERROR C:\Users\-removed-\aeon\src\daemon\daemon.cpp:174 Failed to initialize p2p server.
2015-Aug-23 12:15:25.445844 Mining has been stopped, 0 finished

I used latest cmake (3.3), boost 1.57 and VStudio 2013 as described on the OP, and I'm on Win 8.0 x64.
I think I saw some error concerning a "version.h" file when generating the configuration files or when compiling, not sure now and I have cleared the logs already. Will check it out again later.

Cheers!
 

[Radouch]

Super quiet here...  

holidays...

I used latest cmake (3.3), boost 1.57 and VStudio 2013 as described on the OP, and I'm on Win 8.0 x64.
 

I used boost 1.59 and VStudio 2015 and my compiled binaries run on Win 7 x64 without problems.
Only I had to rename some folder, but unfortunatelly do not remember which one...

[Radouch]

This morning version:

https://drive.google.com/file/d/0B7aFZCwh53eNd1F6LUJ5a3JlNTg/view?usp=sharing

[myagui]

Thanks for the input Radouch. I'm not going to run a binary from a recent member as I don't have an isolated environment for testing right now, but perhaps that helps others.

I didn't manage to fix whatever issue is causing me grief with my regular Windows box, but I was able to compile the binaries on a freshly installed Win 10 VM. The binaries created on the Win 10 VM did work fine on my usual PC (Win 8.0). 

For anyone else that might want to test these, do understand that I'm a relative newbie at compilation (most of my experience is with cudaminer/ccminer), so I doubt I'd be able to fix any issues one might find. The following link has binaries from the current code on git, and were compiled using a clean/fresh Windows 10 x64 VM with VStudio 2015 and Boost 1.59.
Aeon-Win-x64-0.9.2.0-git.zip

@smooth:
I see my hashrate restored while solo mining on the daemon (about 640h/s now), so thank you, looks that the issue is fixed!
Side note, please update the OP with the revised compilation instructions as per the following post:
https://bitcointalk.org/index.php?topic=641696.msg11946271#msg11946271

Cheers!

[smooth]

I see my hashrate restored while solo mining on the daemon (about 640h/s now), so thank you, looks that the issue is fixed!

Great!

That's a pretty nice hash rate! What CPU is that?

Side note, please update the OP with the revised compilation instructions as per the following post:
https://bitcointalk.org/index.php?topic=641696.msg11946271#msg11946271

Cheers!

Done. Thanks for pointing out the update.

[myagui]

Cheers Smooth! It's an i7-4770, standard clocks and all, running 6 threads, above normal priority.

Frustrated with my earlier trouble with compiling on the original Windows box, I had a few more cracks at it, and finally sorted what the issue with compiling on that one as well. Suspecting that I had a broken boost setup, I rebuilt boost, then recompiled there, and presto, also got me working binaries. Happy camper. 

I'm not sure this needs correcting on the compilation instructions, could be my misunderstanding, but anyhow, that's how it worked for me - definitely the case on building boost 1.59 - not sure if it makes any difference on earlier versions, as the documented 1.57.

Where it reads:
b2 --toolset=msvc variant=release link=static threading=multi runtime-link=static address-model=64

I used instead:
b2 toolset=msvc variant=release link=static threading=multi runtime-link=static address-model=64

[Phantas]

http://aeonpool.mooo.com/  is down

[Radouch]

Thanks for the input Radouch. I'm not going to run a binary from a recent member as I don't have an isolated environment for testing right now, but perhaps that helps others.

I really appreciate your reaction, Myagui. No reaction makes me really uncertain if my reports are of any use.

Concerning binaries: better safe than sorry, no problem. I only want to stress that my account is one year old (and only 6 months younger than yours). I just prefer reading over writing, especially if I do not have anything meaningful to say.

Have a nice day :-)