SOV NETWORK
← Back to home

SOV Network — Knowledge Bank

Civic education for the SOV Network: what it is, how to use it, and the protocols that make it work. This is the same Knowledge Bank shown inside the SOV app's Academy — published here so anyone can read it without installing anything.

Contents

What SOV is and why it exists

The world needed something new

Bitcoin proved that money does not need a bank. But Bitcoin never solved identity, communication, or justice. The SOV Network was built to go further — a single network where you own your identity, your money, your messages, and your voice in how the rules are written. Not controlled by any company. Not dependent on any government. Built to outlast them both.

Not a blockchain — a Sovereign Mesh

SOV is NOT a blockchain. There are no blocks, no chain of blocks, no mining race, and no global queue every payment must wait in. SOV is a SOVEREIGN MESH: self-contained nodes that gossip peer-to-peer, each holding the shared ledger, confirming transactions by witnessing them rather than by burning energy. It is called a "mesh" because the nodes form a web with no centre — any node can leave or join and the network carries on; and "sovereign" because YOU — not a company, not a chain — own your identity, your money, and your voice. Its one genuinely new idea is PROOF OF PERSONHOOD: one human, one wallet, proven by your own biometrics on your own device. That is what no blockchain has — the network knows you are a real, unique person without knowing who you are. So when you describe SOV, don't reach for "crypto" or "blockchain". Say what it actually is: a sovereign, proof-of-personhood mesh — self-contained nodes, one human one wallet, no central operator, and no app store.

Your identity is your key — nothing else

Every other network asks you to trust a company with your password, your phone number, or your email. SOV asks for none of those. Your palm is your key. It cannot be stolen, guessed, or reset by a corporation. When you enroll, your biometric is processed on your device and never sent to any server. Your Sovereign ID is yours permanently — no account to be banned, no service to be shut down.

Everything Bitcoin is — and everything it is not

Bitcoin is digital gold — scarce, decentralized, and unstoppable. SOV respects that design. But Bitcoin has no identity layer, no messaging, no governance, no justice system, and no built-in community. It cannot tell who is human and who is a bot. SOV solves all of that. One human, one wallet. The network knows you are real — and that changes everything.

The last network that can be built this way

Governments are moving fast to regulate digital identity and digital money. The window to build a truly free, sovereign network is closing. SOV was designed from the ground up to operate behind firewalls, survive hostile infrastructure, and resist seizure — because citizens in many countries cannot afford to wait for permission. Every citizen who joins today makes it harder to stop tomorrow.

Works behind firewalls and in blackouts

SOV Speak routes messages through relay nodes that operate on standard ports. Even in countries that block popular apps, SOV messages get through. When a recipient is offline, the message stays in the sender’s outbox on their own device — the relay stores nothing. The moment the recipient reconnects, the network broadcasts their presence and the sender’s device automatically delivers. No message content ever touches a relay. No conversation can be intercepted.

How SOV works

SOV is a peer-validated digital currency secured by biometric identity. Every citizen gets a wallet, a Sovereign ID, and a permanent place on the shared ledger. No bank account required. No minimum balance. No credit check. If you are human and you have a phone, you qualify.

Justice without courts

On the SOV Network, citizens have a real dispute process — no lawyers, no fees, no waiting months for a ruling. If a transaction is disputed, five citizens selected at random review the evidence and vote. The majority decides. Funds move according to the verdict within 72 hours. This is the first digital economy where justice is built into the protocol.

Your vote actually changes the rules

The Network Constitution is not a document written by a company and handed to you. It is a living set of protocols that citizens vote to activate. Every enrolled citizen votes equally — your balance does not change your weight. If 5,000 citizens vote to enable a new feature, it activates for the whole network. The citizens own the rules.

Run a node on macOS or Linux

The SOV desktop wallet is the same application on Windows, macOS and Linux, and on all three it is also a full node — the node is not a separate download. What differs between them is only how you get Tailscale, and Tailscale is needed ONLY if your connection cannot accept incoming traffic.

START HERE, on any of the three: install the wallet, sign in, open the Node tab, leave Reachability on Auto and switch Run a Node ON. On ordinary home broadband the app opens your router itself, or relays through the mesh if your network is awkward, and you configure nothing at all. When it shows "Reachable at: …" you are serving, and uptime is what earns. Most people never need anything below this paragraph.

IF AUTO CANNOT GET THROUGH — mobile hotspot, CGNAT, student or office Wi-Fi, any network where you cannot forward a port — you use Tailscale Funnel, which gives your node a stable public address over an outbound-only connection, for free. You install Tailscale yourself and sign in to YOUR OWN Tailscale account. The SOV network never provisions it for you and never sees your tailnet.

ON WINDOWS the wallet can install Tailscale for you: press Enable Tailscale Funnel and accept the normal Windows prompt, then sign in through your browser once.

ON macOS you install it yourself first — from tailscale.com/download, or with "brew install --cask tailscale" if you use Homebrew. Open Tailscale once and sign in. The wallet then finds it automatically, including the App Store version, whose command-line tool lives inside the application bundle rather than on your PATH.

ON LINUX install it with your package manager — "sudo apt install tailscale" on Debian or Ubuntu, "sudo dnf install tailscale" on Fedora, "sudo pacman -S tailscale" on Arch — then "sudo tailscale up" and sign in. Linux needs ONE extra command that Windows and macOS do not: "sudo tailscale set --operator=$USER". Without it the wallet cannot talk to the Tailscale service, because that service is owned by root. Run it once and you are done; the wallet will tell you if you forgot.

Then on any OS: set Reachability to Tailscale Funnel, switch Run a Node ON, and the first time only, approve the Funnel link in your browser. Citizens reach you on the standard secure port with no port-forwarding anywhere.

A note on Linux desktops: the wallet needs a few system libraries that some minimal installations leave out, and a keyring to store your keys in. The download page lists the exact packages. If the wallet will not start on a server or inside a container, that is expected — it is a desktop application, and a machine with no screen should run the node software directly instead.

Running the network

The SOV Network runs on relay nodes operated by certified Node Operators around the world. Relays keep the shared ledger in sync, deliver messages, and witness transactions. The more operators there are, the stronger, faster, and more resilient the network becomes. Any citizen with a server can become a relay operator. This is infrastructure owned by the people who use it.

Using SOV day to day

One human, one wallet

The SOV Network allows exactly one wallet per person, enforced by biometric identity. There are no bots, no fake accounts, and no whales who joined 100 times. Every citizen has equal weight in governance. Every new citizen gets the same fresh start. The network is designed for people — not corporations, not algorithms.

SOV Value and the ⟡ symbol

The ⟡ symbol represents the SOV reference rate — the citizen-voted guide price of 1 SOV. Once 5,000 citizens enroll, the network holds its first value vote. Citizens propose a price. The median of all proposals becomes the rate. It updates every 10,000 new enrollments. No exchange sets this number. No company owns it. Citizens decide the value of what they built.

A real economy — not a speculation game

SOV is not designed to be traded on exchanges and pumped by speculators. It is designed to be earned, spent, and saved by real citizens doing real things. Node Operators earn for running the infrastructure. Enrollment Helpers earn for bringing new citizens on. Justice jurors earn for resolving disputes fairly. The SOV economy rewards participation, not speculation.

SOV Speak — messaging with receipts

SOV Speak lets you send messages, voice notes, photos, and files to any citizen on the network. Every message shows a delivery status: Sending → Delivered → Read. You can send SOV directly inside a conversation — the payment appears as a receipt in the chat thread. No phone number required. No SIM card. Just your Sovereign ID.

Protecting your wallet

Your wallet is secured by your 12-word seed phrase, an optional 6-digit PIN, and guardian recovery. Write your seed phrase on paper and store it safely — it is the only way to restore your wallet if your phone is lost or stolen. No central authority can freeze your funds, reset your access, or demand your keys. This is what it means to truly own your money.

SOV Link lets any website or app accept your Sovereign ID as a login. It works in two phases. The FIRST time you visit a SOV-enabled site, you tap "Sign in with SOV", and the browser shows you a 6-digit pairing code. You open your SOV app, tap Settings → Connect to External Site, type the code, confirm the site name, and choose a password just for that site. Your SOV app signs the link on the device — your seed phrase never enters the browser, never reaches the external site, and never touches the network in readable form. EVERY TIME after that, the site shows a normal username + password form. You type your Sovereign ID (or palm name) and the password you created for that site. The site checks the password locally on its own server — the SOV network is not contacted at all on repeat logins. This means your day-to-day sign-ins are instant and work even when the SOV network is busy or offline. The password is bound to that specific site, so if one site is breached the credential cannot be reused anywhere else.

Many login systems use a QR code on the desktop that you scan with your phone. SOV Link deliberately does NOT do this. A photographed or screenshotted QR code is a fully valid login token — anyone who captures the picture could log in as you before you do. SOV Link uses a short 6-digit numeric pairing code instead. The code is one-use, expires in 90 seconds, and is bound to the specific website domain you are trying to sign in to. Even if someone watches you type it, it has already been consumed by the time they could try to use it, and it only works for one site anyway. This is a deliberate design choice — small operational friction (typing 6 digits) traded for a meaningful improvement in phishing resistance.

SOV Link's full protocol has a detailed end-to-end walkthrough showing what every actor does — the developer registering a platform, the citizen signing in for the first time, the citizen returning a week later. It covers the two-phase model (one-time linking + relay-free repeat login), why SOV Link uses a pairing code instead of a QR code, and what guarantees the protocol delivers versus what it does NOT do — written so a non-technical reader can follow it straight through.

If you actually write the code, the SOV Link developer guide walks you from "I have heard of SOV Link" to "my website accepts SOV Link logins" in about 30 minutes. It shows the exact PHP and Node.js code for the two server endpoints you build (the kickoff endpoint and the callback receiver), the database schema you need, the HTML and JavaScript for the login page, and a testing checklist. It assumes you know PHP or Node.js but assumes nothing about SOV. The textbook tells you WHAT happens during a SOV Link sign-in; the developer guide shows you THE CODE THAT MAKES IT HAPPEN — including the file that surprised everyone the first time through, the sov-callback.php that receives the relay's server-to-server POST.

For platform developers — integrate in 15 minutes

If you build websites or apps and want to power your platform with one-human-one-account, SOV Login is the easiest integration on the network. Register your platform once with any SOV relay node, add a "Sign in with SOV" button that shows the citizen a 6-digit pairing code (the citizen confirms it inside their SOV app's "Connect to External Site" screen — there is no browser-typed seed phrase, no externally-hosted login page), and accept the signed callback when the citizen returns. On the back end you store the citizen Sovereign ID with a UNIQUE constraint — the SOV biometric layer guarantees one ID per human, your database enforces one row per ID, and together they give you a sybil-proof user base without captchas, SMS verification, or KYC paperwork. A full step-by-step integration guide with PHP and Node.js example code is available.

Registering a new platform on the network

Before a website can offer “Sign in with SOV”, it has to be connected to the network — and there is no admin office, no corporate sign-up, and no key handed out by a company. It is done by an enrolled SOV citizen who approves the request with their own identity and pays a small one-time SOV fee (currently 10 SOV, set by citizen vote). That fee flows into the operator reward pool that pays the people running the network — the total SOV supply never changes. The network keeps no special administrative override: by design, only a real, biometrically verified human can add a platform. The connection tool is served by every node on the network, so any builder can get it directly from a node and run it themselves — no app store, no central download server, no third party. Running it generates the platform’s own keys, signs the request, and returns a private confirmation secret only that platform can read. From that moment the platform is live. Because the same tool ships inside the node software, the ability to connect new platforms spreads with the network itself.

Protocols — how the network works

Protocol: Why SOV has no usernames

SOV deliberately has no usernames, no @handles and no display names you can choose. That is a privacy decision, not a missing feature. The moment citizens can type their own name, some of them will type their real name — and a network that promised no personal data would be quietly leaking it, permanently and publicly. So the protocol never offers the field at all.

Instead every citizen gets a nickname the network derives from their Sovereign ID: the same ID always produces the same nickname, on every device, with no lookup and nothing stored. It is generated on your own device, so it never travels anywhere and no server holds a name table. Your Sovereign ID remains the only network identity; the nickname exists purely so humans can recognise a contact at a glance instead of reading a 20-character string. Nobody can buy, squat, transfer or impersonate one, because nobody chooses one — including you.

Protocol: The Sealed-Launch Invariant (§905)

After the network ships its first signed snap, the relay code has NO special admin key — every privileged action must be authorised by a real biometrically enrolled citizen, signing with their own Ed25519 key, paying any fee from their own wallet. There is no admin token, no super-user key, no founder override, no "is_admin" column anywhere. Registering a platform, creating a poll, filing a petition, opening a dispute, publishing an Academy article — all follow the same template: the citizen builds a canonical signed payload, signs it on-device (the private key never leaves the device), the relay verifies the signature against the enrolled public key, checks the timestamp (±60s replay protection), takes any required fee, and performs the action. This is why SOV cannot be centralised by anyone — not the founder, not an operator coalition, not a state actor: the only way to act for a citizen is to BE that citizen, holding their key.

Protocol: Petitions — the off-cadence governance path

A petition lets any enrolled citizen propose changing a governance parameter without waiting for a formal poll cycle. Fellow citizens SIGN it (one signature per citizen, enforced at the database layer). If signatures cross the supermajority threshold (default 67% of enrolled citizens) the change activates immediately — no poll needed. If they cross the lower threshold (default 33%) a normal governance poll is created automatically for the rest of the network to vote on. If neither threshold is met before expiry, the petition is rejected by silence. Petitions are the escape hatch alongside paced polls: a clear supermajority skips debate; a significant minority escalates to a vote; weak support simply lapses. Both thresholds are themselves citizen-tunable.

Protocol: How citizens govern every value (4-part contract)

Every value citizens can vote on follows a mandatory four-part contract so there are NO hidden hardcoded constants after launch: (1) the parameter is declared with its range, (2) seeded with a sensible default on first boot, (3) read from the governance table at runtime (never a baked-in number), and (4) given a pre-built poll in the app Constitution tab. There are dozens of such parameters today — poll durations, fee rates, jury sizes, retention windows, fee rates, and more — and the registry grows as new features land via the same contract. A critical rule: governance values are always read as strings and compared exactly (a binary protocol gate checks == "1"), because a number cast silently breaks the gate. If citizens should be able to vote on it, it must pass through all four parts — no exceptions. This is the §905 invariant made concrete: the way a feature is written determines whether citizens can adjust it.

Protocol: Network fees — small, capped, and paid to the people who run it

SOV charges small, citizen-voted fees on a few actions, and none of it goes to a founder or gets burned into nothing — every fee flows into the operator reward pool that funds the citizens hosting the network. THE TRANSFER FEE is a fraction of a percent of the amount you send (a current default set by vote), and it is CAPPED so no single transfer — however large — ever costs more than a small fixed ceiling. That makes SOV cheaper than Bitcoin at every size: sending a tiny amount costs a fraction of a cent, and a whale settlement is capped at the ceiling. THE EXCHANGE FEE is a small percentage of a completed trade. THE PLATFORM FEE is paid once a year by a business that wants to accept "Sign in with SOV" — ordinary citizens NEVER pay to log in anywhere. All three fee rates and the transfer cap are governance parameters: citizens can vote them up, down, or to zero. This is the SOV economy in one sentence — the cut a bank would keep is instead a citizen-set, capped contribution that circulates straight back to the people doing the work.

Protocol: How a new node is let in

Anyone may run a node, but no node lets itself in. When a new node first meets the network it announces itself, and the peers that hear it check three things against their own copy of the ledger: that the operator gave a Sovereign ID at all, that the ID belongs to a genuinely enrolled citizen, and that this citizen is not already running more nodes than the rules allow. A node offering no operator ID is refused outright. That is not bureaucracy — a network that accepts anonymous nodes can be flooded by one person running thousands of them, and every vote and every payout after that is meaningless.

The question is not put to the whole network. Asking every node would get slower each time the network grew, and it would also be weaker than it sounds: if any single node's approval were enough, one dishonest node could wave in anything it liked. Instead a small random sample of peers is asked, and a majority of that sample must agree. The cost of admitting a node stays the same whether the network has ten nodes or ten thousand, and an attacker has to control most of a group they cannot choose and cannot predict.

Checking costs the network nothing. Every node already holds the full enrollment ledger, so "is this a real citizen?" is answered on the spot, from local data, without asking anyone. How many peers are sampled and how many must agree are both citizen-governed values, so the network can tighten or loosen its own front door by vote as it grows.

Protocol: Operator income — earning by keeping the network alive

Citizens who run relay nodes earn SOV for the real work of keeping the network running: witnessing transactions and staying online. A node must be CONTINUOUSLY up for a qualifying period (a current default of about three weeks) before it earns — sleeping or shutting the machine down breaks the streak, so payouts reward genuine uptime, not machines that are mostly off. Payment is a fixed reward per relay per month (governance-set), with a deliberately steep anti-monopoly curve: your first relay earns the full reward, a second and third earn a small fraction, and a fourth or beyond earns nothing but recognition — so running a farm of nodes gives you no advantage, keeping the network spread across many independent operators. Crucially, operators are paid FROM THE FEES that flow in first, and only then, capped, from the genesis reserve — so as the network grows and fees rise, it funds its own operators and the reserve becomes a long-term runway rather than a pot that drains. You can watch every fee flow into the pool and every payout leave it on the live SOV Economy screen — the ledger is public.

Protocol: One human, one identity — the face lock

SOV guarantees one account per living person, and it now enforces that across BOTH hands. Your palm is your key, and for accessibility you may enroll with either hand — but a single person could otherwise try to register their left palm as one identity and their right as another, because two palms of the same person look unrelated to a palm scanner. The face lock closes that gap. During the liveness check the app already looks at your face; from that it computes a private mathematical fingerprint (never a photo, and it cannot be turned back into your face) and the network checks it against everyone already enrolled. If your face already has an identity, a second enrollment is refused — you are told to recover your existing wallet instead. The check happens on the network side, so it cannot be skipped by a modified app. Identical twins are the one natural limit every face system shares. This is what keeps one-human-one-vote and one-human-one-wallet true, no matter which hand you scan.

To run a node, see Running a node.