Skip to content
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

Withdrawal TX not accepted by peers. Fee too low. #6493

Closed
systemling32 opened this issue Jan 1, 2023 · 2 comments · Fixed by #6544
Closed

Withdrawal TX not accepted by peers. Fee too low. #6493

systemling32 opened this issue Jan 1, 2023 · 2 comments · Fixed by #6544

Comments

@systemling32
Copy link

Description

I ran into a problem where I tried to withdraw some coins I bought into my hardware wallet. I set the fee rate to 1sat/vbyte as I am not in a rush and want to save on fees. The transaction shows up on the transaction list inside of bisq but in the confirmations column it shows "Seen by 0 peers" forever and the transaction is never mined or viewable on any blockchain explorer.
However the balance I wanted to withdraw is subtracted from my available balance and is not spendable anymore.
Only way to regain these funds is to Delete SPV file and resync.

Version

v1.9.8

Steps to reproduce

In the 'send funds' dialog select a single native segwit UTXO as input, spend the entire UTXO to another native segwit address, check 'Amount includes mining fee' and set a custom withdrawal transaction fee rate of 1sat/vbyte

Expected behaviour

  • Create a transaction with a fee rate of around 1.02sat/vbyte so that it surpasses the minRelayTxFee of 1000sat/kB
  • allow floating point input for fee rate so a user can enter something between 1-2sat/vbyte and create a TX that is not rejected by standard mempool settings
  • If a transactions is not accepted by any peers after a defined period of time scrap it and make the inputs spendable again. Also alert the user of the scrapped TX and the possible reason.

Actual behaviour

Transaction shows up as broadcasted but seen by 0 peers. Funds are marked as spent.
In my testing I calculated that my withdrawal TX hat a fee rate of exactly 1000 sat/kB whereas this post says it needs to be greater than 1000 to be valid.

Device or machine

amd64 Ubuntu

@boring-cyborg
Copy link

boring-cyborg bot commented Jan 1, 2023

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

@ghost
Copy link

ghost commented Jan 2, 2023

Thanks for the detailed write-up. Will get that implemented ASAP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant