How to Run a Private Silent Payments Server on Start9 with Frigate & Sparrow
Silent payments (BIP 352) are one of the most powerful privacy upgrades ever designed for Bitcoin. They allow you to share a single, static public receiving address while cryptographically deriving a unique, un-linkable Taproot address on-chain for every incoming transaction. But relying on third-party public indexing servers partially defeats that privacy. In this step-by-step tutorial, learn how to run your own private Frigate Electrum Server on Start9 (StartOS) and connect it seamlessly to Sparrow Wallet.
Why Silent Payments Need Your Own Node
With standard Bitcoin addresses, address reuse links all your payments together on public block explorers. Silent payments eliminate address reuse completely by having the sender tweak the recipient's public key using ECDH (Elliptic Curve Diffie-Hellman) shared secrets. However, scanning the blockchain for those tweaked outputs requires computational indexing. By self-hosting the Frigate indexer on your Start9 server, your wallet never leaks IP addresses, xpubs, or transaction query metadata to external public servers.
What is Frigate?
Frigate is an open-source, high-performance Electrum indexing server with native support for BIP 352 Silent Payments. It connects directly to your local Bitcoin Core node and your existing Electrum backend (such as Fulcrum or Electrs) on StartOS.
Beyond Silent Payments, Frigate also serves as a blazing-fast Electrum server for standard Native SegWit (BIP 84), Taproot (BIP 86), and legacy multisig wallets in Sparrow, Cake Wallet, or Nunchuk.
Prerequisites
Before starting the setup, ensure you have the following hardware and software ready:
1. A Start9 Server (StartOS)
A dedicated Start9 Server (Server One, Server Pro, or DIY mini-PC) running StartOS.
2. Bitcoin Core & Fulcrum / Electrs
A fully synced Bitcoin Core node and an underlying Electrum backend (Fulcrum is recommended for speed, or Electrs) already installed and running on your Start9 dashboard.
3. Sparrow Desktop Wallet
The latest release of Sparrow Wallet installed on your local computer.
Step-by-Step Installation & Configuration Guide
Step 1: Install Frigate from the Start9 Community Registry
Frigate is maintained in the Start9 Community Registry:
- Log in to your Start9 dashboard and click on Marketplace in the left sidebar.
- By default, you are on the official Start9 Registry. Click the registry selector button in the top-left corner and choose Community Registry.
- Click OK to confirm switching to community packages.
- In the search bar, type
frigate(orfrig). - Select Frigate and click Install.
Step 2: Configure Dependencies and Start the Service
Once downloaded, open the Frigate service page on your dashboard:
- You will see a notification stating "Task Required: Configuration". Click the configuration/play button.
- Under Electrum Server Dependency, choose your active indexing engine: select either Fulcrum or Electrs from the dropdown.
- Click Submit, then click Start to launch the service.
Step 3: Configure Tor and Local Connection Interfaces
Once Frigate is fully synced, navigate to the Interfaces tab on the Frigate service page:
- For Remote Tor Access (Recommended): Click on Electrum SSL API, select Add Onion Service, choose Create new address, and submit. Copy the resulting
.onionaddress. The default port is50001(or50002depending on SSL configuration). - For Local LAN Access: You can also connect via your local mDNS address (e.g.,
yournode.local:50001) or your Start9 server's local IP address while on your home network.
Step 4: Connect Sparrow Wallet to Your Private Server
Bring your copied connection address into Sparrow Wallet:
- Open Sparrow Wallet and navigate to File → Settings (or press
Ctrl+,/Cmd+,). - In the settings modal, select the blue Server tab.
- Under Server Type, choose Private Electrum.
- In the URL field, paste your Start9 Frigate
.onionaddress (or local IP/mDNS). - Ensure the Port is set to
50001(or matching your interface port). - Click Test Connection.
- A green checkmark and server banner will appear confirming successful connection. Close the settings modal.
- Look at the bottom-right corner of Sparrow: the connection indicator will pulse blue and turn solid, signaling a live, private connection to your personal node.
Testing Silent Payments in Sparrow
With Sparrow connected directly to your private Frigate server, open a wallet configured with Silent Payments (BIP 352):
1. The Static Receive Address
Go to the Receive tab. You will see a single static Silent Payment address (starting with sp1...) and its accompanying QR code. You can freely share this static address on your social media, invoices, or personal website. Every payer will send funds to completely distinct Taproot addresses on-chain, preventing chain analysis companies from linking your incoming payments together.
2. Clean Address Indexing
In the Addresses tab, you will observe unique derived receive addresses generated on demand. Change outputs are handled cleanly without exposing your wallet balance to outside observers.
3. Universal Compatibility with Native SegWit
You do not need multiple servers for different wallets. Open any standard Native SegWit (BIP 84) or Taproot wallet in Sparrow: Frigate serves transaction histories and balance updates instantly across all standard address types.
Want One-on-One Help Setting Up Your Node or Privacy Tools?
Running your own sovereign Bitcoin infrastructure is the ultimate path to financial self-sovereignty. If you want hands-on assistance setting up Start9, configuring Electrum backends, or mastering Sparrow Wallet, book a private 1:1 coaching session today.
Book a 1:1 Coaching SessionWatch the Step-by-Step Tutorial on YouTube
Follow along live on screen with Forrest HODL as he installs Frigate on Start9, sets up the Tor onion service, connects Sparrow Wallet, and tests both Silent Payment and SegWit wallets.