Bitcoin Node

Start9 Server One: first-person setup walkthrough.

READ7 min · UPDATED2026-05-08

Reviewed against primary sources cited at the bottom of this page.

From boot to a synced Bitcoin node serving a Sparrow wallet over Tor onion. ISO selection, certificate trust, initial block download timing, and the cert-pinning trick to make Sparrow connect cleanly. The Start9 Server One is the lowest-friction path from "I want to verify my own transactions" to "I'm running a node."

This page is a first-person walkthrough. The hardware was purchased at retail. No affiliate relationships with Start9, hardware resellers, or any wallet provider.

THE SHORT VERSION

Plug the Server One into power and ethernet. Open a browser and visit the local URL. Trust the root certificate Start9 provides. The device installs Bitcoin Core automatically and begins initial block download. IBD takes 2 to 5 days depending on internet and disk speed. Once synced, connect Sparrow Wallet over Tor using the onion address from the Start9 web UI. From that point you are running a full Bitcoin node and verifying your own transactions without trusting any third party.

What the Server One is and why use it

Start9's Server One is a small Linux server pre-loaded with StartOS, an opinionated distribution that runs Bitcoin Core, Lightning, Sparrow Wallet, and other self-hosted services with one-click install. The alternative to a Server One is buying parts and configuring everything yourself; the alternative to running a node at all is trusting Coinbase, Mempool.space, or an SPV wallet to verify your transactions for you. Server One sits at the "lowest-friction full-validation" point on the spectrum.

Specs (verified at retail purchase, May 2026): 8 GB RAM, 1 TB or 2 TB NVMe storage option, gigabit ethernet, modest CPU. Sufficient for a Bitcoin full node plus several services running in parallel. Power draw is approximately 8 to 12 watts at idle, peaking around 25 during IBD.

Step 1: Initial boot and OS selection

Unbox the Server One. Connect ethernet to your router and the power adapter. The device boots into StartOS automatically.

From any device on your local network, open a browser to the URL printed in the Start9 quick-start guide (something like https://start.local or the IP address of the device on your LAN). The first connection triggers a self-signed certificate warning. This is expected and is the whole point of the Server One: you are explicitly trusting your own device rather than a third-party certificate authority.

Set a password, claim the device, and create a recovery phrase. StartOS generates this for you; write it down on paper and keep it with your other wallet seeds (it is the equivalent for the box itself, not for the wallet).

Step 2: Trust the root certificate

StartOS provides its own root CA. Downloading and installing this on each device you use saves you from clicking through the self-signed-cert warning every time. The setup wizard provides the download. On macOS/iOS the cert installs to the system keychain; on Windows it goes into the Trusted Root Certification Authorities store; on iOS you have to enable it in Settings → General → About → Certificate Trust Settings verify×DON'T TRUST, VERIFYClaim: StartOS uses a self-signed root certificate authority that requires explicit trust installation on each client device.Verify at: Start9 documentation ↗The self-signed root CA is intentional. Confirm installation steps against current Start9 docs as procedures change between StartOS versions..

Once trusted, the Server One's web UI loads without warnings on every device that has the cert installed. This is the same model as Tailscale or any other self-hosted system that uses an internal CA.

Step 3: Install Bitcoin Core

From the StartOS dashboard, go to Marketplace and find Bitcoin Core. One click installs it. Default configuration is sensible: full validation, mempool enabled, pruning off (you have the disk space). The install takes a few minutes; the bigger time investment is the next step.

Once Bitcoin Core is installed and running, StartOS exposes it on both clearnet (for LAN connections) and a Tor onion address (for remote connections). Both work; Tor onion is the privacy-preserving option for connecting wallets from outside your home network.

Step 4: Initial block download (IBD)

Bitcoin Core needs to download and verify every block since the genesis block (~600 GB as of May 2026). This is the slowest part of getting set up.

IBD TIMING ESTIMATES

Gigabit ethernet, NVMe SSD: 2 to 3 days
100 Mbps internet, NVMe SSD: 3 to 5 days
Gigabit ethernet, SATA SSD: 4 to 6 days (the slower disk is the bottleneck, not the network)
HDD: avoid. IBD on an HDD takes weeks and degrades the drive.

During IBD, leave the device powered on and connected. Power outages or unclean shutdowns will resume from where they left off, just slower. You can use the rest of StartOS during IBD; only Bitcoin Core itself is unavailable for normal queries.

Step 5: Sparrow connection via Tor onion

After IBD completes, the Server One can serve wallets. Install Sparrow Wallet on your daily-use computer (this part is not on the Server One; Sparrow runs on your laptop/desktop).

In Sparrow: File → Preferences → Server. Choose Bitcoin Core. Configure:

URL: the .onion address from the Bitcoin Core service page in StartOS
Port: 8332 (default mainnet RPC)
User and password: from the Bitcoin Core "Credentials" tab in StartOS
Use Tor: yes (Sparrow includes embedded Tor; just toggle it on)

Click Test Connection. Sparrow connects, fetches your block height, and confirms it matches your node's. From this point forward every Bitcoin address Sparrow shows, every UTXO it tracks, and every transaction it broadcasts goes through your own node. You are not trusting any third-party server for any part of the wallet's operation.

Other services worth installing

Mempool.space: a self-hosted version of mempool.space using your own node's data. Great for fee estimation without trusting the public site.
BTC RPC Explorer: a lightweight block explorer that runs locally. Useful for verifying transactions without leaking them to public APIs.
Electrs: an Electrum server backed by your node. Lets you connect any Electrum-protocol wallet (BlueWallet, Electrum, Sparrow) without using a public Electrum server.
LND or Core Lightning: if you want a Lightning node. Different tradeoffs; both run cleanly on the Server One.
JoinMarket or Whirlpool (where available): for coinjoin if privacy is a priority. See coinjoin landscape.

Each is a single click to install. The Marketplace handles updates and security patches. You are running a small fleet of Bitcoin-adjacent services without ever opening a terminal.

When the Server One makes sense

You hold meaningful Bitcoin in self-custody. Verifying your own transactions is a non-trivial security upgrade above SPV wallets that rely on third-party servers.
You value privacy. Trusting Mempool.space or Blockstream's Esplora to look up your addresses leaks information. Your own node never tells anyone what addresses you watch.
You will not run a node from a command line. StartOS removes that requirement.
You want to support the network. Each node is a peer that helps propagate transactions and blocks. The marginal contribution is small but real, and especially valuable in geographies with low node density.

If you hold under approximately 0.01 BTC and don't care about transaction privacy, the marginal value of a Server One over a normal SPV wallet is questionable. The hardware is approximately $400 to $700; the time investment is modest but not zero.

Common questions

Can I run this on a Raspberry Pi instead?

StartOS supports Raspberry Pi 4 and 5. A Pi setup is cheaper ($150 of parts vs $400+ for Server One) but slower IBD and slightly more fragile (microSD wear is real). Server One is the "official hardware" experience; the Pi route works for technically-comfortable users.

Do I need to forward ports on my router?

For wallet-server use cases (Sparrow connecting to your node), no. Tor onion addresses work through your router without port forwarding because the connection is initiated outbound. Port forwarding is only required if you want to serve other peers from the public internet, which is optional and adds bandwidth load.

What happens if the device dies?

If hardware fails, your Bitcoin is fine. Your seed phrase (kept separately) is what holds your keys. Restoring the node means buying new hardware, installing StartOS, and waiting through another IBD. Your wallet (held in Sparrow on your laptop, not on the node) keeps working with any other server in the meantime.

How much electricity does it use?

Approximately 8 to 12 watts at idle (most of the time, post-IBD). Over a year: roughly 90 kWh. At average US rates: approximately $14/year. Equivalent to a small LED bulb running constantly.

Is this overkill for someone holding 0.1 BTC?

Subjective. At 0.1 BTC ($7,700 at $77K), running a node is more about learning and sovereignty than about cost-justifying the hardware. At 1 BTC and above, the privacy and verification value scales meaningfully. The right framework is in custody levels.

Running a Bitcoin node · the broader explainer
Sparrow Wallet guide
Multisig · the natural extension of self-sovereignty
Custody levels · when this level of node matters
Bitaxe Gamma Duo review · the miner companion

Sources

Start9 documentation · docs.start9.com
Bitcoin Core, official release notes and documentation · bitcoincore.org
Sparrow Wallet, official documentation · sparrowwallet.com
Tor Project, hidden services documentation · torproject.org
First-person measurements and configuration notes from a four-month operational period (Feb to May 2026)

Last updated 2026-05-08. Not financial advice. Do your own research.

Subscribe via RSS for new articles.