Skip to content

Add OP_PAIRCOMMIT topic page#875

Open
dergigi wants to merge 1 commit into
masterfrom
topic/add-op-paircommit-topic-page-871
Open

Add OP_PAIRCOMMIT topic page#875
dergigi wants to merge 1 commit into
masterfrom
topic/add-op-paircommit-topic-page-871

Conversation

@dergigi

@dergigi dergigi commented Jun 17, 2026

Copy link
Copy Markdown
Member

Adds a new OP_PAIRCOMMIT topic page with a concise explanation of the proposed tapscript opcode and what it enables.

  • adds data/topics/op-paircommit.mdx with verified references to BIP 442, bips.dev, and the Delving Bitcoin discussion thread

Closes #871


Build preview:

@dergigi dergigi requested a review from TumaBitcoiner June 17, 2026 01:05
@vercel

vercel Bot commented Jun 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
os-website Ready Ready Preview, Comment Jun 17, 2026 1:06am

Request Review


Bitcoin script already has simple ways to commit to single items with hashes. OP_PAIRCOMMIT adds a compact way to commit to pairs of items, and repeated applications can build Merkle-style commitments to larger sets of data. That makes it useful for advanced contracts that need to commit to structured data while revealing only the branch being used.

The proposal is discussed as a building block for more expressive tapscript contracts, including designs that need better in-script data commitments or staged delegation logic. It is also one of the opcode candidates discussed in the broader LNHANCE proposal set.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The proposal is discussed as a building block for more expressive tapscript contracts, including designs that need better in-script data commitments or staged delegation logic. It is also one of the opcode candidates discussed in the broader LNHANCE proposal set.
The proposal is discussed as a building block for more expressive tapscript contracts, including designs that need better in-script data commitments or staged delegation logic. It is also one of the opcode candidates discussed in the broader [LNHANCE][/topics/lnhance] proposal set.

LNHANCE needs to also be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add OP_PAIRCOMMIT topic page

2 participants