BSV Key Derivation Scheme (BKDS)
The privacy-preserving key-derivation foundation beneath much of the stack.
People and peers
Add identity and private communication
Derive relationship-specific keys, reveal only needed certificate fields, and authenticate both ends of a channel.
Recommended sequence
Build the boundaries in order
- 01
Establish key semantics
Make privacy and purpose part of every derived-key request.
- 02
Model claims
Issue, hold, selectively reveal, and revoke certified identity fields.
- 03
Sign and encrypt payloads
Use interoperable envelopes for recipient-bound messages and signatures.
- 04
Authenticate the channel
Negotiate identity and certificates over the current peer-authentication protocol and HTTP transport.
Take the next step
Turn the map into a working plan
The working set
Standards in this path
Security Levels, Protocol IDs, Key IDs and Counterparties
Names security levels, protocols, key IDs, and counterparties consistently.
Identity Certificates
Defines selectively revealable identity certificates and revocation semantics.
Certificate Creation and Revelation
We define methods for an application to request that a wallet create and prove BRC-52 identity certificates. We define a set of additional messages that extend the BRC-1 application-to-wallet messaging layer with this functionality. We specify the functionality to be performed by the wallet as part of these processes, including a standard methodology for wal
Message Signature Creation and Verification
This document defines a protocol for creating and verifying digital message signatures in the Bitcoin ecosystem. It leverages the BRC-42 key derivation and BRC-43 invoice numbers to facilitate privately-verifiable signatures, increasing security and privacy in Bitcoin message interactions.
Serialization Format for Portable Encrypted Messages
This document describes a protocol for a portable message encryption and description scheme. It follows the BRC-42 key derivation and BRC-43 invoice number standards to protect the confidentiality of message content, without requiring the added complexity of agreeing on a specific BRC-43 protocol for the parties to use.
Peer-to-Peer Mutual Authentication and Certificate Exchange Protocol
The current peer mutual-authentication and certificate-exchange protocol.
HTTP Transport for BRC-103 Mutual Authentication
Binds BRC-103 peer authentication to HTTP transport.
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 →