-
https://github.com/bitcoin/bips/blob/master/bip-0069.mediawiki
https://github.com/bitcoinjs/bip69
-
Normal wallets should basically always apply bip69 for transactions they create.
The downside of this here is that OP_RETURN outputs would be the zero'th output and you'd burn your identity.
I s…
-
Trezor Suite is going to [abandon](https://github.com/trezor/trezor-suite/issues/10765) the use of [BIP-69](https://github.com/bitcoin/bips/blob/master/bip-0069.mediawiki) and instead just randomize t…
-
See https://github.com/bitcoinjs/bolt11/issues/5#issuecomment-381479499
Travis support should mimic bitcoinjs-lib which has already been updated.
```
bech32
bip174
bip21
bip32
bip32-utils
…
-
At some point, it would be helpful to clarify what we mean by BIP 62 compliance.
The BIP has been withdrawn and parts of it may are probably not applicable to the privacy goal we're attempting to mea…
-
Under blockchain observer, the relevant attack is:
> Link outputs in a transaction to a single entity by detecting which output is a change output
The current countermeasure listed under this is:
>…
-
Useful for some of us who may need ins and outs to have specific slots, like when adding covenants to unsigned TX, or when spending an authchain together with a BCMR OP_RETURN - in which case we want …
-
The selectUTXO function produces occasionally ``dust`` outputs.
This is how I use the selectUTXO function:
``` ts
const selected = selectUTXO(userUTXOs, psbtOutputs, 'default', {
changeAdd…
-
In the ``EstimatorOpts`` type, the ``dust`` field is a type of *number*, but the default hardcoded value is *bigint*. So there is a mismatch, and an error is being thrown.
```ts
private dust = 1…
-
### Description
Add BIP69 transaction feature flag
### Problem to be solved
BIP69 (deterministic lexicographical sorting of transaction inputs and outputs) ensures private information (e.g. c…