-
See the discussion in #859 . Any output type other than v0 P2WPKH currently identifies the output as belonging to the taker or the taker's payee. Further, this presents a non-obvious fingerprinting ri…
-
java.lang.NullPointerException: Attempt to invoke virtual method 'long org.bitcoinj.core.Coin.getValue()' on a null object reference
at org.bitcoinj.core.Transaction.hashForWitnessSignature(T…
-
```
/**
* A P2PKH witness example for estimating txn size before signing transaction.
*/
const P2WPKH_WITNESS_EXAMPLE: Witness = {
scripts: [
{ hex: '304402200000000000000000000000000000…
-
when import (with a privatekey)p2sh or lagacy(any type) privatekey wallet is not sendable to any one .
bug here!
open general / enable adavanced mode
add now / select opticalbitcoin/it shows 3 opt…
ghost updated
2 years ago
-
Affects chains which support SegWit, but not bech32 address encoding. Right now the default behavior is b58 encoding the Segwit pk_script. This is just wrong. Instead, we should have it make nested P2…
-
**Describe the bug**
BIP141 address generation does not match Ian Coleman tool and several others. https://iancoleman.io/bip39/
**To Reproduce**
zpub = _generated _zpub__
pybtc.Address(key=zpub…
-
Currently when somebody requests orderbook, he will receive responses from both sw (p2sh-p2wpkh) and sw0 (native segwit p2wpkh) yield generators and then do filtering at the client side. I propose we …
-
Currently, `CreateDescriptors` creates `descriptors` based on the path and script type specified by the user.
This is probably not as useful as having the ability to create a descriptor based on a st…
-
BIP141 ([https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki](url)) describes adding a new structure called "witnesses" to "segregate" script and signature data from the rest of the transac…
-
At present, it seems that a given HierarchicalKey instance can only be encoded as a single address type, eg p2pkh, p2wpkh, p2sh-p2wpkh, etc. AddressCreator takes no constructor arguments and internal…