Bjarne Magnussen
Bjarne Magnussen
Are those issues mostly related to sending out transactions, or is it equally problematic to receive transaction information over Tor? Blockstream.info has an onion site for its API and so...
Thanks for the info!
You must run bitcoin core with the configuration parameter `rpcallowip=` set to its host ip.
Unfortunately not supported as it requires BIP-32 to be implemented.
A PR would be fantastic! I started working on implementing it but never found the time to finish it. I could share it with you if you are interested in...
I only have some snippets for the BIP32 part of this issue. I was working on a BIP32 library implementation. It was forked from `bip32utils` (which now does not exist...
I think initially supporting BIP39 is very beneficial as it allows for better interoperability. Of course later the support for Electrum's own seed system could always be added.
It would then be interesting to see how `bip32utils` performs with the changes above that make use of `coincurve` instead, which is using CFFI as binding to C.
There is no function for it, however this can be calculated easily: ```python import bit k = bit.PrivateKeyTestnet() unconfirmed_balance = sum(u.amount for u in k.get_unspents() if u.confirmations==0) ```
This is definitely a problem with the API services -- and may only be for testnet. I can confirm that the problem is with `BitpayAPI`, which is the first one...