Important Note

A Nano node stores the entire ledger of transactions. While the Nano team is experimenting with pruning (removing historical data to reduce disk space), the primary way to manage storage for a Nano node is by ensuring you have enough space available on your SSD-based hard drive.

Current Storage Requirements

• Principal Representative Nodes (more than 0.1% of online voting weight): Require 400GB+ of free space on an SSD.

• Non-voting and Regular Representative Nodes: Also require 400GB+ of free space on an SSD.

Pruning (Experimental)

Ledger pruning allows for the removal of blocks that are not account frontiers (the latest state of an account). The goal is to reduce the ledger size, but the pruning feature is currently experimental and not for production use. Pruning requires a full ledger to be bootstrapped initially. Pruned nodes can still serve as bootstrap servers for remaining blocks. Note that pruning is not available for voting nodes.

Configuration

Nano node configuration is typically managed through TOML configuration files. Specific settings for disk space limits or pruning, if available, would be found within these configuration files.

For details on specific pruning parameters (like min-retain-blocks), you would consult the relevant documentation or configuration files (e.g., app.toml in some cases).

In summary, to manage hard drive limits for a Nano node, you primarily focus on providing sufficient SSD storage based on the recommended requirements. The experimental pruning feature is an ongoing development to reduce storage needs, but currently, it is not recommended for production nodes.

🪙 Installing and Configuring Nano Node (V28.1) in Docker

This document details the complete process of installing, configuring, and activating a Nano node as a representative, including importing an external wallet with seed.

✅ General information

• Node version: V28.1
• Container: Docker (docker compose)
• Basic system: Ubuntu 24.04 (Noble)
• P2P port open: 7075 TCP/UDP
• Representative account: nano_ie9a...
• Wallet ID: 5D59...
• Seed: B9D32...
• Mnemonic (example with 24 words): crash rabbit disease then daring nice park salad lamp bridge point human found tortoise paper nerve simple enjoy device add decorate trouble sister vast

🐳 Installing Docker and Docker Compose

sudo apt update
sudo apt install -and ca-certificates curl gnupg lsb-release


# Clave GPG
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | \
 sudo gpg --dearmor -the /etc/apt/keyrings/docker.gpg


# Repository for Ubuntu 24.04 (noble)
echo \
 "deb [arch=$(dpkg --print-architecture) \
 signed-by=/etc/apt/keyrings/docker.gpg] \
 https://download.docker.com/linux/ubuntu \
 noble stable" | \
 sudo tee /etc/apt/sources.list.d/docker.list > /dev/null


# Final installation
sudo apt update
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

📦 Nano Container Configuration

mkdir -p ~/nano-node-docker
cd ~/nano-node-docker

docker-compose.yml

services:
  nano_node:
    image: nanocurrency/nano:V28.1
    container_name: nano_node
    restart: unless-stopped
    ports:
      - "7075:7075/tcp"
      - "7075:7075/udp"
    volumes:
      - ./data:/root/Nano

sudo docker compose up -d

🔐 Wallet and account import

1. Access the container

sudo docker exec -it nano_node bash

2. Create wallet

nano_node --wallet_create
# Result:
# 4D...

3. Import seed

nano_node --wallet_change_seed \
 --wallet=4D... \
 --seed=P6AD...

4. Create a derivative account (from the seed)

nano_node --account_create \
 --wallet=4D...


# Result:
# nano_7...

🗳️ Set up an account as a Representative

nano_node --wallet_representative_set \
 --wallet=4D... \
 --account=nano_7...

nano_node --account_representative_set \
 --account=nano_7... \
 --representative=nano_7...

💾 Manual backup of the wallets.ldb file

cp ~/nano-node-docker/data/Nano/wallets.ldb ~/wallets-backup.ldb

🧪 Node Verification

sudo docker logs -f nano_node
sudo docker exec -it nano_node bash
nano_node --diagnostics

📌 Notes

-The imported wallet is fully functional within the node. -The account is already registered as a representative. -The filewallets.ldbcontains all the keys derived from the seed.

Appendix: Manual verification of the Nano node

✅ 1. Verify that the container is running

sudo docker ps

It should display a line like:

nanocurrency/nano:V28.1   ...   Up XX minutes ...   nano_node

✅ 2. View logs in real time

sudo docker logs -f nano_node

You should see:

[monitor] [info] Blocks confirmed: ...
[monitor] [info] Peers: ...

✅ 3. Check connectivity and diagnostics

sudo docker exec -it nano_node bash
nano_node --diagnostics

✅ 4. View number of blocks

nano_node --debug_block_count

✅ 5. View list of connected peers

nano_node --debug_peers

Expected output:

[::ffff:178.33.122.56]:7075
[::ffff:51.81.243.15]:7075

🧭 Manual Verification of the Nano Node

Last updated: 2025-06-05 03:37:44

Manually verify that the node is up, without scripts or external monitoring.

📝 Recommendation

Perform this review at least once a day if you don’t have automatic supervision.

These checks ensure that the node is: -✅ Synchronized -✅ Connected -✅ Operational -✅ Active on the Nano network

⚠️ Disclaimer

This guide was created to document practical commands to interact with a self-hosted Nano node via its JSON-RPC API. While its content has been carefully verified, its behavior is not guaranteed in all environments or custom configurations.

Use these commands at your own risk. Always make backups before changing sensitive settings or handling private keys.

For issues or help, refer to the official Nano documentation or the community forums.