Skip to content
Full node

Running a full node

A full node is a program that downloads every block and checks every one of them against every rule. It is how you use Genoryn Krypton without trusting anybody, and how the network stays in the hands of the people who use it. This guide takes you from nothing to a running node on Linux, Windows or macOS.

Start here

What is a full node?

A full node is the program kryptond. It connects to other nodes, downloads the whole blockchain from the first block, and validates it: the proof of work of every block, the zero-knowledge proof of every transfer, that no coin is spent twice, that no block pays out more than the rules allow. After that it keeps up, one block a minute, and passes what it has checked on to others.

The wallet does not need one. Its light mode verifies the proof of work behind what nodes tell it and is a sound choice for everyday use. A full node goes further: it checks everything, and asks nobody.

The point of it

Why a full node is worth running

Nobody can fool you

Your node has verified every GNR you are paid, back to the block that created it. A block that breaks a rule does not exist for it, however much mining power stands behind it.

Validation

Nobody watches you

A wallet on your own node asks no other computer about your payments. Nothing about what you hold or whom you pay leaves the house.

Privacy

The network gets stronger

Your node relays blocks and transactions and serves nodes that are catching up. More honest nodes make the network harder to split or censor.

Network support

The rules stay yours

The rules of Genoryn Krypton are whatever the nodes of the people who accept it enforce. Running one is how you have a say, and the only way.

Your miner depends on no one

A miner gets its work from a node. With your own, no outage or decision of someone else's node can stop it.

Mining

An API of your own

Build on it: an explorer, a shop, a payment checker. The API answers on your computer, with no limits and no one in between.

API
Read this first

Costs and warnings

Running a node is safe and cheap, but not free of things to know.

What you need

Minimum requirements

20 GBof free disk: about 0.5 GB today, with room for years
2 GBof free memory
2 cores64-bit x86 processor; more cores sync faster
TCP 30333open to the internet only if you want to accept other nodes

Windows 10 or 11, Ubuntu 24.04 or newer, Debian 13 or newer, or any system you can build Rust programs on. More in Requirements.

Instructions

Linux

Ubuntu and Debian: the package

For Ubuntu 24.04 or newer and Debian 13 or newer. Open a terminal and download the package and its checksums:

cd ~/Downloads
curl -fLO https://github.com/genoryn/genoryn/releases/download/v1.0.46/genoryn-krypton_1.0.46_amd64.deb
curl -fLO https://github.com/genoryn/genoryn/releases/download/v1.0.46/SHA256SUMS

Check that the package is the one the project published. The line must end in OK:

sha256sum -c SHA256SUMS --ignore-missing

Install it. This puts kryptond, krypton-wallet, krypton-miner and krypton-wallet-cli in /usr/bin:

sudo apt install ./genoryn-krypton_1.0.46_amd64.deb
kryptond --version

Start the node. It prints what it does and keeps running until you press Ctrl+C; the chain is stored in ~/.genoryn-krypton/mainnet:

kryptond

In a second terminal, ask it how far it is:

curl -s http://127.0.0.1:30334/v1/info

The answer shows height, the block your node has reached, and best_peer_height, where the network is. When they are equal, your node is synced.

Run it as a service

To have the node start with the computer and restart by itself, set it up as a systemd service. The package brings a script that creates a user of its own for the node (krypton), stores the chain in /var/lib/krypton and starts the service with the system's sandboxing switched on:

sudo bash /usr/lib/genoryn-krypton/deploy/setup-server.sh mainnet
# is it running?
systemctl status kryptond
# what is it doing?
journalctl -u kryptond -f
# stop it, start it
sudo systemctl stop kryptond
sudo systemctl start kryptond

If ufw is your firewall and it is on, the script opens port 30333 for other nodes. It does not switch a firewall on that was off.

Other distributions

On any x86-64 Linux with glibc 2.39 or newer, use the archive. It holds the same four programs and the same service script:

curl -fLO https://github.com/genoryn/genoryn/releases/download/v1.0.46/genoryn-krypton-1.0.46-linux-x64.tar.gz
curl -fLO https://github.com/genoryn/genoryn/releases/download/v1.0.46/SHA256SUMS
sha256sum -c SHA256SUMS --ignore-missing
tar -xzf genoryn-krypton-1.0.46-linux-x64.tar.gz
cd genoryn-krypton-1.0.46
./kryptond
# or, as a service:
sudo bash ./deploy/setup-server.sh mainnet

From source

On older systems, or to run exactly what you have read. You need Rust 1.89 or newer and nothing else:

git clone https://github.com/genoryn/genoryn
cd genoryn
cargo build --release -p kryptond
./target/release/kryptond

Check the signature too. SHA256SUMS is signed with the project's hybrid post-quantum release key (ML-DSA-87 + SLH-DSA, fingerprint e4567fb116258bdd). With the source code at hand, cargo run --release -p krypton-release -- verify docs/release-key.pub SHA256SUMS SHA256SUMS.sig checks it. The wallet's updater does this by itself before it installs anything.

Instructions

Windows

The easy way: the wallet

  1. Install the wallet

    Download GenorynKrypton-1.0.46-Windows-x64-Setup.exe from Download and run it. It installs for you alone and asks for no administrator rights. The node comes with it.

  2. Create or open a wallet

    Choose a password, write the 24 words on paper.

  3. Switch to full node

    Open Network. Under Connection mode choose Full node: download and validate the whole chain on this computer and press Save. The wallet starts the node and, from now on, asks only it.

  4. Watch it sync

    The Chain card on the same page shows the height your node has reached; Own node says running. You can use the wallet meanwhile.

  5. Optional: accept other nodes

    Tick Let other nodes connect to my full node, press Save, then Stop node and Start my full node. Windows asks once whether the node may accept connections: allow it. Then forward port 30333 on your router (below).

The node runs while the wallet runs. Closing the wallet's window keeps both running while the miner is on; Quit stops everything. The chain is stored in %APPDATA%\GenorynKrypton\mainnet and is kept when you update or remove the program.

Without the wallet: the command line

The node is a program of its own, kryptond.exe, in the folder the wallet was installed to (and in the portable zip). In PowerShell:

cd "$env:LOCALAPPDATA\Programs\Genoryn Krypton"
.\kryptond.exe --version
.\kryptond.exe
# in a second window: how far is it?
(Invoke-RestMethod http://127.0.0.1:30334/v1/info) | Select-Object height, best_peer_height, peers

To start it with Windows, make a task in Task Scheduler that runs kryptond.exe "at log on". Do not run it and the wallet's own node at the same time: they would use the same folder and the same ports.

Instructions

macOS

There is no packaged build for macOS yet, so the node is built from its source code. The project's tests run on macOS with every change. You need the Xcode command-line tools and Rust:

xcode-select --install
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
git clone https://github.com/genoryn/genoryn
cd genoryn
cargo build --release -p kryptond -p krypton-wallet-cli
./target/release/kryptond

The chain is stored in ~/.genoryn-krypton/mainnet. In a second Terminal window, curl -s http://127.0.0.1:30334/v1/info shows how far the node is. macOS asks whether kryptond may accept incoming connections: allow it if you want other nodes to reach yours.

What to expect

The first sync

A new node starts at block 0 and works its way up, verifying as it goes. On a fast desktop processor (Intel Core Ultra 9 285K) it took 32 minutes at block 21,800, on 19 November 2026; a slower computer needs longer, and the time grows with the chain. It may pause and go on; you can stop it at any time and it continues where it was.

While it syncs, a wallet on that node shows payments only up to the block the node has reached. Wait for height to equal best_peer_height before you rely on a balance.

Now what?

Using your node

Point your wallet at it

On the same computer: Network → Full node. From another computer of yours: enter the node's address under Nodes for light mode. The command-line wallet takes --node http://127.0.0.1:30334.

Ask it things

The wallet's Console tab puts questions to your node by command: getblockchaininfo, getpeerinfo, getblock 21000. It completes commands as you type.

The console

Mine on it

The wallet's miner uses your node by itself in full-node mode. On a server: krypton-miner --node http://127.0.0.1:30334 --address-file address.txt.

Mining

From a terminal, the node answers plain web requests and JSON-RPC:

curl -s http://127.0.0.1:30334/v1/info      # the chain, as your node sees it
curl -s http://127.0.0.1:30334/v1/peers     # who it is connected to
curl -s http://127.0.0.1:30334/v1/block/21000
curl -s http://127.0.0.1:30334/rpc -H 'content-type: application/json' \
     -d '{"jsonrpc":"2.0","id":1,"method":"getblockcount","params":[]}'
Network configuration

Letting other nodes reach yours

A node works without this: it connects out to 8 others and that is enough to stay in sync. Accepting incoming connections is what makes it useful to nodes that are new or catching up.

Is it reachable already?

Ask the node for its peers, in the wallet's console (getpeerinfo) or with curl -s http://127.0.0.1:30334/v1/peers. If some of them show "inbound": true after an hour or so, other nodes are reaching you and there is nothing to do.

If not: the three doors

  1. The node itself

    kryptond listens unless it is started with --no-listen. The wallet's node listens only when Let other nodes connect to my full node is ticked.

  2. The computer's firewall

    Allow incoming TCP on port 30333. On Ubuntu with ufw: sudo ufw allow 30333/tcp. On Windows, allow kryptond.exe when Windows asks, or add an inbound rule for TCP 30333 in Windows Defender Firewall.

  3. The router

    At home your computer sits behind a router. Give the computer a fixed address on your home network (in the router's settings, often called a DHCP reservation), then add a port forwarding rule: TCP, port 30333, to that address. Routers differ; the manual of yours says where.

Forward 30333 only. Never forward port 30334: that is the node's API, meant for your own computer. To offer the API to others, put it behind a web server with limits; the project's own configuration is in deploy/caddy.

Configuration tuning

Options

kryptond has no configuration file: everything is an option on its command line. With the service, put options in /etc/krypton/kryptond.env as KRYPTON_EXTRA_ARGS="--max-inbound 16" and restart it.

OptionDefaultWhat it does
--networkmainnetmainnet, testnet or devnet (a private chain on your computer). Also KRYPTON_NETWORK.
--data-dir~/.genoryn-krypton/<network>
%APPDATA%\GenorynKrypton\<network>
Where the chain is stored. Put it on another disk if the first is small. Also KRYPTON_DATA_DIR.
--no-listenoffAccept no incoming connections: the node only connects out. The setting for a metered line.
--max-inbound64How many nodes may connect to yours. Lower it to send less.
--max-outbound8How many nodes yours connects to.
--listen0.0.0.0:30333The address and port other nodes connect to.
--rpc127.0.0.1:30334The address and port of the API. Leave it on 127.0.0.1 unless a web server stands in front of it.
--peernoneAnother node to connect to, as host:port. May be given several times.
--no-seedsoffDo not use the built-in seed nodes: connect only to the peers you name.

How much the node writes to its log is set by the environment variable RUST_LOG: RUST_LOG=debug kryptond for more, RUST_LOG=warn for less.

NetworkOther nodes (TCP)API (this computer)
Mainnet3033330334
Testnet3133331334
Devnet3233332334
Keeping it current

Updating

New versions fix problems and sometimes prepare a change of rules that takes effect at a block height announced in advance. A node that is never updated will one day stop following the network. Every release is listed, with what changed, under News.

Help

If something goes wrong

What you seeWhat it usually is
height stays at 0, peers is 0The node cannot reach anyone. Check the internet connection and that outgoing connections are not blocked. Name a peer: kryptond --peer seed.genoryn.io:30333.
An error that an address or port is already in useAnother kryptond is running: the wallet's own node, or the service. Run one.
kryptond: … GLIBC_2.39 not foundThe system is older than the packaged programs need. Build from source.
The disk is fullStop the node, move its folder to a larger disk and start it with --data-dir.
No incoming peersOne of the three doors is shut: see Network configuration. The node works without them.

Still stuck?

Say what you did, what you expected and what you saw. Never post your recovery phrase.