Copyright (c) 2014-2022, AEON, The Monero Project.
Portions Copyright (c) 2012-2013 The Cryptonote developers.
- Web: aeon.cash
- Bitcointalk: https://bitcointalk.org/index.php?topic=641696.0
- Reddit: https://www.reddit.com/r/Aeon
- GitHub: https://github.com/aeonix/aeon
- IRC: #aeon on Libera
- Discord: https://discord.gg/TM8mEsx
- Vulnerability response should be redirected to Monero because much of Aeon's technical ground is shared
- Our Vulnerability Response Process encourages responsible disclosure
- We are also available via HackerOne
- You can subscribe to an announcement list to get critical announcements from the Aeon core team. The announcement list can be very helpful for knowing when software updates are needed.
| Type | Status |
|---|---|
| License |  |
Aeon is a private, secure, untraceable, decentralised digital currency. You are your bank, you control your funds, and nobody can trace your transfers unless you allow them to do so.
Privacy: Aeon uses a cryptographically sound system to allow you to send and receive funds without your transactions being easily revealed on the blockchain (the ledger of transactions that everyone has). This ensures that your purchases, receipts, and all transfers remain absolutely private by default.
Security: Using the power of a distributed peer-to-peer consensus network, every transaction on the network is cryptographically secured. Individual wallets have a 25 word mnemonic seed that is only displayed once, and can be written down to backup the wallet. Wallet files are encrypted with a passphrase to ensure they are useless if stolen.
Untraceability: By taking advantage of ring signatures, a special property of a certain type of cryptography, Aeon is able to ensure that transactions are not only untraceable, but have an optional measure of ambiguity that ensures that transactions cannot easily be tied back to an individual user or computer.
This is the core implementation of Aeon. It is open source and completely free to use without restrictions, except for those specified in the license agreement below. There are no restrictions on anyone creating an alternative implementation of Aeon that uses the protocol and network in a compatible manner.
As with many development projects, the repository on Github is considered to be the "staging" area for the latest changes. Before changes are merged into that branch on the main repository, they are tested by individual developers in their own branches, submitted as a pull request, and then subsequently tested by contributors who focus on testing and code reviews. That having been said, the repository should be carefully considered before using it in a production environment, unless there is a patch in the repository for a particular show-stopping issue you are experiencing. It is generally a better idea to use a tagged release for stability.
Anyone is welcome to contribute to Aeon's codebase! If you have a fix or code change, feel free to submit it as a pull request directly to the "master" branch. In cases where the change is relatively small or does not affect other parts of the codebase it may be merged in immediately by any one of the collaborators. On the other hand, if the change is particularly large or complex, it is expected that it will be discussed at length either well in advance of the pull request being submitted, or even directly on the pull request.
Aeon is a 100% community-sponsored endeavor. If you want to join our efforts, the easiest thing you can do is support the project financially. Both Aeon and Bitcoin donations can be made to donate.aeon.cash if using a client that supports the OpenAlias standard. Alternatively you can send AEON to the Aeon donation address via the donate command (type help in the command-line wallet for details).
The Aeon donation address is: WmsSWgtT1JPg5e3cK41hKXSHVpKW7e47bjgiKmWZkYrhSS5LhRemNyqayaSBtAQ6517eo5PtH9wxHVmM78JDZSUu2W8PqRiNs (viewkey: 71bf19a7348ede17fa487167710dac401ef1556851bfd36b76040facf051630b)
The Bitcoin donation address is: 12Cyjf3qV6qLyXdzpLSLPdRFPUVidvnzFM
Core development funding and/or some supporting services are also graciously provided by sponsors:
There are also several mining pools that kindly donate a portion of their fees, a list of them can be found on our Bitcointalk post.
See LICENSE.
If you want to help out, see CONTRIBUTING for a set of guidelines.
Aeon uses a software upgrade (hard fork) mechanism to implement new features. This means that users of Aeon (end users and service providers) should run current versions and upgrade their software as needed. In contrast to Monero, there is no fixed schedule for hard forks, and the schedule for the next fork will be determined organically through community discussion. The required software for these upgrades will be available prior to the scheduled date. Please check the repository prior to this date for the proper Aeon software version. Below is the historical schedule and the projected schedule for the next upgrade. Dates are provided in the format YYYY-MM-DD.
| Software upgrade block height | Date | Fork version | Minimum Aeon version | Recommended Aeon version | Details |
|---|---|---|---|---|---|
| 592000 | 2015-08-04 | v1 (exceptional, version not bumped) | v0.9.0.0 | v0.9.14.0 | blocktime = 240 seconds, CryptoNight-Lite, lower mining priority for ringsize < 3 |
| 963500 | 2018-06-03 | v7 | v0.12.0.0 | v0.12.9.0-aeon | Rebase to Monero's latest codebase with RingCT disabled, CryptoNight-Lite variant 1, limited use of ringsize 1, ban ringsize 2 |
| 1146200 | 2019-10-25 | v8 | v0.13.0.0-aeon | v0.13.1.0-aeon | Switch to K12 PoW, reduced tx size with Borromean sigs, fixed ringsize 3, long-term block size, enforced 10 block age |
| 1280000 | 2020-11-11 | v9 | v0.14.1.0-aeon | v0.14.2.2-aeon | Difficulty algorithm variant 9 (cut/sort removed, lag reduced to 8), change to the block median used to calculate penalty, deterministic unlock times |
The following table summarizes the tools and libraries required to build. A
few of the libraries are also included in this repository (marked as
"Vendored"). By default, the build uses the library installed on the system,
and ignores the vendored sources. However, if no library is found installed on
the system, then the vendored source will be built and used. The vendored
sources are also used for statically-linked builds because distribution
packages often include only shared library binaries (.so) but not static
library archives (.a).
| Dep | Min. version | Vendored | Debian/Ubuntu pkg | Arch pkg | Fedora | Optional | Purpose |
|---|---|---|---|---|---|---|---|
| GCC | 4.7.3 | NO | build-essential |
base-devel |
gcc |
NO | |
| CMake | 3.5 | NO | cmake |
cmake |
cmake |
NO | |
| pkg-config | any | NO | pkg-config |
base-devel |
pkgconf |
NO | |
| Boost | 1.58 | NO | libboost-all-dev |
boost |
boost-devel |
NO | C++ libraries |
| OpenSSL | basically any | NO | libssl-dev |
openssl |
openssl-devel |
NO | sha256 sum |
| libzmq | 3.0.0 | NO | libzmq3-dev |
zeromq |
cppzmq-devel |
NO | ZeroMQ library |
| OpenPGM | ? | NO | libpgm-dev |
libpgm |
openpgm-devel |
NO | For ZeroMQ |
| libnorm[2] | ? | NO | libnorm-dev |
` | YES | For ZeroMQ | |
| libunbound | 1.4.16 | YES | libunbound-dev |
unbound |
unbound-devel |
NO | DNS resolver |
| libsodium | ? | NO | libsodium-dev |
libsodium |
libsodium-devel |
NO | cryptography |
| libunwind | any | NO | libunwind-dev |
libunwind |
libunwind-devel |
YES | Stack traces |
| liblzma | any | NO | liblzma-dev |
xz |
xz-devel |
YES | For libunwind |
| libreadline | 6.3.0 | NO | libreadline-dev |
readline |
readline-devel |
YES | Input editing |
| ldns | 1.6.17 | NO | libldns-dev |
ldns |
ldns-devel |
YES | SSL toolkit |
| expat | 1.1 | NO | libexpat1-dev |
expat |
expat-devel |
YES | XML parsing |
| GTest | 1.5 | YES | libgtest-dev[1] |
gtest |
gtest-devel |
YES | Test suite |
| Doxygen | any | NO | doxygen |
doxygen |
doxygen |
YES | Documentation |
| Graphviz | any | NO | graphviz |
graphviz |
graphviz |
YES | Documentation |
[1] On Debian/Ubuntu libgtest-dev only includes sources and headers. You must
build the library binary manually. This can be done with the following command sudo apt-get install libgtest-dev && cd /usr/src/gtest && sudo cmake . && sudo make && sudo mv libg* /usr/lib/
[2] libnorm-dev is needed if your zmq library was built with libnorm, and not needed otherwise
[3] Note the differences of Libunwind and Libreadline for 16.04 and 18.04 distros
Install all dependencies at once on Debian/Ubuntu 16.04:
sudo apt update && sudo apt install build-essential cmake git pkg-config libboost-all-dev libssl-dev libzmq3-dev libunbound-dev libsodium-dev libunwind8-dev liblzma-dev libreadline6-dev libldns-dev libexpat1-dev doxygen graphviz libpgm-dev
Install all dependencies at once on Debian/Ubuntu 18.04:
sudo apt update && sudo apt install build-essential cmake git pkg-config libboost-all-dev libssl-dev libzmq3-dev libunbound-dev libsodium-dev libunwind-dev liblzma-dev libreadline-dev libldns-dev libexpat1-dev doxygen graphviz libpgm-dev libnorm-dev
Clone recursively to pull-in needed submodule(s):
$ git clone --recursive https://github.com/aeonix/aeon
If you already have a repo cloned, initialize and update:
$ cd aeon && git submodule init && git submodule update
Aeon uses the CMake build system and a top-level Makefile that invokes cmake commands as needed.
-
Install the dependencies
-
Change to the root of the source code directory, change to the most recent release tag, and build:
cd aeon git checkout v0.14.2.2-aeon makeOptional: If your machine has several cores and enough memory, enable parallel build by running
make -j<number of threads>instead ofmake. For this to be worthwhile, the machine should have one core and about 2GB of RAM available per thread.Note: If cmake can not find zmq.hpp file on OS X, installing
zmq.hppfrom https://github.com/zeromq/cppzmq to/usr/local/includeshould fix that error.Note: The instructions above will compile the most stable release of the Aeon software. If you would like to use and test the most recent software, use
git checkout master. The master branch may contain updates that are both unstable and incompatible with release software, though testing is always encouraged. -
The resulting executables can be found in
build/release/bin -
Add
PATH="$PATH:$HOME/aeon/build/release/bin"to.profile -
Run Aeon with
aeond --detach -
Optional: build and run the test suite to verify the binaries:
make release-testNOTE:
core_teststest may take a few hours to complete. -
Optional: to build binaries suitable for debugging:
make debug -
Optional: to build statically-linked binaries:
make release-static
Dependencies need to be built with -fPIC. Static libraries usually aren't, so you may have to build them yourself with -fPIC. Refer to their documentation for how to build them.
-
Optional: build documentation in
doc/html(omitHAVE_DOT=YESifgraphvizis not installed):HAVE_DOT=YES doxygen Doxyfile
Tested on a Raspberry Pi Zero with a clean install of minimal Raspbian Stretch (2017-09-07 or later) from https://www.raspberrypi.org/downloads/raspbian/. If you are using Raspian Jessie, please see note in the following section.
-
apt-get update && apt-get upgradeto install all of the latest software -
Install the dependencies for Aeon from the 'Debian' column in the table above.
-
Increase the system swap size:
sudo /etc/init.d/dphys-swapfile stop
sudo nano /etc/dphys-swapfile
CONF_SWAPSIZE=2048
sudo /etc/init.d/dphys-swapfile start
-
If using an external hard disk without an external power supply, ensure it gets enough power to avoid hardware issues when syncing, by adding the line "max_usb_current=1" to /boot/config.txt
-
Clone Aeon and checkout most recent release version:
git clone https://github.com/aeonix/aeon.git
cd aeon
git checkout tags/v0.14.2.2-aeon
- Build:
make release
-
Wait 4-6 hours
-
The resulting executables can be found in
build/release/bin -
Add
PATH="$PATH:$HOME/aeon/build/release/bin"to.profile -
Run Aeon with
aeond --detach -
You may wish to reduce the size of the swap file after the build has finished, and delete the boost directory from your home directory
If you are using the older Raspbian Jessie image, compiling Aeon is a bit more complicated. The version of Boost available in the Debian Jessie repositories is too old to use with Aeon, and thus you must compile a newer version yourself. The following explains the extra steps, and has been tested on a Raspberry Pi 2 with a clean install of minimal Raspbian Jessie.
- As before,
apt-get update && apt-get upgradeto install all of the latest software, and increase the system swap size
sudo /etc/init.d/dphys-swapfile stop
sudo nano /etc/dphys-swapfile
CONF_SWAPSIZE=2048
sudo /etc/init.d/dphys-swapfile start
-
Then, install the dependencies for Aeon except
libunwindandlibboost-all-dev -
Install the latest version of boost (this may first require invoking
apt-get remove --purge libboost*to remove a previous version if you're not using a clean install):
cd
wget https://sourceforge.net/projects/boost/files/boost/1.64.0/boost_1_64_0.tar.bz2
tar xvfo boost_1_64_0.tar.bz2
cd boost_1_64_0
./bootstrap.sh
sudo ./b2
- Wait ~8 hours
sudo ./bjam cxxflags=-fPIC cflags=-fPIC -a install
-
Wait ~4 hours
-
From here, follow the general Raspberry Pi instructions from the "Clone Aeon and checkout most recent release version" step.
Binaries for Windows are built on Windows using the MinGW toolchain within MSYS2 environment. The MSYS2 environment emulates a POSIX system. The toolchain runs within the environment and cross-compiles binaries that can run outside of the environment as a regular Windows application.
Preparing the build environment
-
Download and install the MSYS2 installer, either the 64-bit or the 32-bit package, depending on your system.
-
Open the MSYS shell via the
MSYS2 Shellshortcut -
Update packages using pacman:
pacman -Syu -
Exit the MSYS shell using Alt+F4
-
Edit the properties for the
MSYS2 Shellshortcut changing "msys2_shell.bat" to "msys2_shell.cmd -mingw64" for 64-bit builds or "msys2_shell.cmd -mingw32" for 32-bit builds -
Restart MSYS shell via modified shortcut and update packages again using pacman:
pacman -Syu -
Install dependencies:
To build for 64-bit Windows:
pacman -S mingw-w64-x86_64-toolchain make mingw-w64-x86_64-cmake mingw-w64-x86_64-boost mingw-w64-x86_64-openssl mingw-w64-x86_64-zeromq mingw-w64-x86_64-libsodiumTo build for 32-bit Windows:
pacman -S mingw-w64-i686-toolchain make mingw-w64-i686-cmake mingw-w64-i686-boost mingw-w64-i686-openssl mingw-w64-i686-zeromq mingw-w64-i686-libsodium -
Open the MingW shell via
MinGW-w64-Win64 Shellshortcut on 64-bit Windows orMinGW-w64-Win64 Shellshortcut on 32-bit Windows. Note that if you are running 64-bit Windows, you will have both 64-bit and 32-bit MinGW shells.
Cloning
-
To git clone, run:
git clone --recursive https://github.com/aeonix/aeon.git
Building
-
Change to the cloned directory, run:
cd aeon -
If you would like a specific version/tag, do a git checkout for that version. eg. 'v0.14.2.2-aeon'. If you dont care about the version and just want binaries from master, skip this step:
git checkout v0.14.2.2-aeon -
If you are on a 64-bit system, run:
make release-static-win64 -
If you are on a 32-bit system, run:
make release-static-win32 -
The resulting executables can be found in
build/release/bin -
Optional: to build Windows binaries suitable for debugging on a 64-bit system, run:
make debug-static-win64 -
Optional: to build Windows binaries suitable for debugging on a 32-bit system, run:
make debug-static-win32 -
The resulting executables can be found in
build/debug/bin
The project can be built from scratch by following instructions for Linux above. If you are running Aeon in a jail you need to add the flag: allow.sysvipc=1 to your jail configuration, otherwise lmdb will throw the error message: Failed to open lmdb environment: Function not implemented.
We expect to add Aeon into the ports tree in the near future, which will aid in managing installations using ports or packages.
This has been tested on OpenBSD 5.8.
You will need to add a few packages to your system. pkg_add db cmake gcc gcc-libs g++ gtest.
The doxygen and graphviz packages are optional and require the xbase set.
The Boost package has a bug that will prevent librpc.a from building correctly. In order to fix this, you will have to Build boost yourself from scratch. Follow the directions here (under "Building Boost"): https://github.com/bitcoin/bitcoin/blob/master/doc/build-openbsd.md
You will have to add the serialization, date_time, and regex modules to Boost when building as they are needed by Aeon.
To build: env CC=egcc CXX=eg++ CPP=ecpp DEVELOPER_LOCAL_TOOLS=1 BOOST_ROOT=/path/to/the/boost/you/built make release-static-64
You will need to add a few packages to your system. pkg_add cmake zeromq libiconv.
The doxygen and graphviz packages are optional and require the xbase set.
Build the Boost library using clang. This guide is derived from: https://github.com/bitcoin/bitcoin/blob/master/doc/build-openbsd.md
We assume you are compiling with a non-root user and you have doas enabled.
Note: do not use the boost package provided by OpenBSD, as we are installing boost to /usr/local.
# Create boost building directory
mkdir ~/boost
cd ~/boost
# Fetch boost source
ftp -o boost_1_64_0.tar.bz2 https://netcologne.dl.sourceforge.net/project/boost/boost/1.64.0/boost_1_64_0.tar.bz2
# MUST output: (SHA256) boost_1_64_0.tar.bz2: OK
echo "7bcc5caace97baa948931d712ea5f37038dbb1c5d89b43ad4def4ed7cb683332 boost_1_64_0.tar.bz2" | sha256 -c
tar xfj boost_1_64_0.tar.bz2
# Fetch and apply boost patches, required for OpenBSD
ftp -o boost_test_impl_execution_monitor_ipp.patch https://raw.githubusercontent.com/openbsd/ports/bee9e6df517077a7269ff0dfd57995f5c6a10379/devel/boost/patches/patch-boost_test_impl_execution_monitor_ipp
ftp -o boost_config_platform_bsd_hpp.patch https://raw.githubusercontent.com/openbsd/ports/90658284fb786f5a60dd9d6e8d14500c167bdaa0/devel/boost/patches/patch-boost_config_platform_bsd_hpp
# MUST output: (SHA256) boost_config_platform_bsd_hpp.patch: OK
echo "1f5e59d1154f16ee1e0cc169395f30d5e7d22a5bd9f86358f738b0ccaea5e51d boost_config_platform_bsd_hpp.patch" | sha256 -c
# MUST output: (SHA256) boost_test_impl_execution_monitor_ipp.patch: OK
echo "30cec182a1437d40c3e0bd9a866ab5ddc1400a56185b7e671bb3782634ed0206 boost_test_impl_execution_monitor_ipp.patch" | sha256 -c
cd boost_1_64_0
patch -p0 < ../boost_test_impl_execution_monitor_ipp.patch
patch -p0 < ../boost_config_platform_bsd_hpp.patch
# Start building boost
echo 'using clang : : c++ : <cxxflags>"-fvisibility=hidden -fPIC" <linkflags>"" <archiver>"ar" <striper>"strip" <ranlib>"ranlib" <rc>"" : ;' > user-config.jam
./bootstrap.sh --without-icu --with-libraries=chrono,filesystem,program_options,system,thread,test,date_time,regex,serialization,locale --with-toolset=clang
./b2 toolset=clang cxxflags="-stdlib=libc++" linkflags="-stdlib=libc++" -sICONV_PATH=/usr/local
doas ./b2 -d0 runtime-link=shared threadapi=pthread threading=multi link=static variant=release --layout=tagged --build-type=complete --user-config=user-config.jam -sNO_BZIP2=1 -sICONV_PATH=/usr/local --prefix=/usr/local install
Build cppzmq
Build the cppzmq bindings.
We assume you are compiling with a non-root user and you have doas enabled.
# Create cppzmq building directory
mkdir ~/cppzmq
cd ~/cppzmq
# Fetch cppzmq source
ftp -o cppzmq-4.2.3.tar.gz https://github.com/zeromq/cppzmq/archive/v4.2.3.tar.gz
# MUST output: (SHA256) cppzmq-4.2.3.tar.gz: OK
echo "3e6b57bf49115f4ae893b1ff7848ead7267013087dc7be1ab27636a97144d373 cppzmq-4.2.3.tar.gz" | sha256 -c
tar xfz cppzmq-4.2.3.tar.gz
# Start building cppzmq
cd cppzmq-4.2.3
mkdir build
cd build
cmake ..
doas make install
Build Aeon: env DEVELOPER_LOCAL_TOOLS=1 BOOST_ROOT=/usr/local make release-static
The default Solaris linker can't be used, you have to install GNU ld, then run cmake manually with the path to your copy of GNU ld:
mkdir -p build/release
cd build/release
cmake -DCMAKE_LINKER=/path/to/ld -D CMAKE_BUILD_TYPE=Release ../..
cd ../..
Then you can run make as usual.
# Build image (for ARM 32-bit)
docker build -f utils/build_scripts/android32.Dockerfile -t aeon-android .
# Build image (for ARM 64-bit)
docker build -f utils/build_scripts/android64.Dockerfile -t aeon-android .
# Create container
docker create -it --name aeon-android aeon-android bash
# Get binaries
docker cp aeon-android:/src/build/release/bin .
By default, in either dynamically or statically linked builds, binaries target the specific host processor on which the build happens and are not portable to other processors. Portable binaries can be built using the following targets:
make release-static-linux-x86_64builds binaries on Linux on x86_64 portable across POSIX systems on x86_64 processorsmake release-static-linux-i686builds binaries on Linux on x86_64 or i686 portable across POSIX systems on i686 processorsmake release-static-linux-armv8builds binaries on Linux portable across POSIX systems on armv8 processorsmake release-static-linux-armv7builds binaries on Linux portable across POSIX systems on armv7 processorsmake release-static-linux-armv6builds binaries on Linux portable across POSIX systems on armv6 processorsmake release-static-win64builds binaries on 64-bit Windows portable across 64-bit Windows systemsmake release-static-win32builds binaries on 64-bit or 32-bit Windows portable across 32-bit Windows systems
You can also cross-compile static binaries on Linux for Windows and macOS with the depends system.
make depends target=x86_64-linux-gnufor 64-bit linux binaries.make depends target=x86_64-w64-mingw32for 64-bit windows binaries. Requires: python3 g++-mingw-w64-x86-64 wine1.6 bcmake depends target=x86_64-apple-darwin11for macOS binaries. Requires: cmake imagemagick libcap-dev librsvg2-bin libz-dev libbz2-dev libtiff-tools python-devmake depends target=i686-linux-gnufor 32-bit linux binaries. Requires: g++-multilib bcmake depends target=i686-w64-mingw32for 32-bit windows binaries. Requires: python3 g++-mingw-w64-i686make depends target=arm-linux-gnueabihffor armv7 binaries. Requires: g++-arm-linux-gnueabihfmake depends target=aarch64-linux-gnufor armv8 binaries. Requires: g++-aarch64-linux-gnu
The required packages are the names for each toolchain on apt. Depending on your distro, they may have different names.
Using depends might also be easier to compile Aeon on Windows than using MSYS. Activate Windows Subsystem for Linux (WSL) with a distro (for example Ubuntu), install the apt build-essentials and follow the depends steps as depicted above.
DISCLAIMER: These packages are not part of this repository or maintained by this project's contributors, and as such, do not go through the same review process to ensure their trustworthiness and security.
Packages are available for
-
(TODO)
Ubuntu and snap supported systems, via a community contributed build.snap install aeon --beta
Installing a snap is very quick. Snaps are secure. They are isolated with all of their dependencies. Snaps also auto update when a new version is released.
-
(TODO)
Arch Linux (via AUR): -
(TODO)
Void Linux:xbps-install -S aeon -
(TODO)
GuixSDguix package -i aeon -
OS X via Homebrew
brew tap sammy007/aeon brew install aeon -v -
Docker
# Build using all available cores docker build -t aeon . # or build using a specific number of cores (reduce RAM requirement) docker build --build-arg NPROC=1 -t aeon . # either run in foreground docker run -it -v /aeon/chain:/root/.aeon -v /aeon/wallet:/wallet -p 11180:11180 aeon # or in background docker run -it -d -v /aeon/chain:/root/.aeon -v /aeon/wallet:/wallet -p 11180:11180 aeon -
The build needs 3 GB space.
-
Wait one hour or more
Packaging for your favorite distribution would be a welcome contribution!
The build places the binary in bin/ sub-directory within the build directory
from which cmake was invoked (repository root by default). To run in
foreground:
./bin/aeond
To list all available options, run ./bin/aeond --help. Options can be
specified either on the command line or in a configuration file passed by the
--config-file argument. To specify an option in the configuration file, add
a line with the syntax argumentname=value, where argumentname is the name
of the argument without the leading dashes, for example log-level=1.
To run in background:
./bin/aeond --log-file aeond.log --detach
To run as a systemd service, copy
aeond.service to /etc/systemd/system/ and
aeond.conf to /etc/. The example
service assumes that the user aeon exists
and its home is the data directory specified in the example
config.
If you're on Mac, you may need to add the --max-concurrency 1 option to
aeon-wallet-cli, and possibly aeond, if you get crashes refreshing.
See README.i18n.md.
While Aeon isn't made to integrate with Tor, it can be used wrapped with torsocks, by setting the following configuration parameters and environment variables:
--p2p-bind-ip 127.0.0.1on the command line orp2p-bind-ip=127.0.0.1in aeond.conf to disable listening for connections on external interfaces.--no-igdon the command line orno-igd=1in aeond.conf to disable IGD (UPnP port forwarding negotiation), which is pointless with Tor.DNS_PUBLIC=tcporDNS_PUBLIC=tcp://x.x.x.xwhere x.x.x.x is the IP of the desired DNS server, for DNS requests to go over TCP, so that they are routed through Tor. When IP is not specified, aeond uses the default list of servers defined in src/common/dns_utils.cpp.TORSOCKS_ALLOW_INBOUND=1to tell torsocks to allow aeond to bind to interfaces to accept connections from the wallet. On some Linux systems, torsocks allows binding to localhost by default, so setting this variable is only necessary to allow binding to local LAN/VPN interfaces to allow wallets to connect from remote hosts. On other systems, it may be needed for local wallets as well.- Do NOT pass
--detachwhen running through torsocks with systemd, (see utils/systemd/aeond.service for details). - If you use the wallet with a Tor daemon via the loopback IP (eg, 127.0.0.1:9050),
then use
--untrusted-daemonunless it is your own hidden service.
Example command line to start aeond through Tor:
DNS_PUBLIC=tcp torsocks aeond --p2p-bind-ip 127.0.0.1 --no-igd
TAILS ships with a very restrictive set of firewall rules. Therefore, you need to add a rule to allow this connection too, in addition to telling torsocks to allow inbound connections. Full example:
sudo iptables -I OUTPUT 2 -p tcp -d 127.0.0.1 -m tcp --dport 11181 -j ACCEPT
DNS_PUBLIC=tcp torsocks ./aeond --p2p-bind-ip 127.0.0.1 --no-igd --rpc-bind-ip 127.0.0.1 \
--data-dir /home/amnesia/Persistent/your/directory/to/the/blockchain
This section contains general instructions for debugging failed installs or problems encountered with Aeon. First ensure you are running the latest version built from the Github repo.
We generally use the tool gdb (GNU debugger) to provide stack trace functionality, and ulimit to provide core dumps in builds which crash or segfault.
- To use gdb in order to obtain a stack trace for a build that has stalled:
Run the build.
Once it stalls, enter the following command:
gdb /path/to/aeond `pidof aeond`
Type thread apply all bt within gdb in order to obtain the stack trace
- If however the core dumps or segfaults:
Enter ulimit -c unlimited on the command line to enable unlimited filesizes for core dumps
Enter echo core | sudo tee /proc/sys/kernel/core_pattern to stop cores from being hijacked by other tools
Run the build.
When it terminates with an output along the lines of "Segmentation fault (core dumped)", there should be a core dump file in the same directory as aeond. It may be named just core, or core.xxxx with numbers appended.
You can now analyse this core dump with gdb as follows:
gdb /path/to/aeond /path/to/dumpfile
Print the stack trace with bt
- To run aeond within gdb:
Type gdb /path/to/aeond
Pass command-line options with --args followed by the relevant arguments
Type run to run aeond
There are two tools available:
- ASAN
Configure Aeon with the -D SANITIZE=ON cmake flag, eg:
cd build/debug && cmake -D SANITIZE=ON -D CMAKE_BUILD_TYPE=Debug ../..
You can then run the aeon tools normally. Performance will typically halve.
- valgrind
Install valgrind and run as valgrind /path/to/aeond. It will be very slow.
Instructions for debugging suspected blockchain corruption as per @HYC
There is an mdb_stat command in the LMDB source that can print statistics about the database but it's not routinely built. This can be built with the following command:
cd ~/aeon/external/db_drivers/liblmdb && make
The output of mdb_stat -ea <path to blockchain dir> will indicate inconsistencies in the blocks, block_heights and block_info table.
The output of mdb_dump -s blocks <path to blockchain dir> and mdb_dump -s block_info <path to blockchain dir> is useful for indicating whether blocks and block_info contain the same keys.
These records are dumped as hex data, where the first line is the key and the second line is the data.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent