Unified, Vendor-Neutral, Unchanging, and Open BSV Blockchain Standard Wallet-to-Application Interface
The central application-to-wallet boundary. Start here for most Metanet apps.
Start here
Build a Metanet application
Keep keys out of app code, ask a standards-compatible wallet to act, and make permissions legible to users.
Recommended sequence
Build the boundaries in order
- 01
Adopt the interface
Model app capabilities around the vendor-neutral wallet interface rather than a wallet-specific SDK surface.
- 02
Name access safely
Choose stable protocol and key identifiers, security levels, and counterparties before adding cryptographic calls.
- 03
Organize app state
Use baskets for tracked outputs and labels for actions instead of a parallel app-owned wallet database.
- 04
Declare the app
Describe permissions and deployment components so wallets and infrastructure can present and run the app coherently.
Take the next step
Turn the map into a working plan
The working set
Standards in this path
BSV Key Derivation Scheme (BKDS)
The privacy-preserving key-derivation foundation beneath much of the stack.
Security Levels, Protocol IDs, Key IDs and Counterparties
Names security levels, protocols, key IDs, and counterparties consistently.
Wallet Transaction Output Tracking (Output Baskets)
Lets a wallet group and return application-relevant outputs as named baskets.
Transaction Labels and List Actions
BRC-65 extends the functionality of BRC-56 by introducing the ability to label Bitcoin transactions when they are created using the BRC-1 Transaction Creation Request. This extension allows applications to organize and categorize transactions for different purposes. BRC-65 also introduces the capability to list labeled transactions, providing applications wi
Group Permissions for App Access
This specification defines the manifest declaration format for grouped wallet permissions. It allows an application to declare, in one place, the protocol access, spending authorization, basket access, and certificate disclosure capabilities it expects to request from the user. The current interoperable manifest namespace is metanet.groupPermissions . Wallet
The deployment-info.json Specification
We define a comprehensive and authoritative specification of the deployment-info.json schema. It is intended to serve as a reference for developers building BSV blockchain applications that integrate with the LARS (Local Automated Runtime System) and CARS (Cloud Automated Runtime System) tooling and beyond. By following this specification, projects can ensur
This path is guidance, not a new protocol or maturity designation. Check each BRC’s upstream status note, normative language, and implementation section before shipping.
Editorial policy →