Rusty Russell on Nostr: BTW, Rearden (apparently from Jeremy?) pointed out that my simplified CTV-like scheme ...
BTW, Rearden (apparently from Jeremy?) pointed out that my simplified CTV-like scheme was flawed because it didn't commit to the order of input txids.
You need to xor SHA(inputnum | intxid) for each input to fix this.
I still like the scheme, because it clearly commits to everything the txid commits to (with modifications required by efficiency concerns). Like a "forward txid" to mirror the normal txids which are backwards references.
I should write it up, for comparison with CTV. Maybe once I've done that I'll no longer think it's a significant simplification?
Published at
2024-12-09 21:14:27Event JSON
{
"id": "1cfcbf4a1c1e622094f02c0741d5391624b425bcaee011c4d417268eb12cace5",
"pubkey": "f1725586a402c06aec818d1478a45aaa0dc16c7a9c4869d97c350336d16f8e43",
"created_at": 1733778867,
"kind": 1,
"tags": [],
"content": "BTW, Rearden (apparently from Jeremy?) pointed out that my simplified CTV-like scheme was flawed because it didn't commit to the order of input txids.\n\nYou need to xor SHA(inputnum | intxid) for each input to fix this.\n\nI still like the scheme, because it clearly commits to everything the txid commits to (with modifications required by efficiency concerns). Like a \"forward txid\" to mirror the normal txids which are backwards references. \n\nI should write it up, for comparison with CTV. Maybe once I've done that I'll no longer think it's a significant simplification?",
"sig": "23d09db53ce5f101e6d116ff86e2904cd4f0201d3257feff5e676dbf3614583b358ece0e99cbc8a58373a864c9b6866535c60b5eb2daf4627ae1ae8125b7e860"
}