Summary: TollGate is best cataloged as network-access and connectivity-sale infrastructure rather than as a novelty hotspot project or narrow captive-portal hack. Its primary sources describe a protocol for selling internet access in small increments in exchange for bearer-asset payments, especially Cashu ecash and sats-denominated pricing, across WiFi, Ethernet, Bluetooth, and Nostr-mediated negotiation paths. The crucial categorization clue in this pass is that TollGate is shipping both a protocol surface and operator stack: the core spec defines protocol, interface, and medium layers; pricing and session events are standardized; OpenWRT reference implementations exist; and routers can even buy connectivity from upstream TollGates and resell it automatically.
What it does:
Defines a protocol for selling network connectivity in granular time- or data-based increments
Uses bearer-asset payments, especially Cashu tokens, so customers can buy access without accounts, subscriptions, or KYC
Standardizes advertisements, session events, notices, pricing tags, and transport/interface combinations across different physical media
Supports WiFi, Ethernet, and future Bluetooth-style connectivity patterns, with both HTTP and Nostr transport options
Provides a reference OpenWRT implementation that turns routers into payment-gated internet access points
Supports reseller and multi-hop flows in which one TollGate can buy internet from another and resell it downstream
Key claims:
The main README says TollGate is “a protocol for selling network access in exchange for small, frequent bearer asset payments — streaming sats for connectivity”
The README says any device that can gate connectivity, including a WiFi router, Ethernet switch, or Bluetooth tether, can act as a TollGate
The README says customers pay with ecash tokens for exactly what they use and emphasizes “no accounts, no subscriptions, no sign-ups, no KYC”
The README says the same common data model works across different physical media and negotiation interfaces, and explicitly separates protocol, interface, and medium layers
TIP-01 defines standardized Nostr event types for advertisements, sessions, and notices, including metric, allotment, device-identifier, and structured error tags
TIP-02 defines Cashu pricing tags and says a TollGate can accept multiple mints and multiple currencies, with customers sending Cashu tokens directly over supported transports
The OpenWRT reference implementation README says TollGate turns an OpenWRT router into a Cashu-powered payment gateway for internet access and can also operate as a client to upstream TollGates in reseller mode
The OpenWRT implementation README also says the router can sweep balances to configured Lightning addresses, which makes the stack look like a reusable connectivity-and-settlement control plane rather than a one-off demo
Whitepaper: No canonical standalone TollGate whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official protocol repository, its TIP specs, and the OpenWRT reference implementation repo; see ../whitepapers/tollgate-primary-sources-2026-05-02.md.