From 88a1ae5782390be7417ccc873018eae56299a486 Mon Sep 17 00:00:00 2001 From: Brandon Lucas Date: Fri, 30 May 2025 15:31:46 -0400 Subject: [PATCH 1/3] BIP77: remove duplicate "the" --- bip-0077.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bip-0077.md b/bip-0077.md index 07852f2b..25f73b26 100644 --- a/bip-0077.md +++ b/bip-0077.md @@ -222,7 +222,7 @@ receiver shares encoded in the URI. Instead of defining new Bitcoin URI parameters, the session-specific parameters are encoded in the [ fragment](https://datatracker.ietf.org/doc/html/rfc3986#section-3.5) -of the the mailbox endpoint URL. +of the mailbox endpoint URL. The `#` fragment separator character must be [RFC 3986 percent-encoded](https://datatracker.ietf.org/doc/html/rfc3986#section-2.1) From 6a311752dd4744e3886ab110ab356627884022e2 Mon Sep 17 00:00:00 2001 From: "Johan T. Halseth" Date: Mon, 2 Jun 2025 14:09:04 -0600 Subject: [PATCH 2/3] BIP443: list stack elements in bottom-to-top order and a few minor fixups --- bip-0443.mediawiki | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/bip-0443.mediawiki b/bip-0443.mediawiki index 620336e9..97f42fe1 100644 --- a/bip-0443.mediawiki +++ b/bip-0443.mediawiki @@ -38,7 +38,7 @@ This document is licensed under the 3-clause BSD license. The ability to constrain the future of coins beyond what is possible with presigned transactions is at the core of numerous attempts to improve bitcoin. Some of the proposed applications include: -* UTXO sharing schemes like Ark, CoinPools, Timeout Trees, etc. use various types of output restrictions in order to enable multiple parties to share the control of a UTXO, while ensuring that each participant controls their own `balance. +* UTXO sharing schemes like Ark, CoinPools, Timeout Trees, etc. use various types of output restrictions in order to enable multiple parties to share the control of a UTXO, while ensuring that each participant controls their own balance. * OP_VAULT[[bip-0345.mediawiki|BIP-345]] is a proposed opcode to implement a 2-step withdrawal process, enabling on-chain reactive security. * OP_CHECKTEMPLATEVERIFY[[bip-119.mediawiki|BIP-114]] is a long-proposed opcode to constrain a transaction to a ''template'' with a fixed set of outputs. * Sidechains and rollups could be implemented via a UTXO encumbered with a recursive covenant, updating the sidechain state root every time it is spent. @@ -135,10 +135,10 @@ The tapscript opcode OP_SUCCESS187 (0xbb) is constrain OP_CHECKCONTRACTVERIFY. When evaluating OP_CHECKCONTRACTVERIFY (OP_SUCCESS187, -0xbb), the expected format of the stack, shown bottom to top, is: +0xbb), the expected format of the stack, shown bottom-to-top, is: - + where: @@ -462,4 +462,4 @@ without upgrade except for mining and block validation. == Acknowledgements == -TODO \ No newline at end of file +TODO From ca05d44e640b8d30a07e9edea08cb5a15e70619e Mon Sep 17 00:00:00 2001 From: strmfos <155266597+strmfos@users.noreply.github.com> Date: Fri, 30 May 2025 12:41:50 +0200 Subject: [PATCH 3/3] BIP175: remove out-of-date implementation (404) --- bip-0175.mediawiki | 1 - 1 file changed, 1 deletion(-) diff --git a/bip-0175.mediawiki b/bip-0175.mediawiki index 30c79858..4ffba807 100644 --- a/bip-0175.mediawiki +++ b/bip-0175.mediawiki @@ -244,7 +244,6 @@ Communication between payer and payee as well as hashing the contract and genera ==Reference implementations== -* Reference wallet implementation, based on Copay project : https://github.com/commerceblock/copay ([[https://github.com/commerceblock/copay/pull/1|pull_request]]) * Reference implementation to Hash to Partial Derivation Path Mapping in javascript ([[https://github.com/commerceblock/pay-to-contract-lib/blob/master/lib/contract.js|https://github.com/commerceblock/pay-to-contract-lib]]) ==Reference==