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

wallet: unnecessary coinbase chain position assert #1833

Conversation

torkelrogstad
Copy link
Contributor

Description

Removes an unneeded assertion from preselect_utxos. I'm not precisely sure how I triggered this, but I encountered this while syncing a rather large signet wallet containing lots of freshly generated UTXOs.

This assertion is not needed, as unconfirmed coinbase TXs get filtered away in the branch below anyways.

Checklists

All Submissions:

  • I've signed all my commits
  • I followed the contribution guidelines
  • I ran cargo fmt and cargo clippy before committing

Bugfixes:

  • This pull request breaks the existing API
  • I've added tests to reproduce the issue which are now passing
  • I'm linking the issue being fixed by this PR

This assertion is not needed, as unconfirmed coinbase TXs get filtered
away in the branch below anyways.
@evanlinjin
Copy link
Member

I'm not precisely sure how I triggered this, but I encountered this while syncing a rather large signet wallet containing lots of freshly generated UTXOs.

The fact that there is an unconfirmed coinbase tx signals that there is a bug.

Would you mind describing the conditions that triggered this?

I.e.

  • What chain source you used. bdk_electrum, bdk_esplora, something custom, etc.
  • whether you did a full-scan request or a sync request (if electrum/esplora) before trying to create tx.
  • Wallet state before the sync.

@torkelrogstad
Copy link
Contributor Author

This might actually be fixed by this recent PR: #1830

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 this pull request may close these issues.

2 participants