BRC-180: B — Bitcoin Data Protocol - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codifies the deployed B content record, complementing the data-carrier standards.
Clarifies optional fields, raw bytes, empty content, and the limits of legacy b:// transaction selection.
This focused draft supersedes the corresponding material in #1. It targets opldotdev/BRCs master only; no upstream submission or merge is requested. Based on current master 39a643f, without the stale corpus tree or duplicate BRC-159–162 files.
Validation: required sections, all three indexes for new proposals, local link resolution, numbering references, and git diff whitespace checks passed. Portable primitive/example checks are included where described above; these are not independent interoperability certification.
Remaining review limits: Raw-script extraction fixtures and pinned historical examples remain useful before upstream.
Draft dependencies (linked explicitly because every PR targets master independently):
Numbering follows master AGENTS.md: lowest available numbers after repository history and upstream/fork claims; BRC-178 belongs to the separately reviewed P2P proposal. BRC-190 retains its established number. Recheck allocation before merging and convert draft-branch citations to durable canonical references as dependencies land.