NONO

Copyright (c) 2026, the NONO contributors Copyright (c) 2014-2024, The Monero Project (upstream codebase) Portions Copyright (c) 2012-2013 The Cryptonote developers

NONO is a fair-launch, CPU-mined privacy currency. It is a fork of Monero with an independent network, a separate emission curve, and no insider allocations. Privacy properties, the RandomX proof-of-work, and the broader Cryptonote machinery are inherited from Monero unchanged.

Official Links

• 🌐 Website: https://nonoprivacy.com

• 𝕏 X: https://x.com/nonocoin

• 💬 Discord: https://discord.gg/Tuwt6TAbJw

• 📢 Telegram: https://t.me/nonoprivacy

• Total emission target: 88,888,888 NONO (asymptotic, pre-tail)

• Block time: 60 seconds

• Decimals: 10

• Proof of work: RandomX (CPU-friendly, ASIC-resistant)

• Initial block reward: ~42.38 NONO

• Tail emission: 1.45 NONO/block (~1.45 NONO/min)

• Privacy: RingCT, stealth addresses, bulletproofs+ — all unchanged from Monero

• No premine. No dev tax. No founder allocation. The genesis coinbase output is derived from deterministic NUMS pubkeys with no known private key, so it is provably unspendable — see utils/genesis/derive_nums_pubkeys.py.

Why NONO

Modern privacy currencies tend to centralize over time: GPU mining concentrates hash rate in industrial farms, premines reward early insiders, dev funds nudge governance, and "fair-launch" claims often come with quiet exceptions. NONO is an attempt to push back on all four at once:

• Fair launch. No premine. No reserved allocation. No team address. The genesis coinbase is unspendable by construction. Every NONO in circulation was mined.
• CPU-friendly. Inherits Monero's RandomX. The chain is intentionally inhospitable to specialized hardware, and the 60-second block target and slower per-minute emission curve give small miners more time to onboard.
• Privacy without theater. The same RingCT / stealth address / bulletproofs+ stack that secures Monero today. NONO does not invent new cryptography; it inherits a well-reviewed one.
• No governance capture. No foundation. No multisig treasury. Issues and PRs live in this GitHub repository.

NONO is a fork — not Monero

NONO ships its own:

• network id, magic bytes, address prefixes, P2P/RPC/ZMQ ports, and seed-node policy
• genesis transaction (different output amount, NONO-derived NUMS pubkeys, separate nonce per network)
• emission curve scaled to 10 decimals (EMISSION_SPEED_FACTOR_PER_MINUTE = 21, intentionally a slower/fairer launch curve than Monero's)
• daemon binary (nonod) and wallet binaries (nono-wallet-cli, nono-wallet-rpc)
• empty checkpoint table and empty DNS bootstrap lists, pending NONO infrastructure
• no donate command and no hardcoded donation address — fair-launch chain, nothing to donate to

What NONO does not change: RingCT, stealth addresses, bulletproofs+, RandomX, the ring signature scheme, or any other consensus or cryptographic primitive carried over from Monero. NONO inherits these unchanged and gives full credit to upstream.

Attribution

NONO is built directly on the Monero source tree and would not exist without the work of the Monero Project and the Cryptonote authors. Where this README, the source comments, or the citation list refer to research papers, protocol design, or the broader Cryptonote/RingCT/RandomX literature, those references point back to the Monero ecosystem on purpose and should stay that way.

• Upstream codebase: https://github.com/monero-project/monero
• This NONO repository: https://github.com/hempmillionaire/Nono
• Monero Research Lab publications: cited inline in source where relevant
• RandomX specification: https://github.com/tevador/RandomX

The Monero Project, Monero Research Lab, and Cryptonote authors are not affiliated with NONO and have not endorsed it. Any bugs introduced by NONO's changes are NONO's responsibility, not theirs.

License

This software inherits Monero's BSD 3-Clause license. See LICENSE for the full text. NONO's own changes are released under the same license.

Contributing

NONO is a small project. The repository on GitHub is the source of truth, and pull requests against master are welcome.

Community

• Website: https://nonoprivacy.com
• X: https://x.com/nonocoin
• Discord: https://discord.gg/Tuwt6TAbJw
• Telegram: https://t.me/nonoprivacy

Questions, development discussion, and community support happen in Discord.

If you are submitting a change that touches consensus (anything in cryptonote_config.h, the emission formula, the genesis transaction, or protocol versions), please flag it explicitly in the PR description. NONO's policy is to stop touching consensus once the chain is live unless tests prove a change is required.

Scheduled software/network upgrades

NONO starts at block 0 with all features from Monero's v16 protocol active (RingCT, bulletproofs+, view tags, CLSAG, RandomX). No NONO hardforks are scheduled. The table below is the inherited Monero hardfork history and is preserved for protocol context only — it does not apply to NONO's chain, because NONO never ran those forks. NONO's first block is its own genesis.

Future NONO upgrades, if any, will be added here once they are designed, tested, and scheduled. The project's stated policy is to stop touching consensus once mainnet is live unless tests prove a change is necessary.

Software upgrade block height	Date	Fork version	Minimum Monero version	Recommended Monero version	Details
1009827	2016-03-22	v2	v0.9.4	v0.9.4	Allow only >= ringsize 3, blocktime = 120 seconds, fee-free blocksize 60 kb
1141317	2016-09-21	v3	v0.9.4	v0.10.0	Splits coinbase into denominations
1220516	2017-01-05	v4	v0.10.1	v0.10.2.1	Allow normal and RingCT transactions
1288616	2017-04-15	v5	v0.10.3.0	v0.10.3.1	Adjusted minimum blocksize and fee algorithm
1400000	2017-09-16	v6	v0.11.0.0	v0.11.0.0	Allow only RingCT transactions, allow only >= ringsize 5
1546000	2018-04-06	v7	v0.12.0.0	v0.12.3.0	Cryptonight variant 1, ringsize >= 7, sorted inputs
1685555	2018-10-18	v8	v0.13.0.0	v0.13.0.4	max transaction size at half the penalty free block size, bulletproofs enabled, cryptonight variant 2, fixed ringsize 11
1686275	2018-10-19	v9	v0.13.0.0	v0.13.0.4	bulletproofs required
1788000	2019-03-09	v10	v0.14.0.0	v0.14.1.2	New PoW based on Cryptonight-R, new block weight algorithm, slightly more efficient RingCT format
1788720	2019-03-10	v11	v0.14.0.0	v0.14.1.2	forbid old RingCT transaction format
1978433	2019-11-30	v12	v0.15.0.0	v0.16.0.0	New PoW based on RandomX, only allow >= 2 outputs, change to the block median used to calculate penalty, v1 coinbases are forbidden, rct sigs in coinbase forbidden, 10 block lock time for incoming outputs
2210000	2020-10-17	v13	v0.17.0.0	v0.17.3.2	New CLSAG transaction format
2210720	2020-10-18	v14	v0.17.1.1	v0.17.3.2	forbid old MLSAG transaction format
2688888	2022-08-13	v15	v0.18.0.0	v0.18.5.0	ringsize = 16, bulletproofs+, view tags, adjusted dynamic block weight algorithm
2689608	2022-08-14	v16	v0.18.0.0	v0.18.5.0	forbid old v14 transaction format
XXXXXXX	XXX-XX-XX	XXX	vX.XX.X.X	vX.XX.X.X	XXX

X's indicate that these details have not been determined as of commit date.

* indicates estimate as of commit date

Release staging schedule and protocol

Approximately three months prior to a scheduled software upgrade, a branch from master will be created with the new release version tag. Pull requests that address bugs should then be made to both master and the new release branch. Pull requests that require extensive review and testing (generally, optimizations and new features) should not be made to the release branch.

Compiling NONO from source

Dependencies

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	Void pkg	Fedora pkg	Optional	Purpose
GCC	7	NO	build-essential	base-devel	base-devel	gcc	NO
CMake	3.10	NO	cmake	cmake	cmake	cmake	NO
pkg-config	any	NO	pkg-config	base-devel	base-devel	pkgconf	NO
Boost	1.66	NO	libboost-all-dev	boost	boost-devel	boost-devel	NO	C++ libraries
OpenSSL	1.1.1	NO	libssl-dev	openssl	openssl-devel	openssl-devel	NO	cryptography
libzmq	4.2.0	NO	libzmq3-dev	zeromq	zeromq-devel	zeromq-devel	NO	ZeroMQ library
libunbound	1.4.16	NO	libunbound-dev	unbound	unbound-devel	unbound-devel	NO	DNS resolver
libsodium	?	NO	libsodium-dev	libsodium	libsodium-devel	libsodium-devel	NO	cryptography
libunwind	any	NO	libunwind8-dev	libunwind	libunwind-devel	libunwind-devel	YES	Stack traces
libreadline	6.3.0	NO	libreadline6-dev	readline	readline-devel	readline-devel	YES	Input editing
GTest	1.5	YES	libgtest-dev	gtest	gtest-devel	gtest-devel	YES	Test suite
ccache	any	NO	ccache	ccache	ccache	ccache	YES	Compil. cache
Doxygen	any	NO	doxygen	doxygen	doxygen	doxygen	YES	Documentation
Graphviz	any	NO	graphviz	graphviz	graphviz	graphviz	YES	Documentation
lrelease	?	NO	qttools5-dev-tools	qt5-tools	qt5-tools	qt5-linguist	YES	Translations
libhidapi	?	NO	libhidapi-dev	hidapi	hidapi-devel	hidapi-devel	YES	Hardware wallet
libusb	?	NO	libusb-1.0-0-dev	libusb	libusb-devel	libusbx-devel	YES	Hardware wallet
libprotobuf	?	NO	libprotobuf-dev	protobuf	protobuf-devel	protobuf-devel	YES	Hardware wallet
protoc	?	NO	protobuf-compiler	protobuf	protobuf	protobuf-compiler	YES	Hardware wallet

Install all dependencies at once on Debian/Ubuntu:

sudo apt update && sudo apt install build-essential cmake pkg-config libssl-dev libzmq3-dev libunbound-dev libsodium-dev libunwind8-dev libreadline6-dev qttools5-dev-tools libhidapi-dev libusb-1.0-0-dev libprotobuf-dev protobuf-compiler libboost-chrono-dev libboost-date-time-dev libboost-filesystem-dev libboost-locale-dev libboost-program-options-dev libboost-regex-dev libboost-serialization-dev libboost-system-dev libboost-thread-dev python3 ccache doxygen graphviz git curl

Install all dependencies at once on Arch:

sudo pacman -Syu --needed base-devel cmake boost boost-libs openssl zeromq unbound libsodium libunwind readline python3 ccache doxygen graphviz qt5-tools hidapi libusb protobuf

Install all dependencies at once on Fedora:

sudo dnf install gcc gcc-c++ cmake pkgconf boost-devel openssl-devel zeromq-devel unbound-devel libsodium-devel libunwind-devel readline-devel ccache doxygen graphviz qt5-linguist hidapi-devel libusbx-devel protobuf-devel protobuf-compiler

Install all dependencies at once on openSUSE:

sudo zypper ref && sudo zypper in cppzmq-devel libboost_chrono-devel libboost_date_time-devel libboost_filesystem-devel libboost_locale-devel libboost_program_options-devel libboost_regex-devel libboost_serialization-devel libboost_system-devel libboost_thread-devel libsodium-devel libunwind-devel unbound-devel cmake doxygen ccache fdupes gcc-c++ libevent-devel libopenssl-devel pkgconf-pkg-config readline-devel libqt5-qttools-devel patterns-devel-C-C++-devel_C_C++

Install all dependencies at once on macOS with the provided Brewfile:

brew update && brew bundle --file=contrib/brew/Brewfile

FreeBSD 12.1 one-liner required to build dependencies:

pkg install git gmake cmake pkgconf boost-libs libzmq4 libsodium unbound

Cloning the repository

Clone recursively to pull-in needed submodule(s):

git clone --recursive https://github.com/hempmillionaire/Nono

If you already have a repo cloned, initialize and update:

cd Nono && git submodule init && git submodule update

Note: If there are submodule differences between branches, you may need to use git submodule sync && git submodule update after changing branches to build successfully.

Build instructions

NONO uses the CMake build system and a top-level Makefile that invokes cmake commands as needed.

On Linux and macOS

• Install the dependencies

• Change to the root of the source code directory and build. NONO has not tagged its first release yet, so for now build from master. Once a release tag exists (e.g. v0.1.0), git checkout v0.1.0 before make:

  cd Nono
  make

  Optional: If your machine has several cores and enough memory, enable parallel build by running make -j<number of threads> instead of make. For this to be worthwhile, the machine should have one core and about 2GB of RAM available per thread.

  Note: until NONO publishes a release tag, the instructions above build from the current master branch. Once a release tag exists, pinning to it with git checkout vX.Y.Z is the safer default; master continues to move and may contain updates that are unstable or incompatible with release software.

• The resulting executables can be found in build/release/bin

• Add PATH="$PATH:$HOME/Nono/build/release/bin" to .profile

• Run NONO with nonod --detach

• Optional: build and run the test suite to verify the binaries:

  make release-test

  NOTE: core_tests test may take a few hours to complete.

• Optional: to build binaries suitable for debugging:

  make debug

• Optional: build documentation in doc/html (omit HAVE_DOT=YES if graphviz is not installed):

  HAVE_DOT=YES doxygen Doxyfile

• Optional: use ccache not to rebuild translation units, that haven't really changed. the CMakeLists.txt file automatically handles it

  sudo apt install ccache

On the Raspberry Pi

Tested on a Raspberry Pi 5B with a clean installation of Raspberry Pi OS (64-bit) with Debian 12 from https://www.raspberrypi.com/software/operating-systems/.

• apt-get update && apt-get upgrade to install the latest software

• Install the build dependencies from the 'Debian' column in the table above.

• Optional: 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 NONO. NONO has no tagged releases yet, so build from master for now. Once a release tag exists, add git checkout vX.Y.Z before the build step:

  git clone --recursive https://github.com/hempmillionaire/Nono.git
  cd Nono

• Build:

  USE_SINGLE_BUILDDIR=1 make release

• Wait a few hours

• The resulting executables can be found in build/release/bin

• Add export PATH="$PATH:$HOME/Nono/build/release/bin" to $HOME/.profile

• Run source $HOME/.profile

• Run NONO with nonod --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

On Windows:

Binaries for Windows can be 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. Installing MSYS2 requires 64-bit Windows 10 or newer.

• Open the MSYS shell via the MSYS2 MSYS shortcut

• Update packages using pacman:

  pacman -Syu

• Install dependencies:

  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-libsodium mingw-w64-x86_64-hidapi mingw-w64-x86_64-unbound

• Open the MingW shell via MSYS2 MINGW64 shortcut.

Cloning

• To git clone, run:

  git clone --recursive https://github.com/hempmillionaire/Nono.git

Building

• Change to the cloned directory, run:

  cd Nono

• If a NONO release tag exists by the time you're reading this, you can pin to it via the tags list — git checkout vX.Y.Z. NONO has not tagged its first release yet, so for now skip this step and just build from master.

• To build NONO, run:

  make release-static -j $(nproc)

  The resulting executables can be found in build/release/bin

• Optional: to build Windows binaries suitable for debugging, run:

  make debug -j $(nproc)

  The resulting executables can be found in build/debug/bin

On FreeBSD:

The project can be built from scratch by following instructions for Linux above(but use gmake instead of make). If you are running NONO in a jail, you need to add sysvsem="new" to your jail configuration, otherwise lmdb will throw the error message: Failed to open lmdb environment: Function not implemented.

(NONO ships no packaged distribution yet — build from source.)

On OpenBSD:

You will need to add a few packages to your system. pkg_add cmake gmake zeromq libiconv boost libunbound.

The doxygen and graphviz packages are optional and require the xbase set. Running the test suite also requires py3-requests package.

Build NONO: gmake

Note: you may encounter the following error when compiling the latest version of NONO as a normal user:

LLVM ERROR: out of memory
c++: error: unable to execute command: Abort trap (core dumped)

Then you need to increase the data ulimit size to 2GB and try again: ulimit -d 2000000

On NetBSD:

Check that the dependencies are present: pkg_info -c libexecinfo boost-headers boost-libs protobuf readline libusb1 zeromq git-base pkgconf gmake cmake | more, and install any that are reported missing, using pkg_add or from your pkgsrc tree. Readline is optional but worth having.

Third-party dependencies are usually under /usr/pkg/, but if you have a custom setup, adjust the "/usr/pkg" (below) accordingly.

Clone the NONO repository recursively and checkout the most recent release as described above. Then build NONO: gmake BOOST_ROOT=/usr/pkg LDFLAGS="-Wl,-R/usr/pkg/lib" release. The resulting executables can be found in build/NetBSD/[Release version]/Release/bin/.

On Solaris:

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.

Cross Compiling

You can also cross-compile static binaries on Linux for Windows and macOS with the depends system.

• make depends target=x86_64-linux-gnu for 64-bit linux binaries.
• make depends target=x86_64-w64-mingw32 for 64-bit windows binaries.
  • Requires: g++-mingw-w64-x86-64
  • You also need to run:

    update-alternatives --set x86_64-w64-mingw32-g++ $(which x86_64-w64-mingw32-g++-posix) && \
    update-alternatives --set x86_64-w64-mingw32-gcc $(which x86_64-w64-mingw32-gcc-posix)

• make depends target=x86_64-apple-darwin for Intel macOS binaries.
  • Requires: clang-18 lld-18
• make depends target=arm64-apple-darwin for Apple Silicon macOS binaries.
  • Requires: clang-18 lld-18
  • You also need to run:

    export PATH="/usr/lib/llvm-18/bin/:$PATH"

• make depends target=i686-linux-gnu for 32-bit linux binaries.
  • Requires: g++-multilib bc
• make depends target=i686-w64-mingw32 for 32-bit windows binaries.
  • Requires: python3 g++-mingw-w64-i686
• make depends target=arm-linux-gnueabihf for armv7 binaries.
  • Requires: g++-arm-linux-gnueabihf
• make depends target=aarch64-linux-gnu for armv8 binaries.
  • Requires: g++-aarch64-linux-gnu
• make depends target=riscv64-linux-gnu for RISC V 64 bit binaries.
  • Requires: g++-riscv64-linux-gnu
• make depends target=x86_64-unknown-freebsd for freebsd binaries.
  • Requires: clang-8
• make depends target=arm-linux-android for 32bit android binaries
• make depends target=aarch64-linux-android for 64bit android binaries

The required packages are the names for each toolchain on apt. Depending on your distro, they may have different names. The depends system has been tested on Ubuntu 18.04 and 20.04.

Using depends might also be easier to compile NONO 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.

The produced binaries still link libc dynamically. If the binary is compiled on a current distribution, it might not run on an older distribution with an older installation of libc.

Trezor hardware wallet support

If you have an issue with building NONO with Trezor support, you can disable it by setting USE_DEVICE_TREZOR=OFF, e.g.,

USE_DEVICE_TREZOR=OFF make release

For more information, please check out Trezor src/device_trezor/README.md.

Guix builds

See contrib/guix/README.md.

Installing NONO from a package

NONO does not ship pre-built packages yet. Build from source per the section above. Once mainnet stabilises and a release artifact pipeline is set up, packages for the common distributions will be published here; until then, git clone and make release is the supported path.

Running nonod

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 the foreground:

./bin/nonod

To list all available options, run ./bin/nonod --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/nonod --log-file nonod.log --detach

To run as a systemd service, copy nonod.service to /etc/systemd/system/ and nonod.conf to /etc/. The example service assumes that the user nono 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 nono-wallet-cli, and possibly nonod, if you get crashes refreshing.

Internationalization

See README.i18n.md.

Using Tor

There is a new, still experimental, integration with Tor. The feature allows connecting over IPv4 and Tor simultaneously - IPv4 is used for relaying blocks and relaying transactions received by peers whereas Tor is used solely for relaying transactions received over local RPC. This provides privacy and better protection against surrounding node (sybil) attacks.

NONO is not designed to integrate with Tor directly, but it can be wrapped with torsocks by setting the following configuration parameters and environment variables (the same guidance that applies to Monero's daemon applies here, since the network stack is inherited):

• --p2p-bind-ip 127.0.0.1 on the command line or p2p-bind-ip=127.0.0.1 in nonod.conf to disable listening for connections on external interfaces.
• If you use the wallet with a Tor daemon via the loopback IP (eg, 127.0.0.1:9050), then use --untrusted-daemon unless it is your own hidden service.

Example command line to start nonod through Tor:

nonod --proxy 127.0.0.1:9050 --p2p-bind-ip 127.0.0.1

A helper script is in contrib/tor/nono-over-tor.sh. It assumes Tor is installed already, and runs Tor and nonod with the right configuration.

Using Tor on Tails

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 24701 -j ACCEPT
DNS_PUBLIC=tcp torsocks ./nonod --p2p-bind-ip 127.0.0.1 --rpc-bind-ip 127.0.0.1 \
    --data-dir /home/amnesia/Persistent/your/directory/to/the/blockchain

Pruning

NONO's chain is fresh and currently tiny. There is no firm blockchain-size guidance yet — operators running the very first nodes can expect the database to grow at roughly the per-block weight allowed by the protocol, so for 60s blocks with the inherited Monero block-weight ceiling, an idle chain accumulates ~MB per day, scaling with usage. A pruned blockchain still serves at least the recent 5,500 blocks of historical data to other peers and is otherwise functionally identical to a full node. To use a pruned blockchain, it is best to start the initial sync with --prune-blockchain. However, it is also possible to prune an existing blockchain using the nono-blockchain-prune tool or using the --prune-blockchain nonod option with an existing chain. If an existing chain exists, pruning will temporarily require disk space to store both the full and pruned blockchains.

For more detailed information see the 'Pruning' entry in the Moneropedia

Debugging

This section contains general instructions for debugging failed installs or problems encountered with NONO. First, ensure you are running the latest version built from the GitHub repo.

Obtaining stack traces and core dumps on Unix systems

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/nonod `pidof nonod`

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 nonod. 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/nonod /path/to/dumpfile`

Print the stack trace with bt

• If a program crashed and cores are managed by systemd, the following can also get a stack trace for that crash:

coredumpctl -1 gdb

To run nonod within gdb:

Type gdb /path/to/nonod

Pass command-line options with --args followed by the relevant arguments

Type run to run nonod

Analysing memory corruption

There are two tools available:

ASAN

Configure NONO 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 NONO tools normally. Performance will typically halve.

valgrind

Install valgrind and run as valgrind /path/to/nonod. It will be very slow.

LMDB

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 ~/Nono/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.

Known Issues

Protocols

Socket-based

Because of the nature of the socket-based protocols that drive NONO, certain protocol weaknesses are somewhat unavoidable at this time. While these weaknesses can theoretically be fully mitigated, the effort required (the means) may not justify the ends. As such, please consider taking the following precautions if you are a NONO node operator:

• Run nonod on a "secured" machine. If operational security is not your forte, at a very minimum, have a dedicated a computer running nonod and do not browse the web, use email clients, or use any other potentially harmful apps on your nonod machine. Do not click links or load URL/MUA content on the same machine. Doing so may potentially exploit weaknesses in commands which accept "localhost" and "127.0.0.1".
• If you plan on hosting a public "remote" node, start nonod with --restricted-rpc. This is a must.

Blockchain-based

Certain blockchain "features" can be considered "bugs" if misused correctly. Consequently, please consider the following:

• When receiving NONO, be aware that it may be locked for an arbitrary time if the sender elected to, preventing you from spending that NONO until the lock time expires. You may want to hold off acting upon such a transaction until the unlock time lapses. To get a sense of that time, you can consider the remaining blocktime until unlock as seen in the show_transfers command.