Run a Nito seed server
A seed server helps new Nito nodes find the network. Set one up on your own server with one command, in a few minutes.
curl -sSL https://seedsetup.nito.tools | sudo bashPowered by DigiNode Seeder, which can also run seed servers for DigiByte and Litecoin.
What is a seed server?
When a Nito node starts for the first time, it doesn't know any other nodes. It finds them by asking the DNS seed servers written into Nito Core: small servers, run by volunteers, that check the network all the time and hand out the addresses of nodes that are up and on the right chain.
Every extra seed server, run by a different person in a different place, makes the network harder to cut off or mislead. Running one is a simple, low-cost way to help Nito.
How it works
- A new Nito node asks a seed server from the list built into Nito Core, such as
seed.nito.tools. - The seed server answers like a DNS server, with the addresses of reliable Nito nodes.
- The new node connects to those nodes, and learns about more nodes from them.
- It starts downloading the blockchain from the nodes it has connected to.
Behind the scenes, the seed server:
- Crawls the Nito network all the time, revisiting known nodes to check they're still there.
- Only hands out nodes that are reachable, up to date and running Nito Core v4, the only version accepted after Nito's v4 hard fork.
- Answers the filtered questions Nito Core asks (such as
x1000009.seed.yourdomain.com, for nodes with private transaction support). - Needs very little: a few tens of megabytes of memory and hardly any CPU.
Powered by DigiNode Seeder
The setup command uses DigiNode Seeder, a free tool from DigiNode Tools. Log in to your server, run one command, answer a few questions, and it does the rest:
- Builds the seeder from source, and runs it as a locked-down service that starts at boot and restarts if it stops.
- Suggests all the names from your domain, and answers only for them, so your server can't be misused as an open DNS server.
- Shows you the DNS records to add, ticks off the ones already in place, then checks them and says what's wrong, if anything.
- Installs security updates by itself, can turn on a firewall that only lets in SSH and DNS, and offers to turn off SSH password logins once you log in with a key.
- Gives you one command,
diginode-seeder, to check on it, update it and get it into Nito Core.
More than Nito. DigiNode Seeder runs seed servers for several blockchains, including DigiByte and Litecoin. They can all share one server and one IP address: once your Nito seed server is running, add another blockchain with, for example, diginode-seeder --add digibyte.
The script is open source, and you can read it before you run it: DigiNode-Tools/diginode-seeder-setup on GitHub.
What you need
A server
A small VPS (virtual private server) with its own public IP address and a reliable connection. A seed server needs very little, so the cheapest plan most providers offer is enough: 0.5 GB of memory is fine. Fasthosts, Hetzner, DigitalOcean and Linode are some options, from about £1–2 a month.
It needs Debian 12 or 13, or Ubuntu 22.04 or 24.04, with nothing else using port 53. Your provider's firewall must let UDP port 53 in.
A domain name you control
A domain where you can add DNS records, including NS records for a subdomain. Your seed will have a name like seed.yourdomain.com.
Some DNS providers don't let you add NS records for a subdomain, so check first. Cloudflare and most registrars do.
Running a seed server responsibly
It's a small job, but a lasting one. Once your seed is in Nito Core, every node running that version can ask it for addresses, for as long as that version is in use: often years. Before you begin, please be sure you can:
- Keep it running 24/7
- New nodes can start at any hour, anywhere in the world. A seed that doesn't answer slows them down. DigiNode Seeder does most of the work, but it needs a server that stays on.
- Stay reachable
- Your seed is added to Nito Core with a pull request from your GitHub account, so the developers can contact you if there's ever a problem with it.
- Keep it for the long term
- Plan to run it for a long time. If you ever need to stop, there's a simple way to do it properly (see When you want to stop).
- Run one
- One seed server per person, so there are many independent operators and no single point of failure.
1 Run the setup on your server
Log in to your server with SSH (for example ssh [email protected], with your server's address) and run:
curl -sSL https://seedsetup.nito.tools | sudo bashIt checks the server, then asks a few questions. Press Enter to accept a suggestion in [brackets]:
- Domain
- The domain for your seed, such as
yourdomain.com. All the names are suggested from it. - Names
- It suggests the seed name nodes will look up,
seed.yourdomain.com, and a name for the server itself,seedserver.yourdomain.com, which the seed name is handed to. Press Enter to use them, or change them. If you later add seeders for another blockchain in the same domain, they get names of their own, such asdgbseed.yourdomain.com. - Contact email
- Shown in your seed's DNS records (the SOA record), so people can reach you.
- Login message
- Shows the
diginode-seedercommand each time you log in, so there's nothing to remember. - Security updates
- Installs them by itself, and can restart at 03:30 (server time) when an update needs it. The seed server starts again on its own.
- Firewall
- Turns on a firewall that only lets in SSH and DNS. It uses your server's own SSH port, so you can't be locked out.
- Hostname
- If the server still has its provider's default name (such as
localhost), it offers to rename itdiginode-seeder, so you can see where you're logged in.
It shows a summary before it starts. Then it installs what it needs, builds the seeder and starts it, showing its progress. A few minutes later, once the seed server is finding nodes, it shows the DNS records to add.
2 Add the DNS records
At the DNS provider for your domain, add the records the setup shows you. With the example names, they look like this:
| Name | Type | Value |
|---|---|---|
seedserver.yourdomain.com | A | Your server's IPv4 address, e.g. 203.0.113.10 |
seedserver.yourdomain.com | AAAA | Its IPv6 address, if it has one, e.g. 2001:db8::10 |
seed.yourdomain.com | NS | seedserver.yourdomain.com |
The A (and AAAA) record says where your server is. The NS record hands your seed name over to your server, so it answers for it.
seedserver records to DNS only (grey cloud), not proxied. And make sure the seed name has no other records (A, CNAME…), or the NS record won't work.The setup ticks off the records already in place, and waits while you add the rest. Press Enter and it checks them, and tells you in plain words what's wrong, if anything. DNS changes can take a few minutes to spread: you can also stop and check later with diginode-seeder --dns.
Prefer to set it up manually?
DigiNode Seeder is the quickest way, and it does things a guide can't, like checking your DNS records and keeping the server updated. If you'd rather not run a script, you can read it first (it's one file), or set a seed server up yourself. In short:
Build
On Debian or Ubuntu, build DigiNode DNS Seeder, the seeder program DigiNode Seeder uses:
sudo apt-get install -y build-essential libssl-dev libboost-dev git dnsutils
git clone https://github.com/DigiNode-Tools/diginode-dns-seeder
cd diginode-dns-seeder && make
Run
It answers DNS on port 53, so run it as root, or with CAP_NET_BIND_SERVICE (see the service file below). In the email address, the @ is replaced by a dot:
sudo ./dnsseed --chain nito -h seed.yourdomain.com -n seedserver.yourdomain.com -m you.yourdomain.com -a 203.0.113.10 -p 53
All its options: ./dnsseed --help.
DNS records and firewall
The same records as above. Allow UDP port 53 in, in the server's firewall and your provider's. Then check with dig +short seed.yourdomain.com.
Keep it running
Run it as a systemd service, so it starts at boot and restarts if it stops, and turn on automatic security updates (unattended-upgrades). For example, save this as /etc/systemd/system/nito-seeder.service:
[Unit]
Description=Nito DNS seed server
After=network-online.target
Wants=network-online.target
[Service]
User=nitoseeder
ExecStart=/usr/local/bin/diginode-dns-seeder --chain nito -h seed.yourdomain.com -n seedserver.yourdomain.com -m you.yourdomain.com -a 203.0.113.10 -p 53
StateDirectory=nitoseeder
WorkingDirectory=/var/lib/nitoseeder
AmbientCapabilities=CAP_NET_BIND_SERVICE
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
NoNewPrivileges=yes
ProtectSystem=strict
ProtectHome=yes
PrivateTmp=yes
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target
Install the program as /usr/local/bin/diginode-dns-seeder, create the user (sudo useradd --system --no-create-home --shell /usr/sbin/nologin nitoseeder), then run sudo systemctl enable --now nito-seeder.
To run seed servers for several blockchains on one IP address, put dnsdist on port 53 and run each seeder on its own local port. The DigiNode Seeder guide shows how.
3 Add your seed to Nito Core
Nodes only ask the seed servers written into Nito Core, so your seed only starts helping once it's listed there. You ask for that with a pull request that adds one line to src/kernel/chainparams.cpp in NitoNetwork/Nito-core. Once it's merged, it goes out with the next release, and nodes start using your seed as they update.
Before you ask
- Make sure your seed works from the internet. Run
diginode-seederon your server: it checks it, and shows whether it's in Nito Core yet and, if not, the exact line to add. Once it works, you can ask straight away. - Only ask if you'll keep the server running: the developers want seeds that stay up.
- You need a GitHub account (free, at github.com/signup).
The easy way: let your AI assistant do it
If you're not familiar with Git and GitHub, this is the simplest way. Use the desktop app of the AI assistant you prefer (such as Claude or ChatGPT) on your own computer: it can make the pull request in your web browser or on the command line. It checks your seed first, prepares everything, and shows it to you before anything is published. On your server, run:
diginode-seeder --ai-promptIt prints a prompt with your details filled in. Copy it and paste it into your AI assistant.
Or yourself, on GitHub's website
- Sign in to GitHub, and open src/kernel/chainparams.cpp in Nito Core.
- Click the pencil (Edit this file). GitHub makes your own copy (a fork) of Nito Core.
- In the mainnet section (
CMainParams), find the lines forseed.nito.network.andseed.nitopool.online., and add yours after them, in the same format, with a dot after the name:
Change nothing else.vSeeds.emplace_back("seed.yourdomain.com."); - Click Commit changes… and write a message like
Add seed.yourdomain.com DNS seed. Choose Create a new branch for this commit and start a pull request, then Propose changes. - Check the pull request goes into NitoNetwork/Nito-core, and add a short description, for example: Adds seed.yourdomain.com as a mainnet DNS seed. It runs on its own server (set up with DigiNode Seeder) and answers plain and x1000009. queries. I'll keep it running, and I'm happy to be contacted if it ever has a problem.
- Click Create pull request, and reply to any comments from the developers.
Or from the terminal
For anyone comfortable with git. You need the GitHub CLI (gh), signed in with gh auth login.
gh repo fork NitoNetwork/Nito-core --clone
cd Nito-core
git switch -c add-seed
nano src/kernel/chainparams.cpp # add your line after seed.nitopool.online.
git diff # check only your line changed
git commit -am "Add seed.yourdomain.com DNS seed"
git push -u origin add-seed
gh pr create --repo NitoNetwork/Nito-core --title "Add seed.yourdomain.com DNS seed"
Once it's merged, keep your seed server running. It installs security updates by itself, and diginode-seeder --update updates DigiNode Seeder and the seeder.
4 Look after it
- Set up alerts
- Use a monitoring service to tell you if your seed server stops working. A free one such as UptimeRobot or HetrixTools can email you if your server stops answering: add a port check on
seedserver.yourdomain.com, port 53 (allow TCP port 53 in your provider's firewall too). - Check on it
- Log in now and then, at least once a month. The login message tells you if the seed server has stopped, or if the server is waiting to restart after an update.
Everything the diginode-seeder command can do:
diginode-seeder | How it's doing, and whether your seed is in Nito Core yet (with the line to add, if not). |
--dns | Check your DNS records, and explain anything that's wrong. |
--ai-prompt | A ready-made prompt for your AI assistant to add your seed to Nito Core. |
--update | Update DigiNode Seeder and the seeder. It keeps your settings and only restarts what changed. |
--add digibyte | Add seed servers for another blockchain on the same server (also --add litecoin). Your Nito seed server keeps running. |
--remove <chain> | Stop and remove one blockchain's seed servers. |
--reconfigure | Change the names, the email or other settings. |
--ssh-passwords off | Turn off SSH password logins, so only SSH keys work. Only offered once you've logged in with a key, so you can't lock yourself out. |
--firewall on|off | Turn the firewall (only SSH and DNS let in) on or off. |
--uninstall | Stop and remove the seed servers. Remember to remove your DNS records too, and your seed from Nito Core if it's listed. |
--help | All the options. |
When you want to stop
Nodes keep asking your seed for as long as it's in their copy of Nito Core, so please don't just switch it off:
- Tell Nito Core. Open a pull request removing your seed's line (your AI assistant can do this too), or an issue at NitoNetwork/Nito-core, so the developers know.
- Keep it running a little longer. If you can, keep it running until a release without your seed is out, so nodes have time to move on.
- Remove it. Run
diginode-seeder --uninstallon the server, then delete the DNS records for your seed name andseedserver.yourdomain.com.
Need help?
For questions about Nito, ask in the Nito Telegram group. If DigiNode Seeder isn't working as it should, open an issue on GitHub. More about DigiNode Seeder, including seed servers for DigiByte: diginode.tools/diginode-seeder.