Apps

In the BSV Blockchain ecosystem, an App is more than just a piece of software that uses the BSV blockchain. It follows specific standards for its codebase structure and how it communicates with wallets, deployment metadata, and guides users through permission requests. Below are key ideas to help you understand what makes a BSV App unique.

Core Concepts

1. Deployment Metadata
   Every App should define its deployment metadata in a deployment-info.json file. BRC-102 provides a standardized structure so wallets, services, and other tools can quickly parse an App's declared resources and launch configurations (e.g., local dev with LARS, deployment in the cloud with CARS).

2. App Manifest and Permissions
   Frontends deployed online typically have a manifest.json that describes what permissions they require from users. Whether that's the ability to spend a certain amount of satoshis, read certificate fields, or interact with specific baskets of UTXOs, you can structure these permissions systematically. Group Permissions (described by BRC-73) also go here, making it simpler for users to approve or deny.

3. Wallet Interaction
   Apps talk to wallets using vendor-neutral messaging layers. BRC-100 outlines the unified abstract approach for calling wallet functions like transaction creation or data decryption. Wallets like BSV Desktop use this standard.

4. Overlay Services Apps can be frontend-only, backend-only, or both. If they have a backend folder, it describes one or more topic managers and lookup services responsible for tracking and managing the tokens it creates on the network. You can read about overlay concepts in other docs on this site.

Curation of UTXOs and Tokens

Apps often rely on tokens or specialized transaction outputs to enable unique user experiences, like digital goods, loyalty points, etc:

• Basket Model: BRC-46 groups outputs into "baskets" so an App can quickly locate or manage only the tokens relevant to its functionality.
• Advanced Permission Schemes: For future-proofing and extra security control over digital assets, upcoming standards like BRC-99 let you define specialized "basket IDs" and rules that determine who can spend or view them.

Why Build on BSV Standards?

1. User Trust & Simplicity
   By implementing a standardized manifest and permission flow, you're fostering trust. Users understand precisely what they're granting, and the wallet can solicit clear, consistent prompts.

2. Interoperability & Future-Proofing
   Thanks to a standardized approach, your App naturally works across different wallets that follow the same open protocols. As new permission systems evolve, your App can adopt them seamlessly.

3. Reduced Development Overhead
   No need to tailor separate flows for each wallet or custom lifecycle. By referencing BRC documents, you can code once and cover every compliant wallet integration immediately.

Next Steps

• Bundles & Permissions: Read about BRC-73 to see how to request group permissions from a user via manifest.json.
• Deployment Best Practices: Learn more about how to structure your deployment-info.json in BRC-102.
• Wallet Integration: Familiarize yourself with BRC-100 for consistent wallet interactions across your app's entire user base.
• In Practice: Build your first app by following this guide.

Building an App with BSV standards ensures you tap into a robust and open ecosystem—where wallets, certificates, tokens, and data all interact seamlessly on a scalable BSV blockchain.