Open shannona opened 2 years ago
I think it is sortedmulti
, as multi is being slowly deprecated.
As an addendum, Sparrow reads this correctly, though they read off of the crypto-output
:
ur:crypto-output/taadmetaadnytaaddloxaxhdclaohldlmdrtlacxhnfpptplfyltwelafsnezslyndhllnvdimmwlpylkbwzjltbdmenaahdcxlejtimcnrlbtdemdoereyaqzprkpndbdgwfzflqdbzkohgzobycxcnvabaosbglfamtaaddyoeadlocsdyykaeykaeykaoykaocyhngrmuwzaycynewncnlblgfpvaae
Which is:
401(410(303({3: h'025d2f95c080206041a9ae4487ed803d9ffa819b5d86e76a9485f77ef26fd62e36', 4: h'8a6e6a23b70d2895a2b5f8b4b2759b0b4f4047b3157657fb112023e60ea71282', 6: 304({1: [48, true, 0, true, 0, true, 2, true], 2: 1615565810}), 8: 2683380607})))
401 is wsh
and 410 is cosigner
(versus 407 for sorted-multisig
), per the CDDL.
But my question remains of where cosigner
came from and if it's in an evolving standard.
It's based on a conversation I had with Craig Raw. I'll post screen caps of it to Signal.
The cosigner key derivations have descriptors such as this:
I can't find any documentation on
cosigner
as a descriptor function, and it's not supported bybitcoin-cli
. Is this sufficiently compatible, or should we be usingmulti
instead?Per #145.