š
Original date posted:2022-08-11
š Original message:Earlier last year on March, there was a post here by Jeremy Rubin that explains how a person could delegate its UTXO to some script, by (AFAICT) creating a new transaction using that UTXO, with whatever script you want it to have.
It was written in terms of normal transactions, but can be extended to message signing transactions too.
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018615.html
Only the beginning of the post is relevant here.
- Ali
On Wed, Aug 10, 2022 at 11:11:10PM +0000, Ryan Grant wrote:
> >> TODO: A way for the initial signer to delegate to another
> >> scriptPubKey; needed for better privacy and CoinJoin/Lightning
> >> compatibility
>
> I need more documentation to understand this motivation.
>
> On Tue, Aug 9, 2022 at 8:46 PM Ali Sherief via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
> > In the case of the last TODO, related to delegation to another
> > scriptPubKey, I am not quite sure at the moment what to do about
> > it - perhaps you guys can place a MAST (two Merkle branches, to be
> > specific) - the first branch has the original signer's scriptPubKey,
> > the second branch contains the delegated signer's scriptPubKey.
>
> I don't understand this requirement, but it seems that whatever
> parties are involved can make signatures on the delegating and
> delegated keys.
Ali Sherief [ARCHIVE] /
npub1xqā¦q2u5f
2023-06-07 23:12:39
in reply to nevent1qā¦jk74
Author Public Key
npub1xq96jnxfzrdq4zgre20yqjrjsd29vcw8ymypl4v59cg6q6p66cts8q2u5fPublished at
2023-06-07 23:12:39Event JSON
{
"id": "79c5a6818b84147bb297618d0aefa67364056d4d07c2e0d30ce5eade8e439890",
"pubkey": "300ba94cc910da0a8903ca9e40487283545661c726c81fd5942e11a0683ad617",
"created_at": 1686179559,
"kind": 1,
"tags": [
[
"e",
"7911c55f95e735ed41026f38b07f1268ccff18d71d8415399db75a1d32939c97",
"",
"root"
],
[
"e",
"90cab1e88d69fc5c25f22aaec3b1094c30410455feb357e176689939a7d8915b",
"",
"reply"
],
[
"p",
"2f55bf03677afdb15d004a39383afba6220aa6c059cafa7b8827b87934d3c254"
]
],
"content": "š
Original date posted:2022-08-11\nš Original message:Earlier last year on March, there was a post here by Jeremy Rubin that explains how a person could delegate its UTXO to some script, by (AFAICT) creating a new transaction using that UTXO, with whatever script you want it to have.\n\nIt was written in terms of normal transactions, but can be extended to message signing transactions too.\n\nhttps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018615.html\n\nOnly the beginning of the post is relevant here.\n\n- Ali\n\nOn Wed, Aug 10, 2022 at 11:11:10PM +0000, Ryan Grant wrote:\n\u003e \u003e\u003e TODO: A way for the initial signer to delegate to another\n\u003e \u003e\u003e scriptPubKey; needed for better privacy and CoinJoin/Lightning\n\u003e \u003e\u003e compatibility\n\u003e\n\u003e I need more documentation to understand this motivation.\n\u003e\n\u003e On Tue, Aug 9, 2022 at 8:46 PM Ali Sherief via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e In the case of the last TODO, related to delegation to another\n\u003e \u003e scriptPubKey, I am not quite sure at the moment what to do about\n\u003e \u003e it - perhaps you guys can place a MAST (two Merkle branches, to be\n\u003e \u003e specific) - the first branch has the original signer's scriptPubKey,\n\u003e \u003e the second branch contains the delegated signer's scriptPubKey.\n\u003e\n\u003e I don't understand this requirement, but it seems that whatever\n\u003e parties are involved can make signatures on the delegating and\n\u003e delegated keys.",
"sig": "ec1b274b73a97fddea2a995f09893f07a86adf59a2146783221fe0fdd5c09bb45cc165de52ac0b62899b84925ed0665bf85ea6ebc18a5fe5ec9f595ce3038070"
}