Skip to content
Crypto.world

Research

BitSov: A Composable Bitcoin-Native Architecture for Sovereign Internet Infrastructure

Today's internet concentrates identity, payments, communication, and content hosting under a small number of corporate intermediaries, which the authors frame as an architectural problem producing…

BitSov: A Composable Bitcoin-Native Architecture for Sovereign Internet Infrastructure
arXiv
2603.28727
Published
2026-03-30
Authors
Oliver Aleksander Larsen, Rasmus Thorsen Larsen, Mahyar T. Moghaddam

AI summary

Overview

Research area: Blockchain systems architecture, specifically Bitcoin and Lightning Network-based decentralized internet infrastructure (cs.CR, accepted at BlockArch 2026, the 6th Workshop on Blockchain-Based Architectures, co-located with IEEE ICSA 2026).

Technical level: Intermediate. Readers should be comfortable with concepts such as keypairs, payment channels, block height, and layered system design, but the paper is written as an architectural position paper rather than a formal protocol specification.

Scope (one sentence): The paper proposes BitSov, an eight-layer architectural framework that composes Bitcoin, Lightning, decentralized storage, federated messaging, and mesh connectivity into a "sovereign internet" stack, and describes three architectural patterns plus a research agenda — without reporting an implemented or measured system.

What This Paper Is About

Today's internet concentrates identity, payments, communication, and content hosting under a small number of corporate intermediaries, which the authors frame as an architectural problem producing four single points of failure (revocable identity, intermediated payments, discretionary content persistence, and surveillable communication). Existing decentralized technologies such as Nostr, IPFS, the W3C DID standard, and the Lightning Network each address one piece, but they remain fragmented and are not composed into a coherent, self-sustaining stack. The goal of BitSov is to define such a stack anchored to Bitcoin's base layer, and to argue that payment-gated communication is a viable alternative to moderation-based abuse prevention.

Key Contributions

  1. An eight-layer composable architectural framework for Bitcoin-native sovereign internet infrastructure, spanning Base (Bitcoin L1), Connectivity, Identity, Payment, Storage, Communication, Governance, and Application layers, where each layer depends only on those below it.
  2. Three architectural patterns that emerge from this composition: payment-gated messaging, timechain-locked contracts, and a self-sustaining economic flywheel.
  3. An analysis of quality attributes (censorship resistance, spam resistance, scalability, resilience, privacy, sovereignty, sustainability) mapped to architectural mechanisms, together with an explicit discussion of five trade-offs and limitations.
  4. A research agenda of five open questions (RQ1–RQ5) intended to guide empirical validation by the BlockArch community.

Main Findings

  • Payment-gated messaging as spam deterrence: Every message requires a cleared Bitcoin payment cryptographically bound to message content, verified by the receiver before delivery. Two settlement paths are supported: Lightning micropayments for real-time messaging and on-chain transactions for high-value or archival messages.
  • Economic rather than computational cost: The pattern is positioned against proof-of-work challenges (Dwork–Naor, Hashcash) and against Whatsat, where payment serves primarily as a transport mechanism. In BitSov, payment is elevated to a foundational architectural principle meant to provide spam resistance, receiver compensation, sender accountability, and Sybil resistance.
  • Bounded threat model: Payment gating assumes rational attackers for whom per-message cost exceeds the expected benefit of spam. The authors state it does not eliminate abuse by well-funded adversaries willing to pay above-market rates, and that fee volatility may temporarily shift the cost–deterrence equilibrium.
  • Timechain-locked contracts: Subscriptions and licenses are specified by start block, end block, price in satoshis, and a Schnorr signature over all fields, leveraging Bitcoin's absolute timelocks. On-chain settlement is preferred for contracts because it gives permanent public verifiability; upon reaching the end block, the code transitions to open source.
  • Flywheel economics in satoshis: Revenue margin from paid services is converted into new sovereign nodes, which strengthen the mesh and attract more participants. The authors contrast this with DePIN architectures that rely on protocol-specific tokens, noting BitSov's flywheel avoids token speculation by operating entirely in satoshis.
  • Novelty relative to a known pattern catalog: The authors state that among the 120 blockchain software patterns cataloged by Six et al., neither payment-gated messaging nor timechain-locked contracts appear.
  • Acknowledged limitations: Five trade-offs are identified — payment friction, settlement trade-offs (Lightning sub-second messaging versus roughly 10-minute on-chain confirmation latency), onboarding and key-loss complexity, unvalidated scalability (on-chain throughput constrained to roughly 7 TPS globally, with flywheel dynamics at scale unmodeled), and the governance cold-start problem.
  • Position, not deployment: The paper explicitly states it proposes architectural patterns and design principles rather than reporting on a deployed system; no empirical measurements, benchmarks, or evaluation results are reported.

Methodology in Plain English

This is a position paper, so the method is architectural argumentation rather than experimentation. The authors start from an observed problem — concentration of internet infrastructure — and restate it as four architectural single points of failure. They then define five hierarchically ordered design principles, with sovereign Bitcoin-keypair identity as the non-negotiable root from which the others derive. Using those principles as constraints, they assemble existing, already-published technologies (Bitcoin L1, Lightning, IPFS or Arweave, Nostr-style relay messaging, mesh and satellite connectivity, the W3C DID standard) into an eight-layer stack in which each layer depends only downward. From that composition they derive three named architectural patterns, then map classic software quality attributes to the mechanisms that produce them. Finally, they enumerate trade-offs and convert the unresolved issues into a numbered research agenda. There is no prototype, simulation, deployment, user study, or quantitative evaluation.

Why This Matters

Impact on research. The paper offers a composition-level framing for decentralized infrastructure research: rather than proposing another token or chain, it asks how existing Bitcoin-anchored primitives fit together under explicit design constraints, and it converts that composition into falsifiable research questions (spam thresholds, adversarial performance, formal verification of timechain contracts, graceful degradation, flywheel equilibria). Its explicit positioning against an existing catalog of 120 blockchain software patterns gives other researchers a concrete gap to test.

Real-world applications (as described or implied by the paper's layers):

  • Censorship-resistant messaging and mail where delivery requires a Bitcoin payment rather than a platform's permission.
  • Subscription and software-licensing models anchored to Bitcoin block height, with contracts becoming open source at expiry.
  • Content publishing over IPFS or Arweave with sovereignty-preserving identity, where publishing is always an explicit opt-in action.
  • Connectivity through mesh, satellite, and ISP routes that keeps communication reachable when individual providers fail.

Industry relevance. The paper targets the commercial and regulatory pressure points of cloud, identity, and payment concentration — the authors cite that three cloud providers control over 60% of cloud infrastructure spending — and proposes an economic model (revenue converted into infrastructure nodes, denominated in satoshis) that could interest infrastructure operators, Lightning businesses, and organizations subject to deplatforming or payment freezes. Because it is a position paper, industry relevance is currently at the level of a design proposal and research agenda rather than a demonstrated alternative.

Future Directions

  1. Calibrate the payment gate (RQ1): Determine the micropayment threshold that maximizes spam deterrence while minimizing friction for legitimate users, including how fee volatility affects that equilibrium.
  2. Test under adversarial conditions (RQ2): Evaluate the architecture against Eclipse, Sybil, and state-level censorship attacks, and measure how effectively on-chain fallback mitigates Lightning-layer failures.
  3. Formal verification of timechain-locked contracts (RQ3): Establish whether these contracts can be formally verified and analyze the implications of block time variance.
  4. Graceful degradation and flywheel modeling (RQ4, RQ5): Identify patterns for partial-failure recovery across layers, and model the economic flywheel to find equilibrium conditions and failure modes.

The authors also name concrete validation paths: simulation of payment-gated messaging under adversarial load, prototyping on Bitcoin testnets, and formal verification of the timechain contracts. The governance cold-start problem is stated as not fully addressed by the current framework.

Target Audience

This paper is most useful to blockchain and software architecture researchers — particularly the BlockArch/ICSA community — working on layered settlement, decentralized identity, and Bitcoin-anchored systems. It also suits protocol designers and engineers evaluating Lightning-based messaging or block-height-anchored licensing, and graduate students who need a structured map of how Bitcoin, Lightning, IPFS/Arweave, Nostr-style relays, and mesh networking can be combined. Readers seeking empirical results, benchmarks, or a working implementation will not find them here, since the authors explicitly frame the work as a position paper proposing patterns and a research agenda.

Authors’ abstract

Today's internet concentrates identity, payments, communication, and content hosting under a small number of corporate intermediaries, creating single points of failure, enabling censorship, and extracting economic rent from participants. We present BitSov, an architectural framework for sovereign internet infrastructure that composes existing decentralized technologies (Bitcoin, Lightning Network, decentralized storage, federated messaging, and mesh connectivity) into a…

The full abstract on arXiv
Read the original paper