Cowrie Research

tollgate-primary-sources-2026-05-02

3 min read

TollGate primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone TollGate whitepaper or litepaper surfaced.
  • The clearest current sources of truth were the official protocol repository README, the TIP-01 and TIP-02 spec files, and the OpenWRT reference implementation repo.
  • The materials consistently frame TollGate as reusable connectivity-sale infrastructure rather than as a one-off hotspot or hardware project.

Primary-source snapshots

1) Protocol repository README

  • URL: https://raw.githubusercontent.com/OpenTollGate/TollGate/main/README.md
  • Key excerpt:
    • The README says TollGate is “a protocol for selling network access in exchange for small, frequent bearer asset payments — streaming sats for connectivity.”
    • It says any device that can gate connectivity — WiFi router, Ethernet switch, Bluetooth tether, and similar devices — can act as a TollGate.
    • It also says customers pay with ecash tokens for exactly what they use and emphasizes “no accounts, no subscriptions, no sign-ups, no KYC.”

2) Architecture section

  • URL: https://raw.githubusercontent.com/OpenTollGate/TollGate/main/README.md
  • Key excerpt:
    • The architecture section splits the system into protocol, interface, and medium layers.
    • It explicitly lists protocol specs like TIP-01 and TIP-02, interface specs like HTTP-01/02/03 and NOSTR-01, and medium specs like WIFI-01.
    • The recipes section shows concrete combinations such as WiFi hotspot, Ethernet port, WiFi plus Nostr relay, and Nostr-only modes, which makes the project look like a general-purpose connectivity protocol rather than a single deployment recipe.

3) TIP-01 base events

  • URL: https://raw.githubusercontent.com/OpenTollGate/TollGate/main/TIP-01.md
  • Key excerpt:
    • TIP-01 defines a Nostr advertisement event carrying metering details such as metric, step_size, and supported TIPs.
    • It also defines session events with device identifiers and allotments plus structured notice events with severity and machine-readable error codes.
    • This is strong evidence that TollGate is standardizing negotiation and session semantics, not merely documenting an app.

4) TIP-02 Cashu payments

  • URL: https://raw.githubusercontent.com/OpenTollGate/TollGate/main/TIP-02.md
  • Key excerpt:
    • TIP-02 says a TollGate can accept multiple mints and multiple currencies.
    • It defines price_per_step tags for Cashu pricing and mint selection in the advertisement event.
    • It also says customers send Cashu tokens directly over the TollGate’s supported transport and receive connectivity allotment relative to token value.

5) OpenWRT reference implementation

  • URL: https://raw.githubusercontent.com/OpenTollGate/tollgate-module-basic-go/main/README.md
  • Key excerpt:
    • The implementation README says TollGate turns an OpenWRT router into a Cashu-powered payment gateway for internet access.
    • It says customers pay in sats on a time- or data-based basis, the router gates access, and balances can be swept to configured Lightning addresses.
    • It also says the same binary can act as a client to upstream TollGates so a router can buy internet and resell it automatically.

6) Feature and module surface

  • URL: https://raw.githubusercontent.com/OpenTollGate/tollgate-module-basic-go/main/README.md
  • Key excerpt:
    • The implementation README highlights per-mint pricing, trust allow/blocklists, configurable session increments, renewal thresholds, and profit-share payouts.
    • Its module list includes merchant, upstream session manager, upstream detector, wireless gateway manager, valve, config manager, tollwallet, lightning, and CLI components.
    • That breadth makes TollGate look like an operational connectivity-and-settlement stack rather than a single proof of concept.

Working conclusion

TollGate is best cataloged as pay-as-you-go network-access infrastructure: a protocol and operator stack for selling internet connectivity in granular increments using bearer-asset payments, especially Cashu plus Lightning-adjacent settlement. The decisive evidence in this pass was the combination of (1) the README’s explicit framing around streaming sats for connectivity, (2) the layered protocol/interface/medium architecture, (3) the TIP specs for advertisements, sessions, notices, and Cashu pricing, and (4) the OpenWRT implementation’s reseller, payout, and configuration surface.

Graph View