Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
BIP 392 Silent Payment Output Script Descriptors Guide
BIP 392 guide to Draft sp() descriptors, spscan and spspend encodings, watch-only and full-wallet forms, key origins, recovery and validation.
This guide explains BIP 392 Silent Payment Output Script Descriptors in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 392 is a Draft specification for representing BIP 352 Silent Payment wallets as output script descriptors. The new top-level sp() expression combines Silent Payment key material with sender input public keys to describe BIP341 taproot outputs.
- Why it matters: BIP 392 can make Silent Payment wallets portable within descriptor infrastructure, provided every backup clearly declares whether it is watch-only or spend-capable and implementations strictly validate keys, networks and derivation context.
- Current position: BIP 392 is a Draft specification for representing BIP 352 Silent Payment wallets as output script descriptors.
What this means in simple English
A BIP is a document that proposes or explains a Bitcoin idea, standard or rule. A BIP number does not mean the idea is active. Some BIPs are widely used, while others are drafts or historical proposals.
You do not need to read code to understand the main point. Start with the status, the problem being addressed and the practical effect on ordinary users, wallets, miners or node operators.
Simple example
Think of a mempool as one node’s waiting room for valid transactions that have not yet entered a block. Different nodes can have different waiting rooms, and the contents can change from one second to the next.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Taproot:
- A Bitcoin upgrade that added new signature and script options for spending outputs.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Descriptor scope
sp() is a top-level descriptor only. It creates taproot output scripts dynamically from sender inputs, so it cannot be nested under sh(), wsh() or another script wrapper.
spscan
The Bech32m spscan form contains the private scan key and compressed public spend key. It supports detection and watch-only operation but should not grant spending authority.
spspend
The Bech32m spspend form contains both scan and spend private keys. Treat it as full-wallet secret material with encryption, access control and offline backup.
Two-argument form
sp(scan,spend) requires a private scan key and permits a single public or private spend expression, including compatible aggregate keys. Uncompressed keys are forbidden.
Origins and networks
Optional key-origin data records fingerprint and derivation depth. Mainnet and test networks use distinct human-readable prefixes; reject cross-network or bad-checksum material.
Recovery boundary
A Silent Payment descriptor may expose scan capability, spending capability or both. Backups must label that authority explicitly and retain any derivation and maximum-label information required for complete scanning.
How specialists test it
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
Frequently asked questions
What is BIP 392 Silent Payment Output Script Descriptors?
BIP 392 is a Draft specification for representing BIP 352 Silent Payment wallets as output script descriptors. The new top-level sp() expression combines Silent Payment key material with sender input public keys to describe BIP341 taproot outputs.
Is BIP 392 Silent Payment Output Script Descriptors active or supported today?
BIP 392 is a Draft specification for representing BIP 352 Silent Payment wallets as output script descriptors.
Why does BIP 392 Silent Payment Output Script Descriptors matter?
BIP 392 can make Silent Payment wallets portable within descriptor infrastructure, provided every backup clearly declares whether it is watch-only or spend-capable and implementations strictly validate keys, networks and derivation context.
Do beginners need to use the technical details?
No. Most readers only need to understand the idea and its current status. Developers and node operators can use the primary sources when they need the exact technical rules.
Conclusion
BIP 392 can make Silent Payment wallets portable within descriptor infrastructure, provided every backup clearly declares whether it is watch-only or spend-capable and implementations strictly validate keys, networks and derivation context.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 explained in detail: its seven consensus restrictions, 55% signalling threshold, chain-split risk and August 2026 closure.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.