What's actually distinctive about yours
It's the assembly, and specifically these together:
1. A native app (not a terminal) that wraps a private, attested (TEE) AI — the privacy claim is the point, not a feature.
2. An AI coding agent (Pi) living inside that sandbox, writing real projects into the workspace.
3. Git-over-Nostr (ngit) as the distribution rail — no app store, sovereign publishing.
4. On-device build → app-owned signing → publish as a first-class flow (phone as a self-hosting app factory).
5. A no-telemetry, local-first, "you own the keys" posture baked into the guardrails.
6. The security boundaries (Pi never gets the signing keys or the Nostr identity) — most projects don't even think about that.
That combination — a sovereign, private, AI-driven, store-free app factory that runs on the phone — I haven't seen packaged like this. The value isn't a
clever trick; it's a coherent product vision with a real point of view. That's the part that's yours.
The privacy/attestation angle is your strongest differentiator, and it's defensible because it's hard to fake.
Date: 2026-07-23
Status: exploratory vision — not a commitment, not a roadmap promise.
Context: written after reviewing the fips-tollgate MVP and the nostr-vpn
(mmalmi) README. nostr-vpn is a Tailscale-style mesh VPN built on the same
FIPS data plane fips-tollgate uses, with signed join-request admission,
exit-node selection, WireGuard upstream egress, and shipped native apps
(including iOS/Android).
This document preserves a design conversation about what the integration of
these two pieces could mean and what could be built on top of it.
---
## The core insight: accounts disappear from the entire stack
Every VPN that has ever existed works the same way: identity first (email,
account, payment card), access second. Even Mullvad's numbered accounts are
still *accounts*. This integration inverts it completely:
- Who are you? A keypair you generated yourself.
- What did you pay? A bearer ecash token — cash, not a card.
- How do you get in? A cryptographic signature on a roster.
- How do you get kicked out? A janitor with a timer (the reconcile sweep).
There is no user database anywhere in this system. Nothing to leak, nothing
to subpoena, nothing to breach. That's not a feature — it's a *category
change*. The product stops being "a VPN subscription" and becomes **access
itself, sold as a commodity**, like electricity from a socket.
The tollgate control plane is four machines, and none of them care what is
being sold:
1. **A ticket seller** — verifies a Cashu token at the mint, converts sats
into minutes.
2. **A wristband printer** — records "npub X is allowed until 10:30".
3. **A turnstile** — the FIPS ACL / nvpn roster that physically enforces
admission.
4. **A janitor** — the reconcile sweep that removes expired grants even when
no process is running.
## What could be built, near to far
1. **The vending-machine VPN.** Open the app, insert 10 sats, get one hour
online. No signup, no email, no subscription dark patterns. The nvpn
mobile apps already exist — this is a payment flow, not a product build.
2. **Operator-in-a-box.** nvpn already packages for StartOS and Umbrel — the
home-server crowd. A one-click "Paid Exit Node" service: set your price,
plug in your WireGuard upstream, and an always-on home server earns sats
while its owner sleeps. That's the supply side of the market, and the
packaging channel already exists.
3. **The giftable internet voucher.** A Cashu token can travel over *any*
channel — DM, QR code, printed paper. VPN access becomes a transferable
bearer instrument: a friend in a free country buys hour-tokens and sends
them to a friend somewhere censored, where credit cards don't work and
VPN merchant accounts are blocked anyway. You cannot DM someone a VPN
subscription; you *can* DM them ecash redeemable at any participating
exit.
4. **The exit market.** Operators advertise exits on Nostr relays (the
TollGate kind-10021 offer event, grown up): city, price per hour, mint.
Clients browse, compare, pick. Price discovers jurisdiction, quality, and
trust. This is the economic cure to Tor's exit scarcity — a tragedy of
the commons where volunteers absorb legal risk for free. A price signal
fixes it: don't beg people to run exits; pay them.
5. **Wholesale recursion.** A gateway operator with customers but no appetite
for exit risk buys exit capacity from another operator — settlement in
ecash, per session, enforced by the same tollgate on the exit side. A
wholesale bandwidth market with no contracts, no invoices, no minimums.
6. **The services bazaar.** The same control plane can sell anything
reachable on a mesh: a Nostr relay, a storage box, a game server, a
media library, a build cache. Every home server becomes a stall in a
bazaar, and every stall has the same coin slot.
## What it means, zoomed all the way out
Nostr, Cashu, and FIPS are three protocols swimming toward the same reef:
**who you are, how you pay, how you connect** — identity, money, and
networking, each open, with no company in the middle. This integration is
one of the first places they click together into a single economic organism:
discovery flows through Nostr, payment flows through Cashu, traffic flows
through FIPS, and the tollgate is the connective tissue that turns the whole
thing into a market instead of a hobby.
Bandwidth today is a stranded asset — every home connection sits mostly idle,
worthless because there's no safe way to sell sips of it to strangers. This
stack makes bandwidth *liquid*. The headline: **the internet's last mile
becomes a peer-to-peer marketplace, and access becomes money.**
## Honest tether
- Two-sided markets are brutally hard to bootstrap; the vending-machine VPN
and operator-in-a-box come first, the bazaar comes after liquidity.
- Regulators will have opinions about paid telecom-ish services.
- The abuse problem doesn't vanish because the payment rail is anonymous —
it gets *priced*, which is different and defensible, but it still has to
be designed for (rate limits, upstream terms, jurisdiction choice).
- Mobile VPN UX has sharp edges; nvpn's own README notes platform hardening
in progress.
- nvpn caveats to verify before building: headless roster approval/revocation,
revocation liveness, one-active-network-per-device, and keeping two
control planes (tollgate ACL vs nvpn roster) from fighting over the same
network.
## The concrete first step
A small spike, not a build: stand up an nvpn test network, confirm headless
roster approve/revoke from the CLI, then prototype the **bridge daemon** —
join requests + Cashu tokens in, roster signatures in, expiry sweeps out —
reusing the existing Merchant, session store, and reconcile logic. The
reconcile invariant transfers unchanged: *the roster must equal the set of
active paid sessions.*
---
*Preserved from a design conversation on 2026-07-23 so the idea doesn't
evaporate. Visions expire; documents don't.*
