AI and Bitcoin: how they connect

Digital sovereignty from your pocket

A remote Linux server, operated by AI and paid for in bitcoin, is the missing piece of digital sovereignty.

An alpha proof of concept already starts one from a phone.

Mobility is freedom

No mobility

The peasant is always lacking in mobility. He is as attached to the ground as the plants he cultivates.

Franz Oppenheimer, The State (1908)

Physical mobility

This unprecedented physical mobility will give us the ability to leave a country without leaving our home, increasing competition between governments.

Patri Friedman, “Beyond Folk Activism” (2009)

Mobility in cyberspace

We must declare our virtual selves immune to your sovereignty, even as we continue to consent to your rule over our bodies.

John Perry Barlow, “A Declaration of the Independence of Cyberspace” (1996)

Mobility in cyberspace, today

Cyberspace is the new flag, arguably the most important one, which takes away the necessity of many earlier flags.

Katie The Russian, “Short The State”, Bitcoin Magazine (2022)

Three steps of mobility

So how much of your life is actually in cyberspace, under your control?

The gap Bitcoin left

Bitcoin made money mobile. The rest is rented.

What you own

  • Your keys, maybe

What you rent

  • Mail, files, documents
  • Code and chat
  • Your business
  • Often your node and wallet too

It was never the law. It was skill.

  • Self-custody is hard.
  • Running your own node is hard.
  • Running a Lightning node safely is out of reach for most people.

That barrier just fell.

What changed

AI is the sysadmin

“I’ve run Linux on desktops and servers for 25 years. AI is better at it than I am.”

  • You describe what you want. It installs, configures, hardens and maintains.
  • Linux is the open platform underneath. Nobody can revoke it.

The proposal

Your server in cyberspace

At least one always-on remote Linux server. AI operates it. Bitcoin pays for it.

Why remote, and what it isn’t

Threat Home and laptop Remote server
Home is raided Lost Survives
Devices seized at a border Lost Survives
Provider seizes or reads the machine Not affected Exposed
You want to change jurisdiction Move yourself Move the server

It is redundancy and a choice of jurisdiction, not immunity. It complements a homelab. It doesn’t replace one.

Cypherpunks write code

Farseed

An AI agent that runs entirely in your phone’s browser.

  • It pays for its own model and server over Lightning, with your approval.
  • It builds the server over SSH.
  • It hands you a second agent that lives on that server.

Alpha proof of concept · github.com/douglaz/farseed

How it fits together

Demo

Recorded run from a phone · about 40 minutes of real time, sped up to 3

video goes here

What just happened

  • The agent ran in my browser and held the keys. Only the model calls went out.
  • I approved every payment by hand, in Lightning.
  • The result is a server I control, with its own agent I can keep talking to.

What’s real and what isn’t yet

Said plainly

  • It works end to end today, as an alpha, on a path prepared for it.
  • The hosting provider in the demo is our own instance of LNVPS, at a demo price.
  • Hermes follows recipes that ship with the machine. It isn’t improvising.
  • The Bitcoin node starts from a pruned chain copy that we host, then validates new blocks.
  • The Lightning node is one you can look at: no funds, no channels, no seed backup, keys on a rented server.

The hard part is the browser

  • Providers that take bitcoin rarely offer an API a browser can use to rent a machine with no human clicking through.
  • A browser can’t open SSH by itself. It needs a relay, so the page must know the server’s key in advance.

From a Linux machine none of this is hard. From a phone browser is what makes it reach ordinary people.

Two objections

“Isn’t an online server unsafe?”

  • Nothing is absolutely safe. Offline keys face theft, coercion, disaster and your own mistakes.
  • AI helps the attacker and the watcher too. It doesn’t break good cryptography, and it makes hardening cheaper for defenders.
  • The proposal is not “put everything online”. It is use AI to run what should be online, well.

“Isn’t rented AI giving up sovereignty?”

  • The ideal is your own inference, on hardware you control or rent bare.
  • Until then, pay-per-use, privacy-focused vendors such as PPQ are the lesser evil.
  • A frontier model hardening your infrastructure beats a weak local model doing little.

Bootstrapping always starts on something you don’t control.

Start this month

Rent one server. Pay in bitcoin. Let an AI help you run one service on it.

A remote Linux server, operated by AI and paid for in bitcoin, is the missing piece of digital sovereignty.

The stack, by name

Role Tool
Agent in the browser Farseed (alpha) · github.com/douglaz/farseed
Agent on the server Hermes Agent, by Nous Research
Chat front end T3 Code
Inference, paid in Lightning PPQ (PayPerQ), running DeepSeek V4.1-Flash
Server, paid in Lightning LNVPS (our own instance of the open-source software)
SSH relay for the browser paid-tcp-relay · github.com/douglaz/paid-tcp-relay
Operating system NixOS
Bitcoin and Lightning Bitcoin Core, lnd
Phone wallet and node remote Phoenix, Zeus
Private network Tailscale

Backup

Where are my keys in the browser?

  • An encrypted journal in the browser’s private file system: AES-256-GCM, key derived from your passphrase with PBKDF2, 600,000 rounds.
  • While unlocked, the keys sit in a background worker. The visible page never gets them, and it holds no wallet.
  • Someone with your unlocked phone can use the app as you, but can’t read the keys out.
  • A malicious extension could capture your passphrase as you type. Use a dedicated browser profile and a real passphrase.

Every browser obstacle

  • Not every provider accepts Lightning, though many accept on-chain bitcoin.
  • Many have no API to launch a machine, or only after a manual first launch.
  • APIs without CORS headers can’t be called from a page.
  • SSH needs a relay, so the host key must be known in advance.
  • The page can’t pay: a human pays each invoice, on purpose.
  • Mobile browsers suspend background tabs, so the agent must survive interruption.

What the demo still leans on

  • Manual steps: paying two invoices, signing in to T3 Code once, approving one Tailscale sign-in.
  • Third parties: PPQ for inference, the SSH relay we run, the hosted T3 Code sign-in, Tailscale.
  • Worth keeping even after bootstrap: a hosted password manager, mail, a mesh VPN.