You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Im unable to get testnet extended key (tpriv and tpub), only xpriv and xpub. Is this by design or am I missing something?
let keychain = mnemonic.keychain.bitcoinTestnet.derivedKeychain(withPath: "m/44'/0'/0'/0") let xpub = keychain?.bitcoinTestnet.extendedPublicKey let xpriv = keychain?.bitcoinTestnet.extendedPrivateKey
Thanks in advanced. I am trying to test that the xpriv receiving funds from watch only addresses actually receive the funds, without using real Bitcoin. It is proving a challenge. Any tips would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Fonta1n3
changed the title
testnet extended keys?
testnet extended keys/watch only testing?
Jun 13, 2018
Uh-oh, seems like it's a bug. I looked in the code and there are at least couple of places where we should set correct .network property on a keychain. Meanwhile, you can workaround the issue by setting keychain.network = BTCNetwork.testnet after you've derived your keychain. When these bugs are fixed, that would be an unnecessary no-op.
Any updates on this? Using this library again for seed creation/derivation and need to test with tpub and still have the same issue. Have to hardcode a tpub for now which is not great.
Im unable to get testnet extended key (tpriv and tpub), only xpriv and xpub. Is this by design or am I missing something?
let keychain = mnemonic.keychain.bitcoinTestnet.derivedKeychain(withPath: "m/44'/0'/0'/0") let xpub = keychain?.bitcoinTestnet.extendedPublicKey let xpriv = keychain?.bitcoinTestnet.extendedPrivateKey
Thanks in advanced. I am trying to test that the xpriv receiving funds from watch only addresses actually receive the funds, without using real Bitcoin. It is proving a challenge. Any tips would be greatly appreciated.
The text was updated successfully, but these errors were encountered: