bip-bod-descriptors: address review comments
Some checks failed
GitHub Actions Check / Link-Format-Checks (push) Has been cancelled
GitHub Actions Check / Build-Table-Checks (push) Has been cancelled
GitHub Actions Check / Diff Checks (fails until number assignment) (push) Has been cancelled
GitHub Actions Check / Typo Checks (push) Has been cancelled

This commit is contained in:
seedhammer 2026-02-02 17:35:12 +01:00
parent bd11813f2b
commit bb9d2fd222
2 changed files with 18 additions and 12 deletions

View File

@ -1381,6 +1381,13 @@ users (see also: [https://en.bitcoin.it/wiki/Economic_majority economic majority
| Informational
| Draft
|-
| [[bip-0391.mediawiki|391]]
| Applications
| Binary Output Descriptors
| SeedHammer
| Specification
| Draft
|-
| [[bip-0392.mediawiki|392]]
| Applications
| Silent Payment Output Script Descriptors

View File

@ -1,12 +1,11 @@
<pre>
BIP: ?
BIP: 391
Layer: Applications
Title: Binary Output Descriptors
Author: SeedHammer <team@seedhammer.com>
Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-seedhammer-binary-output-descriptors
Authors: SeedHammer <team@seedhammer.com>
Status: Draft
Type: Standards Track
Created: 2024-01-31
Type: Specification
Assigned: 2026-01-27
License: BSD-2-Clause
</pre>
@ -14,10 +13,10 @@
===Abstract===
This document proposes an efficient encoding format for output descriptors as
defined by [[bip-0380.mediawiki|BIP 380]] and its extensions. Based on
key-value maps as defined by [[bip-0174.mediawiki|BIP 174]], the encoding
supports descriptor and key metadata.
This document proposes an efficient container format for encoding an output
descriptor as defined by [[bip-0380.mediawiki|BIP 380]] and its extensions.
Based on key-value maps as defined by [[bip-0174.mediawiki|BIP 174]], the
encoding supports descriptor and key metadata.
===Copyright===
@ -61,7 +60,7 @@ support at the time of this writing.</ref>.
The Binary Output Descriptor (BOD) format consists of a fixed header, a
key-value map describing the output descriptor, and a key-value map for
each key.
each key.
<bod> := <magic> <global-map> <key-map>*
<magic> := 0x62 0x6F 0x64 0xFF
@ -85,10 +84,10 @@ The defined global types are as follows:
| <tt><compact size uint birth block><bytes></tt>
| The earliest block height that may contain transactions for the descriptor, optionally followed by the UTF-8 encoded name of the descriptor.
| <tt><bytes descriptor></tt>
| The output descriptor in BIP 380 format without inline keys<ref>''Why not encode the descriptor in binary?'''
| The output descriptor in BIP 380 format without inline keys<ref>'''Why not encode the descriptor in binary?'''
Designing and maintaining a compact binary representation of the complex and evolving BIP 380 descriptor
language entail significant effort and introduce a time lag from the introduction of new BIP 380 features
to the spcification of the binary counterpart. We don't believe the space savings outweigh the disadvantages.
to the specification of the binary counterpart. We don't believe the space savings outweigh the disadvantages.
The major source of bloat, base58-encoded keys, are binary encoded for compactness and
can be re-used multiple times in a single descriptor.