LogoLogo
  • README
  • Contribute
    • Discuss on Github
  • Example
    • Banana-Powered Bitcoin Wallet Control Protocol
  • Apps
    • The deployment-info.json Specification
  • Wallet
    • Transaction Creation
    • Data Encryption and Decryption
    • Digital Signature Creation and Verification
    • Input Redemption
    • HTTP Wallet Communications Substrate
    • XDM Wallet Communications Substrate
    • Window Wallet Communication Substrate
    • Wallet Transaction Output Tracking (Output Baskets)
    • Submitting Received Payments to a Wallet
    • Certificate Creation and Revelation
    • Unified Abstract Wallet-to-Application Messaging Layer
    • Transaction Labels and List Actions
    • Output Basket Removal and Certificate Deletion
    • Group Permissions for App Access
    • Extensible Proof-Type Format for Specific Key Linkage Claims
    • P Protocols: Allowing future wallet protocol permission schemes
    • P Baskets: Allowing Future Wallet Basket and Digital Asset Permission Schemes
    • Unified, Vendor-Neutral, Unchanging, and Open BSV Blockchain Standard Wallet-to-Application Interface
  • Transactions
    • Everett-style Transaction Envelopes
    • Simplified Payment Verification
    • Merkle proof standardised format
    • TSC Proof Format with Heights
    • Raw Transaction Format
    • TXO Transaction Object Format
    • Transaction Extended Format (EF)
    • Merkle Path JSON format
    • Compound Merkle Path Format
    • Background Evaluation Extended Format (BEEF) Transactions
    • Simplified Payment Verification
    • Merkle Path Binary Format
    • BSV Unified Merkle Path (BUMP) Format
    • Graph Aware Sync Protocol
    • Scalable Transaction Processing in the BSV Network
    • Atomic BEEF Transactions
    • BEEF V2 Txid Only Extension
  • Scripts
    • Bitcoin Script Binary, Hex and ASM Formats
    • Bitcoin Script Assembly Language
    • Pay to Public Key Hash
    • Pay to R Puzzle Hash
    • Pay to False Return
    • Pay to True Return
    • Push TX
    • Bare Multi-Signature
    • Pay to Push Drop
  • Tokens
    • There is no BRC-20
    • Definition of UTXOs as Bitcoin Tokens
    • Token Exchange Protocol for UTXO-based Overlay Networks
    • Mandala Token Protocol
  • Overlays
    • Overlay Network Data Synchronization
    • Confederacy Host Interconnect Protocol (CHIP)
    • Overlay Network Lookup Services
    • Confederacy Lookup Availability Protocol (CLAP)
    • Universal Hash Resolution Protocol
    • Overlay Network Transaction History Tracking
    • Private Overlays with P2PKH Transactions
    • Standardized Naming Conventions for BRC-22 Topic Managers and BRC-24 Lookup Services
    • Overlay Services Synchronization Architecture
    • Diverse Facilitators and URL Protocols for SHIP and SLAP Overlay Advertisements
  • Payments
    • Direct Payment Protocol (DPP)
    • Paymail Payment Destinations
    • Simple Authenticated BSV P2PKH Payment Protocol
    • PacketPay HTTP Payment Mechanism
    • Hybrid Payment Mode for DPP
    • HTTPS Transport Mechanism for DPP
    • Paymail BEEF Transaction
    • HTTP Service Monetization Framework
  • Peer-to-Peer
    • Authrite Mutual Authentication
    • PeerServ Message Relay Interface
    • PeerServ Host Interconnect Protocol
    • Identity Certificates
    • Genealogical Identity Protocol
    • Publishing Trust Anchor Details at an Internet Domain
    • Message Signature Creation and Verification
    • Serialization Format for Portable Encrypted Messages
    • Defining a Scalable IPv6 Multicast Protocol for Blockchain Transaction Broadcast and Update Delivery
    • Proven Identity Key Exchange (PIKE)
    • Peer-to-Peer Mutual Authentication and Certificate Exchange Protocol
    • HTTP Transport for BRC-103 Mutual Authentication
  • Key Derivation
    • BIP32 Key Derivation Scheme
    • BSV Key Derivation Scheme (BKDS)
    • Security Levels, Protocol IDs, Key IDs and Counterparties
    • Admin-reserved and Prohibited Key Derivation Protocols
    • Revealing Key Linkages
    • Protecting BRC-69 Key Linkage Information in Transit
    • Mnemonic For Master Private Key
    • Linked Key Derivation Scheme
    • Bidirectionally Authenticated Derivation of Privacy Restricted Type 42 Keys
    • Limitations of BRC-69 Key Linkage Revelation
    • Verifiable Revelation of Shared Secrets Using Schnorr Protocol
  • Outpoints
    • Format for Bitcoin Outpoints
    • Spending Instructions Extension for UTXO Storage Format
  • Opinions
    • Users should never see an address
    • List of user experiences
    • Legitimate Uses for mAPI
    • Security and Scalability Benefits of UTXO-based Overlay Networks
    • Improving on MLD for BSV Multicast Services
    • Web 3.0 Standard (at a high level)
    • Thoughts on the Mandala Network
    • Outputs, Overlays, and Scripts in the Mandala Network
  • State Machines
    • Simplifying State Machine Event Chains in Bitcoin
Powered by GitBook
On this page
  • Abstract
  • Motivation
  • Specification
  • Implementation
  • References

Was this helpful?

Edit on GitHub
Export as PDF
  1. Opinions

Web 3.0 Standard (at a high level)

  • Ty Everett (ty@projectbabbage.com)

Abstract

This BRC proposes a high-level, rough-draft standard for Web 3.0, defining the integration of blockchain technology, federated overlay networks, digital wallets, and enhanced browser functionalities to enable a decentralized and serverless web experience. This evolves the current web standards to facilitate content and applications that are fully powered by blockchain, allowing users to interact and manage their identities, assets, and cryptographic keys securely and independently.

Motivation

The current Web 2.0 model relies heavily on centralized servers and client-server architecture. The move to Web 3.0 requires delinking the reliance on central servers by enabling a federated and decentralized infrastructure. This BRC aims to cobble together the necessary standards and protocols to achieve this, focusing on leveraging the previous work in wallet technology, overlays, and decentralized storage to enhance user control, privacy, and interaction on the web.

Specification

  1. BRC26 Storage Overlay Network:

    • Facilitates decentralized storage and retrieval of web content.

    • Domain names point to file hashes rather than IP addresses.

    • Integration with DNS via TXT records for domain-to-hash resolution (DNS TXT points to UHRP URL of index.html).

    • UHRP URLs replace HTTP URLs for referencing scripts, stylesheets, and images inside HTML.

    • Phase out HTTP URLs in a, img, video, link, and script tags in favor of UHRP URLs.

  2. BRC56 Wallet Interface:

    • Provides APIs for digital wallets embedded in browsers.

    • Allows users to manage identities (signing, encrypting, certifying, verifying), assets (in baskets), and cryptographic keys.

    • All identity resolution, permissioning, and certificate management features are supported.

    • Securely interfaces with content and applications via a JavaScript interface on the window object.

  3. Peer-to-Peer Communication:

    • Based on BRC33 (PeerServ) for direct message exchange between users.

    • Expose a JavaScript API for this on the window object.

    • Enhances direct user interaction without intermediary servers.

    • Supports real-time sockets.

  4. Browser Modifications for Web 3.0:

    • Support for executing local code and interacting with BRC56 Wallet API, and using Overlays for state coordination.

    • Deprecation of Fetch API in favor of authenticated and monetized Fetch alternatives (BRC-31 and BRC-41 wrapped versions on all requests).

    • New JavaScript APIs for overlay service queries (BRC-24), transaction submission (BRC-22), and peer-to-peer communications (BRC-33), all of which support federation across many providers at the browser level.

    • Browsers now host digital wallets. Wallet data to be backed up across many providers.

Implementation

Incorporate BRC26 hash resolution capabilities, BRC56 wallet interface in the window object, and BRC33 message relay between users within web browsers. Replace HTTP and the Fetch API with wrapped versions incorporating BRC-31 and BRC-41 for standardized authentication and monetization of all backend systems.

References

  • [BRC22: Overlay Transaction Submission]

  • [BRC24: Overlay State Lookups]

  • [BRC26: Storage Overlay Network]

  • [BRC31: User authentication protocol]

  • [BRC33: PeerServ Message Relay]

  • [BRC41: Payments protocol]

  • [BRC56: Wallet Interface]

PreviousImproving on MLD for BSV Multicast ServicesNextThoughts on the Mandala Network

Last updated 5 months ago

Was this helpful?