-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitcash not creating valid transactions despite returning a TxID #134
Comments
I'm unable to reproduce the bug. I tried to send a tx, and it was sent (and seen in the blockexplorer). |
I am also able to send transactions without issues on my end: The transaction is found on Blockchair: https://blockchair.com/bitcoin-cash/transaction/3cb93f1ee2424d9cf409363cfa0732861d83eac44c57765f4a64a648324ce12b Do you use a custom Node endpoint @revoxhere? |
No, I don't think I'm using any custom endpoints. Haven't changed anything in the source. Is there any way I can prevent this from happening again? I thought I could somehow check if the generated TXID is valid... Thanks for your input and this awesome library! |
Hmm that's strange. Are you able to share a private key that results in this failure? Make sure there is no money in it and that you will never use it again. If you are unable to share that, maybe you can share how it was generated so I can try to reproduce? I understand all this can be sensitive information so please only share if it does not compromise your security. |
Hello there. I'm having a problem with BitCash not sending funds properly, minimal example:
The generated TxID, when explored in a blockchain explorer is not valid and the balance does not change, yet the transaction does not fail.
This is happening both on version
1.0.0
and1.0.1
(used in the example). It happens with any amount and receiving wallet.I really like this library and been using it for the past two years or so, but it seems to not work for the past few days or weeks. Maybe someone can help me troubleshoot this?
Thanks in advance.
The text was updated successfully, but these errors were encountered: