For apps
Build on a
small world.
Bitcoin miners at the core. Overlays and applications around them. Your users at the edge, every one of them a single publish away. This is the overlay side of the network, for the applications that serve everyday users: wallets, exchanges, and services. Your users transact for free; you hand them certainty in return.
Producing blocks instead? See what miners get → Building on settlement data without mining? See the service-provider profile →
Publish once. Every overlay hears.
Applications run on overlays: token ledgers, payment rails, data feeds, whole ecosystems riding Bitcoin. 1BSV delivers to all of them the way it delivers everything: one send, carried to every subscriber simultaneously, with proof attached.
Every audience, one send
Publish an object and every overlay subscribed to its topics receives it in the same instant: your wallet users, your exchange integration, your analytics pipeline, all working from the same object at the same moment. One submission can name several topics at once, and every subscriber sees the whole list. No fan-out servers, no webhook farms, no sync drift between your own services.
Proof, not promises
Each object arrives complete with its Merkle proof, ready to check against a live header feed. Every subscriber, and every end user behind them, verifies independently, the moment it lands. No trust chain between services, no "confirmed, probably."
Cost tracks interest, not the chain
Subscribe by topic and receive exactly your slice; your bandwidth follows what your users care about, never chain volume. And because the network carries the fan-out, a growing audience adds nothing to the publisher's side: one send reaches ten subscribers or ten thousand.
This is what multicast buys an application: simultaneous, verifiable delivery to every overlay you serve, and to everyone else subscribed to the same topics. The object plane is published as open standards you can verify (BRC-148 and BRC-149 on the Standards page). The full design, from the per-host propagation problem to the integration surfaces, is in The overlay object plane.
Built for the businesses that serve users
Applications & Wallets
Serve your users overlay objects with proofs attached and a live header feed: SPV certainty for everyone you serve, without running mining infrastructure.
Exchanges
See the activity your markets depend on sooner, on a stream you can verify rather than trust.
Service providers have their own profile. A broadcaster, wallet backend, explorer or SPV service that builds on settlement data without mining picks the service-provider profile at signup: the whole transaction stream and subtree data, plus the live header feed, with no right to publish settlement into the network. Overlay objects stay with the application profile. The lanes are set out in the User Guide.
Bring your own stack
You don't have to build against the network to use it. A transaction broadcaster, an Arcade v2 and merkle-service stack for instance, runs exactly as released: an open-source bridge lands delivery beside it and speaks the interfaces it already speaks.
- Broadcast goes up once Instead of posting every batch to every datahub, your broadcaster submits once and the network fans it out to every miner on the fabric. Your sending cost stops growing with the number of parties you want to reach.
- Proofs are served from your own machine The subtree and block data your proof service builds from arrives down your tunnel, so the ingest it would otherwise pull across the wide area is served locally. Discovery stays on: if the bridge stops, your stack falls back to its ordinary paths with no proofs lost.
- Open, and you pay only for delivery The bridge is Apache-2.0 with no license check and no metering inside it, and the upstream software is neither forked nor patched. Pointing your broadcaster at it is one line of configuration.
The full design, including where a stock broadcaster over ordinary unicast remains the right answer, is in Arcade v2 on a multicast delivery fabric; the setup is in the User Guide. A broadcaster signs up as a service provider; the block data its proof service also builds from is arranged with us when its tunnel is provisioned, rather than elected from the standard menu.
Your users ride free
Every transaction your users send enters the network for free. What you pay for is the certainty you hand back to them.
- Volume-only You are billed for what is delivered to you (overlay objects and proofs on an application account, settlement data on a service-provider account), and for nothing else. No subscriptions, no minimums, no commitments.
- Ingress is never billed Publishing into the network, and the network's own repair retransmissions, cost you nothing.
- Keys & failover A standard WireGuard tunnel with a primary and a standby path and automatic failover. You generate the keys; we only ever hold the public half.
Give your users proof
The overlay lane is in early access and onboarding its first users. Onboarding is self-service with one approval step.