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

[DrkLvr_]

Hi, trying to build 0.9.9.0 in win64 using the instructions in the OP, receiving this:

Code:

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
IPHLPAPI_LIBRARY
    linked by target "libminiupnpc-static" in directory C:/Users/1/Documents/GitHub/aeon/external/miniupnpc
WINSOCK2_LIBRARY
    linked by target "libminiupnpc-static" in directory C:/Users/1/Documents/GitHub/aeon/external/miniupnpc

-- Configuring incomplete, errors occurred!

Any suggestions welcome

[smooth]

The Windows build problem is a known issue. Arux is working on it.

[Arux]

i just figured out how to cleanly fix windows compilation. i will try to publish the fix today.

[gambadamba]

hi

bitrex
 The last block update occurred 279 minutes ago.

[teknohog]

bitrex
 The last block update occurred 279 minutes ago.

I've also filed a ticket. There's no need to report every single exchange glitch here, but it may be noteworthy that this has happened over and over since their Aeon wallet returned from maintenance.

[Arux]

i pushed a fix to compile binaries on windows. it's in my repo on the fix_win32_compilation branch.
https://github.com/Arux-BTT/aeon/tree/fix_win32_compilation
instructions in the OP are still valid

i pushed it because i guess some people are waiting it but there is still some work to do. The main code is there but improvements are certainly missing. (there is some compile errors on the test folder e.g.)
i expect to make a pull request on the official repo this week if all is ok then i will produce final binaries.

[wck]

Hi I have the 0.9.8 daemon running and i downloaded the 0.9.9 source for windows , how do i update the daemon & wallet to 0.9.9 ? Thank you

You have to build it.   Since you are asking about it, you probably don't have much chance of successfully building it.   Probably best just to wait for the binaries.   If you are going to build it you have to get the correct toolchain in place as well as the correct versions of 3rd party libraries.   To figure out what you need you need to look at the make files or project files depending on what the source includes.   It is often much more involved that it sounds.   Even if someone provides step by step instructions there can be many pitfalls.   

 

[The Cryptophilanthropist]

so can the 0.9.8 daemon be used correctly for now? for example spending coins and mining coins?  Im running this on windows on limited knowledge with core wallets and clients and im interested to mine AEON.  I have been using minergate to mine but I want more control

.0.9.8 is working ok for now as far as I can tell, wait for binaries and mine at my pool 98.239.231.31:9000

[LesPristy]

Since you are asking about it, you probably don't have much chance of successfully building it.

A little encouragement goes a long way.

[smooth]

building on ubuntu or in a virtual machine running ubuntu is not hard. I think all you need to do is:

apt-get install build-essential cmake libboost-all-dev¹
git clone https://github.com/aeonix/aeon
cd aeon
git checkout v0.9.9.0²
make
cd build/release/src
./aeond

¹ If you are using Ubuntu 14.04 you will need libboost1.55-all-dev (default boost version has a bug and should not be used)

² Replace with current release tag

[wck]

Since you are asking about it, you probably don't have much chance of successfully building it.

A little encouragement goes a long way.

I wasn't trying to be encouraging.   What was being asked isn't a simple task.  If you give the impression that it is simple you just waste people's time. 

It also appears that @Arux is already figuring out what to do and making the necessary changes in the code to create Window's binaries. 

@Smooth also offered a good solution.  If you have a Windows computer one can just created a Linux VM and then compile the wallet and daemon on Linux.   Then just run the wallet in the VM.   It really doesn't matter where you run it as long as you keep track of the private key for your wallet.

[daberti]

Trying to build 9.9.0 on Windows and building Boost 1_63_0 went ok.

However cmake raised this errors:
PS C:\Users\Dan\Documents\GitHub\aeon> cmake -G "Visual Studio 14 Win64" -DBOOST_ROOT=d:\boost_1_63_0 -DBOOST_L
=d:\boost_1_63_0\stage\lib
-- Boost version: 1.63.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   chrono
--   regex
--   serialization
--   program_options
--   atomic
-- Found Git: C:/Program Files/Git/cmd/git.exe
-- Found PythonInterp: C:/Users/Dan/AppData/Local/Programs/Python/Python36/python.exe (found version "3.6.1")
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
IPHLPAPI_LIBRARY
    linked by target "libminiupnpc-static" in directory C:/Users/Dan/Documents/GitHub/aeon/external/miniupnpc
WINSOCK2_LIBRARY
    linked by target "libminiupnpc-static" in directory C:/Users/Dan/Documents/GitHub/aeon/external/miniupnpc

Any idea is hotly appreciated.
Thanks in advance

[The Cryptophilanthropist]

Having multiple socket failures on daemon both recent versions, is this a problem on my end??

2017-Apr-03 07:34:33.731541 [P2P8][sock 13] Some problems at write: Broken pipe:32
2017-Apr-03 08:37:01.913991 [P2P3][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:40:18.924091 [P2P7][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:43:20.505536 [P2P1][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:46:29.252562 [P2P7][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:49:32.701434 [P2P3][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:52:39.518486 [P2P2][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:55:49.193804 [P2P9][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:56:20.726422 [P2P4][sock 15] Some problems at write: Connection reset by peer:104
2017-Apr-03 08:59:18.646990 [P2P4][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 09:00:33.005134 [P2P8][sock 15] Some problems at write: Connection reset by peer:104
.....and many more!!!

seeing many more than usual to the point that wallet RPC failed

[Arux]

Trying to build 9.9.0 on Windows and building Boost 1_63_0 went ok.

However cmake raised this errors:
PS C:\Users\Dan\Documents\GitHub\aeon> cmake -G "Visual Studio 14 Win64" -DBOOST_ROOT=d:\boost_1_63_0 -DBOOST_L
=d:\boost_1_63_0\stage\lib
-- Boost version: 1.63.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   chrono
--   regex
--   serialization
--   program_options
--   atomic
-- Found Git: C:/Program Files/Git/cmd/git.exe
-- Found PythonInterp: C:/Users/Dan/AppData/Local/Programs/Python/Python36/python.exe (found version "3.6.1")
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
IPHLPAPI_LIBRARY
    linked by target "libminiupnpc-static" in directory C:/Users/Dan/Documents/GitHub/aeon/external/miniupnpc
WINSOCK2_LIBRARY
    linked by target "libminiupnpc-static" in directory C:/Users/Dan/Documents/GitHub/aeon/external/miniupnpc

Any idea is hotly appreciated.
Thanks in advance

compatible code is not pushed yet in the official repo. if you want to build 0.9.9.0 windows binaries, you must use my repo (git clone https://github.com/Arux-BTT/aeon yourfolder) then switch on "fix_win32_compilation" (git checkout fix_win32_compilation)
work in progress but binaries are functional.

[smooth]

Having multiple socket failures on daemon both recent versions, is this a problem on my end??

2017-Apr-03 07:34:33.731541 [P2P8][sock 13] Some problems at write: Broken pipe:32
2017-Apr-03 08:37:01.913991 [P2P3][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:40:18.924091 [P2P7][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:43:20.505536 [P2P1][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:46:29.252562 [P2P7][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:49:32.701434 [P2P3][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:52:39.518486 [P2P2][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:55:49.193804 [P2P9][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:56:20.726422 [P2P4][sock 15] Some problems at write: Connection reset by peer:104
2017-Apr-03 08:59:18.646990 [P2P4][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 09:00:33.005134 [P2P8][sock 15] Some problems at write: Connection reset by peer:104
.....and many more!!!

seeing many more than usual to the point that wallet RPC failed

Strange. I have tested the wallet quite a bit and I haven't had any problems with it, but others report various issues. Is this Windows or Linux?  The broken pipe/connection reset issues are unclear, could be peers not responding (normal) or something else.

Can you try rebuilding HEAD from master on my repo and let me know if any different. I have a couple of minor fixes there. https://github.com/iamsmooth/aeon

[The Cryptophilanthropist]

Having multiple socket failures on daemon both recent versions, is this a problem on my end??

2017-Apr-03 07:34:33.731541 [P2P8][sock 13] Some problems at write: Broken pipe:32
2017-Apr-03 08:37:01.913991 [P2P3][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:40:18.924091 [P2P7][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:43:20.505536 [P2P1][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:46:29.252562 [P2P7][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:49:32.701434 [P2P3][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:52:39.518486 [P2P2][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:55:49.193804 [P2P9][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:56:20.726422 [P2P4][sock 15] Some problems at write: Connection reset by peer:104
2017-Apr-03 08:59:18.646990 [P2P4][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 09:00:33.005134 [P2P8][sock 15] Some problems at write: Connection reset by peer:104
.....and many more!!!

seeing many more than usual to the point that wallet RPC failed

Strange. I have tested the wallet quite a bit and I haven't had any problems with it, but others report various issues. Is this Windows or Linux?  The broken pipe/connection reset issues are unclear, could be peers not responding (normal) or something else.

Can you try rebuilding HEAD from master on my repo and let me know if any different. I have a couple of minor fixes there. https://github.com/iamsmooth/aeon

It is Linux running a pool
I am building a fresh server as I believe this one may be having issues, it is almost complete (for pool that is) if this one has same issues I'll send a message. I resaved and reloaded blockchain just to check but the errors are already piling up again after an hour, also not finding blocks. Let you know what happens.

[The Cryptophilanthropist]

Btw just had another person running daemon report the same thing on windows, regarding connections

2017-Apr-03 09:47:35.908283 [P2P2][sock 1008] Some problems at write: An existing connection was forcibly closed by the remote host:10054

[LesPristy]

Since you are asking about it, you probably don't have much chance of successfully building it.

A little encouragement goes a long way.

I wasn't trying to be encouraging.   What was being asked isn't a simple task.  If you give the impression that it is simple you just waste people's time. 

Heh, no problem. I find a challenge to be the best motivation.

"You probably can't do that."
"Oh yeah, wanna bet? Hold my beer and watch this."

That can be encouraging to the right kind of person.

I did find that building 0.9.9.0 on Linux (Ubuntu) was quite easy.

The only problem I had with that was aeond refused to connect to the seed node. After a while I got it working by setting "--hide-my-port --allow-local-ip --add-peer 10.X.X.X" to get it to connect to my local Windows box running 0.9.8.0. After that it found the external peers.

I haven't tried the Windows build yet.

[wck]

Since you are asking about it, you probably don't have much chance of successfully building it.

A little encouragement goes a long way.

I wasn't trying to be encouraging.   What was being asked isn't a simple task.  If you give the impression that it is simple you just waste people's time. 

Heh, no problem. I find a challenge to be the best motivation.

"You probably can't do that."
"Oh yeah, wanna bet? Hold my beer and watch this."

That can be encouraging to the right kind of person.

I did find that building 0.9.9.0 on Linux (Ubuntu) was quite easy.

The only problem I had with that was aeond refused to connect to the seed node. After a while I got it working by setting "--hide-my-port --allow-local-ip --add-peer 10.X.X.X" to get it to connect to my local Windows box running 0.9.8.0. After that it found the external peers.

I haven't tried the Windows build yet.

I understand you.   Sorry it is easy to come across wrong in just text.

The AEON code base isn't easy to work with in Windows.   I have a lot of respect for the work the Arux is doing!

[monero-otc]

Anyone wishing to purchase AEON on Bittrex should be aware that they are having some issues with withdrawals.  I've had two withdrawals stuck for a long time now with no resolution.  One for several hours and another one for more than 24 hours.  Both show on the site as complete but are not on the blockchain.  I have opened a support ticket and had some back and forth with them--it is now "escalated" to someone more technical, whatever that means.

Thought I would mention it for those interested in buying on there.  Here is the txid they report on the site for one of the missing withdrawals:

684b32e04cb4b8061dbc7bb1363b66316bd45d8e75e5f9024945985409436744

(not showing on chainradar or minergate though)