Antoine Poinsot
Antoine Poinsot
@pythcoiner for what it's worth Ledger only check that the key part of the internal xpub is the BIP341 NUMS, it does not derive the chaincode. But you are right...
You can have duplicate xpubs without having duplicate keys in the scripts. An (uninteresting) example is `tr(_,{pk(xpubA/0/*),pk(xpubA/1/*)})`.
> I see this constraint in the Liana code as well. So we can't do `tr(unspendable, {pk(key),sha256(h)})`? This is a Liana-specific constraint which i don't think should apply to this...
> What would be the benefit of such a fragment for the "dumb" parser, vs just using the computed unspendable xpub with the NUMS public key as currently done? Compatibility...
> What about having P2P-seeds, an alternative to DNS-seeds I guess the biggest drawback with this is how bootstrapping nodes will actually connect to this "P2P-seeds" instead of leveraging the...
Besides the load, which can be dealt with by having a large number of seeds, i wonder how much getting rid of the DNS caching impacts "privacy", loosely defined. Of...
If i remember correctly bip352 mandate to use key path spend for Taproot. I'm not even sure it can do P2WSH? In this case it would only be possible for...
Why? As mentioned in OP it would only delay such a soft fork if there is a concern that miners could produce an invalid block template, and we can choose...
> By normal circumstance you mean when nobody else on the network is attempting a timewarp attack? But what if there is one? Sure, a timewarp attack is not normal...
Yes. I intend to rebase on top of it once it's merged.