Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

When bumping transmission with an unpaid invoice(s), cancel the unpaid invoice(s) and put total amount in new "bumped" lightning invoice.

Open
  • Is something wrong?
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, payments

Research direction

Start by tracing the transmission-bump flow and how it handles unpaid invoices. Verify that the original invoice is cancelled and that the replacement Lightning invoice uses the full bumped amount rather than only the difference, using the example amounts in the issue as the completion criteria.

Written by the indexing model from the issue text.

Description

When an invoice is unpaid, and users bump, the original invoice should be cancelled, and the new invoice should include the new amount (not the difference between the original and bumped rate).

For example, user submits 1kb transmission for 50 mSats per byte (i.e. 50,000 mSat invoice). User then bumps the transmission to 100 mSats per byte. The old invoice would be cancelled and the new invoice from bumping would be 100,000 mSats.

Dominant language
Python
Stars
38
Forks
9
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Blockstream/satellite-api

All issues in Blockstream/satellite-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.