📅 Original date posted:2014-12-04
📝 Original message:Is anyone working on a serialisation format to convey P2SH HD chains? For
example, to give someone who wants to make recurring payments a single token
that can be used to generate many P2SH addresses paying to a multisig script.
I'm thinking of something along the lines of a simple series of tokens, each
indicating either a HD chain or literal script content. For all HD chains in
the data, a child key would be generated based on the payment number, and all
tokens concatenated to form the P2SH serialised script. Eg, for a simple 2-
of-2, you would do something like this:
literal(OP_2) HDChain HDChain literal(OP_2 OP_CHECKMULTISIG)
Does this sufficiently cover all reasonable use cases?
Luke
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 15:27:41
in reply to nevent1q…jntr
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nSeen on
wss://relay.nostr.bandPublished at
2023-06-07 15:27:41Event JSON
{
"id": "7fdd3bde92e08f9d7ac829dc1fd522c9e66c684190f9cb68e1d4e47a4aca301c",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686151661,
"kind": 1,
"tags": [
[
"e",
"c6dbfebcd0f9a793242cef8ce15ddce4c1c9f20ab58ce3175f3a0ec04fe25d80",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2014-12-04\n📝 Original message:Is anyone working on a serialisation format to convey P2SH HD chains? For \nexample, to give someone who wants to make recurring payments a single token \nthat can be used to generate many P2SH addresses paying to a multisig script.\n\nI'm thinking of something along the lines of a simple series of tokens, each \nindicating either a HD chain or literal script content. For all HD chains in \nthe data, a child key would be generated based on the payment number, and all \ntokens concatenated to form the P2SH serialised script. Eg, for a simple 2-\nof-2, you would do something like this:\n literal(OP_2) HDChain HDChain literal(OP_2 OP_CHECKMULTISIG)\nDoes this sufficiently cover all reasonable use cases?\n\nLuke",
"sig": "d954491b8c7e2c50fede168091b31681a61b0a3f5a91e739b523e7db8625fdce25b9bc93c74e00533b4eaaef898f4263abffca2d38905f0634520770a8237970"
}