About Nanos

Published October 21, 2026 · Updated October 21, 2026 · Checked October 21, 2026

Nanos is a reference manual for Nano (XNO), the digital currency where every account keeps its own chain of blocks and transfers are settled by representative voting. It is written for people who want to understand the network before they use it: newcomers setting up a wallet, people who have received some XNO and want to be safe, node operators and developers.

Who the editors are

Nanos is run by an independent editorial team that signs its work as the Nanos editors. We write about Nano and nothing else, and we sign pages as a team so that the standard stays the same whoever picks up a page: each one is held to the same sourcing rules and the same checks. There is no single expert whose word you have to take, which is why every page lists its sources and shows the date it was read.

We run this site as readers of the protocol documentation, not as part of the Nano project. The project's site, nano.org, and its documentation at docs.nano.org are primary sources here, treated like any other source: quoted accurately, dated, and set aside when a page contradicts itself. Nanos is independently run. It carries no advertising, affiliate links or sponsorship, and no wallet, exchange or other service pays to appear.

What it covers

• How Nano works: The ideas behind Nano (XNO): one chain per account, open representative voting, why transfers carry no fee, and how units like raw relate to one Nano.
• Wallets and keys: How a Nano seed becomes private keys and addresses, how the address format protects against typos, which wallets exist, and how to back one up.
• Sending and receiving: What happens when you send or receive Nano: send and receive blocks, receivable funds, zero fees, the small proof of work, and why a transfer can look stuck.
• Running a node: How to run your own Nano node: requirements, Docker setup, configuration, voting weight and principal representatives, ledger size and pruning, and monitoring.
• For developers: Developer notes for Nano: the node RPC protocol, WebSocket notifications, work generation, state blocks, key derivation, address validation and integration basics.

What it leaves out

We explain how things work. We do not give prices, forecasts or advice about buying, selling or investing, and we do not promote any token, exchange or service. We cannot recover funds, reverse a transfer or give support for a wallet. We do not test or rank wallets: the wallets page lists what nano.org links to, with the date we read it.

How a page is made

• Research. The editors choose the question a reader brings, then read what the top search results and the primary documents say about it.
• Sources saved. The primary pages are saved and every figure, limit and rule in a draft is tied to a passage in a saved page. A fact with no passage is dropped.
• Scripted checks. Before publication, scripts confirm that each quoted passage really appears in the saved source, that every number in the text is in a quoted passage, that the same fact reads the same on every page, and that the page answers the questions the top results answer.
• Read-through. The page is read for contradictions, jargon and anything the source does not support, and sent back when it fails.
• Dated. Each page shows when it was published, updated and checked, and each source shows the day it was read.

How often pages are updated

Node releases change limits and defaults, so any page that quotes a version-dependent figure is re-read against its sources on each major node release, and every page is re-read at least once every 90 days. A page that changes gets a new updated date; a factual error is logged on the corrections page with the date and the fix.

Reach us

Write to editors@nanos.cc with the page address and, if you can, the passage in the documentation that shows the right fact. We read every message and aim to answer within a week. Never send a seed or a private key. More on the contact page.