Skip to content

fix: app not using Blocktank fees #2576

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.

Sign up for GitHub

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

Jump to bottom
Closed
jvsena42 wants to merge 6 commits into from
Closed

fix: app not using Blocktank fees #2576

jvsena42 wants to merge 6 commits into from

Conversation

@jvsena42
Copy link
Member

@jvsena42 jvsena42 commented Nov 11, 2025 •
edited
Loading

Description

App was not using Blocktank on-chain fees for two reasons:

  1. It was prioritizing mempool.space over Blocktank
  2. If both fetch fails, getFees was using hardcoded fees instead of cached ones

Linked Issues/Tasks

Slack thread

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactoring (improving code without creating new functionality)

Tests

  • Detox test
  • Unit test
  • No test

Screenshot / Video

Insert relevant screenshot / recording

QA Notes

TODO

@jvsena42 jvsena42 self-assigned this Nov 11, 2025
@jvsena42 jvsena42 changed the title fix: outdated on-chain fee estimates fix: stale lightning routing fees Nov 11, 2025
@jvsena42 jvsena42 changed the title fix: stale lightning routing fees fix: app not using Blocktank routing fees Nov 12, 2025
@jvsena42 jvsena42 changed the title fix: app not using Blocktank routing fees fix: app not using Blocktan fees Nov 12, 2025
@jvsena42 jvsena42 changed the title fix: app not using Blocktan fees fix: app not using Blocktank fees Nov 12, 2025
@jvsena42 jvsena42 closed this Nov 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@jvsena42 jvsena42

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jvsena42