Docs

Metanet Client and Explorer guides for users, builders and AI agents: setup, funding, payments, recovery, FAQs and portable BRC-100 integrations.

Read as Markdown

Use Metanet Client on desktop or Metanet Explorer on mobile, and build BSV applications with user-held keys. Start with the task you want to complete, then use the shared BRC-100 guides for portable integrations.

Layered BSV app architecture showing apps, BRC-100 wallets, wallet services, overlays, storage, messaging, and the BSV blockchain

The core idea is simple: your app asks a wallet for permissioned capabilities through the BRC-100 interface. The wallet keeps private keys with the user, exposes identity and transaction tools to approved apps, and coordinates with BSV infrastructure such as overlays, MessageBox, UHRP storage, and HTTP 402 payment flows.

Start Here

For a first no-spend success path, run the maintained starter at use.bsv.tools before using these docs as reference material.

Choose Your Path

GoalRead
Learn the mental modelConcepts
Build a working featureQuickstarts
Integrate a specific capabilityGuides
Add wallet-native authWallet authentication
Store local UTXO stateBaskets
Build public or multi-party stateOverlays
Serve verifiable mediaStorage and UHRP
Add paymentsMicropayments

The 2026 BSV Developer Stack

Use these components as the default map unless a guide says otherwise:

  • BRC-100 wallet interface: the portable app-to-wallet API.
  • Wallet implementations: Metanet Client on desktop and Explorer on mobile; verify portability with other supported BRC-100 implementations such as BSV Desktop and BSV Browser.
  • TypeScript SDK: @bsv/sdk for WalletClient, AuthFetch, transactions, PushDrop, certificates, storage helpers, and protocol utilities.
  • Wallet Toolbox: wallet infrastructure for building and operating BRC-100 wallets across TypeScript, Go, and Python ecosystems.
  • Overlays: topic managers and lookup services for app-specific public state.
  • MessageBox: encrypted peer-to-peer delivery for direct app coordination.
  • UHRP storage: content-addressed media hosting and resolution.
  • 402 payments: HTTP-native payment flows for APIs, media, and services.

Current References

Pressure-Test the Premise

These docs explain how to build with the stack. For source-linked answers to common BSV objections, tradeoffs, and unresolved questions, use the BSV evidence desk.

Was this page helpful?