It is better if the scheme is strongly deterministic.On 16 Jan 2015 17:09, Alan
Reiner wrote:
>
> I see no reason to restrict compressed/uncompressed. Strings don't have to
> be the same length to sort them lexicographically. If a multi-sig
> participant provides an uncompressed key, they are
I see no reason to restrict compressed/uncompressed. Strings don't have
to be the same length to sort them lexicographically. If a multi-sig
participant provides an uncompressed key, they are declaring that the
key that they use and it will only be used uncompressed. Clients don't
have to go lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It would - it assumes you have the set of keys and are sorting before
you derive and send funds to such a P2SH address.
It seems there is scope for further narrowing down how a multisig
scripthash address should be determined - what do people think
Since we only need the sorting for creating the scriptPubKey,
wouldn't it make the most sense to sort it by the way it represented in
that context?
On Thu, Jan 15, 2015 at 2:03 PM, Wladimir wrote:
> On Thu, Jan 15, 2015 at 1:17 AM, Matt Whitlock
> wrote:
> > On Wednesday, 14 January 2015, at 3
4 matches
Mail list logo
