Funding page spam creates multiple invoices in LNbits #4

New issue

Closed

opened 2026-01-11 16:22:51 +00:00 by padreug · 1 comment

padreug commented 2026-01-11 16:22:51 +00:00

Owner

Copy link

Bug Description

Repeatedly clicking/refreshing the funding page creates multiple invoices in LNbits instead of reusing an existing unpaid invoice or rate-limiting invoice creation.

Expected Behavior

• Reuse existing unpaid invoice if one already exists for the same amount
• Or implement debouncing/rate-limiting to prevent invoice spam
• Or invalidate previous invoice before creating a new one

Actual Behavior

Each request to the funding page creates a new invoice in LNbits, leading to orphaned unpaid invoices.

Investigation Needed

• Identify where invoice creation is triggered in the funding flow
• Determine if there's existing logic for invoice reuse
• Implement appropriate fix (debounce, reuse, or cleanup)

## Bug Description Repeatedly clicking/refreshing the funding page creates multiple invoices in LNbits instead of reusing an existing unpaid invoice or rate-limiting invoice creation. ## Expected Behavior - Reuse existing unpaid invoice if one already exists for the same amount - Or implement debouncing/rate-limiting to prevent invoice spam - Or invalidate previous invoice before creating a new one ## Actual Behavior Each request to the funding page creates a new invoice in LNbits, leading to orphaned unpaid invoices. ## Investigation Needed - [ ] Identify where invoice creation is triggered in the funding flow - [ ] Determine if there's existing logic for invoice reuse - [ ] Implement appropriate fix (debounce, reuse, or cleanup)

padreug referenced this issue from aiolabs/satmachineadmin 2026-06-01 07:03:27 +00:00

track: legacy aiolabs/lamassu-server issue disposition under Nostr-native architecture (+ future: customer KYC via Nostr DM) #40

padreug commented 2026-06-01 07:11:01 +00:00

Author

Owner

Copy link

Closing as part of aiolabs/lamassu-server archival.

Obsolete under the Nostr-native architecture. Legacy lamassu-server "funding page" (the URL customers visited to pay invoices) is not in our stack at all. Cash-in invoice creation happens on-demand at the bitspire ATM with explicit user flow (insert bill → invoice generated → QR displayed) — no spammable funding URL exists.

Disposition tracked in aiolabs/satmachineadmin#40.

Closing as part of `aiolabs/lamassu-server` archival. **Obsolete under the Nostr-native architecture.** Legacy lamassu-server "funding page" (the URL customers visited to pay invoices) is not in our stack at all. Cash-in invoice creation happens on-demand at the bitspire ATM with explicit user flow (insert bill → invoice generated → QR displayed) — no spammable funding URL exists. Disposition tracked in `aiolabs/satmachineadmin#40`.

padreug closed this issue 2026-06-01 07:11:10 +00:00

padreug referenced this issue from aiolabs/spirekeeper 2026-06-14 07:08:47 +00:00

track: legacy aiolabs/lamassu-server issue disposition under Nostr-native architecture (+ future: customer KYC via Nostr DM) #18

Commenting is not possible because the repository is archived.

No Branch/Tag specified

Branches Tags

main

No results found.

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

aiolabs/lamassu-server#4

No description provided.