Cryp Toon

It could be a setting requiring a minimal number of confirmations. Also you could check the logs if you see an error or warning. If that doesn't solve the problem...

Sounds like one of the service providers is returning wrong results, I will run some checks to see if I can reproduce anything. If you have this issue again, please...

It seems the wallet was not able to send a correct transaction, or the transaction was not accepted by the network so it remains unconfirmed in the wallet. It's hard...

Hi @arshbot, I wasn't aware of this, so thanks for notifying. I need to delve into it in a little more but as far as I understand now the most...

Yes would be nice to add but it's not on my planning yet. I might look at it later, and of course anyone is free to create a pull request.

Could you check if the problem persists in the new version of the library (0.6.0)? I fixed a couple of issues with some service providers.

You can try to install the fastecdsa library seperately and see if that works or if any error pops up. But you can ignore this warning if you are not...

For some tricks on how to get fastecdsa working on Windows see https://github.com/AntonKueltz/fastecdsa/issues/11

That is a good point, I understand the problem with conflicting dependencies. But the library is extensively tested with those specific versions, and it's not possible to test for large...

In commit https://github.com/1200wd/bitcoinlib/commit/8324ef3d2c6d28ebaca15fed480cf205e29c0526 minimum package requirements are used instead of fixed version numbers. Tests with the first and latest version for are packages are succesful. Does this work for you?