LN
← All projectsLNbits

LNbits

Self-hosted Lightning wallet, accounts, payment API, and extension platform supporting multiple funding sources.

BitcoinLightning NetworkPayment infrastructureActive incident
Repository coverage

598 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

51security candidates144second-pass queue196AI analyses
63commits · 30 days
141commits · 60 days
291commits · 180 days
547commits · 365 days
Backfill bands
Nov 8 → May 12291 seen16 candidatesComplete
May 12 → Sep 9146 seen12 candidatesComplete
Sep 9 → Oct 932 seen6 candidatesComplete
Oct 9 → Nov 899 seen10 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

71/100 average clarity
171Strong · 80–100
341Adequate · 60–79
80Thin · 40–59
6Opaque · 0–39
2security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Vlad Stan1372758564
Arc631127366
Riccardo Balbo403140
dni ⚡185558069
Tiago Vasconcelos38311068
monasco622053
Bitkarrot624085
satcat21111075
dependabot[bot]6400093
blackcoffeexbt1005065
Nathan Day904086
Bartok802081
Analysis record

Published AI watches

Last scanned 47 minutes ago

Low 41 AI analysisMessage 73 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat (wasm): Adds csv/print to wasm iframes, core theme passing, optional unhashed description, scoped invoice status, fiat checkout and browser storage (#4328)

This commit adds several new features to LNbits' WebAssembly (WASM) extension system. It introduces ways for extensions to: check invoice status, refresh payment status, create fiat checkout invoices, store small amounts of data in the bro…

Untrusted `extension_context` dictionary replaced by frozen typed model `PaymentExtensionContext` with required `extension_id`, `owner_id`, `wallet_id`, and optional `source_id`.New `wallet.invoice_status` method enforces strict binding checks (extension, owner, wallet, source) before returning only `paid/pending/failed/amount-msat`; rejects legacy/unbound invoices.New `wallet.refresh_payment` requires authentication, wallet ownership or shared-wallet VIEW_PAYMENTS permission, and scopes payment lookup by wallet; hides backend error details.
df3a180aby Arc+1919−8322 files
No security note in commit
Moderate 63 AI analysisMessage 58 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix[8c7f]: reject SSO for accounts with passwords (#4347)

This update blocks users from logging into password-protected accounts through single sign-on (SSO), such as 'Login with GitHub'. Before this change, an attacker who knew or guessed a victim's email address could potentially use an SSO pro…

Authentication bypass mitigation: SSO can no longer authenticate accounts that also have local passwordsAccount takeover risk reduction: blocks an external identity provider from overriding a password-protected accountState preservation: password hash and email_verified flag remain unchanged on rejection
b1d22089by Vlad Stan+70−23 files
No security note in commit
Low 44 AI analysisMessage 58 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix[8c7f]: keep unrecorded Core Lightning payments pending (#4345)

This commit changes how LNbits interprets a missing Core Lightning payment record. Previously, if no payment record existed, LNbits marked the payment as failed. Now it marks it as still pending, because a payment that is currently being s…

Change in payment state machine: empty result now treated as pending rather than failedPotential race condition between payment initiation and status pollingRisk of duplicate payment attempts if pending status leads to retries
49755d33by Vlad Stan+2−21 file
No security note in commit
High 81 AI analysisMessage 75 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: reject user ID authentication for password accounts (#4340)

This commit fixes an authentication bypass in LNbits. Previously, an account that had been created without a password could still be logged into using only the user ID even after a password was later added. An attacker who knew (or guessed…

Authentication bypass via user ID for password-protected accountsStale authentication cache could grant access after password upgradeNew guard `check_passwordless_account` enforces password requirement
db9563d2by Vlad Stan+196−448 files
Vendor flagged security relevance
Moderate 67 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: respect shared wallet permissions for payment updates (#4338)

This commit fixes a permission bug in LNbits where users of shared wallets could update or settle/cancel payments even when they only had view-only access. It also adds a check so that settle/cancel actions only work on special 'hold invoi…

Access-control bypass fix for shared wallet payment updatesNew permission check can_update_payments() tied to shared wallet receive/send permissionsNew hold_invoice guard on settle/cancel endpoints
d718f9aeby Vlad Stan+154−64 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

chore: remove extension builder from core (#4331)

This commit completely removes the 'Extension Builder' feature from LNbits core. It deletes the backend code that generated extensions from templates, the API endpoints, the web UI pages, and related settings. There is no bug being fixed a…

Removal of a code-generation feature that used Jinja2 with autoescape=False (bandit S701 was previously suppressed for this file)Removal of an endpoint that allowed admins to build, deploy, and activate extensions from user-supplied JSON configurationReduction of extension installation attack surface by removing the builder manifest source and preview file-serving route
c8d47013by Vlad Stan+14−334535 files
No security note in commit
Low 49 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: disable paid reviews (#4325)

This update turns off a default paid-extension review service in LNbits. It stops the wallet from automatically contacting a third-party payment/review server when it lists or updates extensions, and resets the default review URL to empty.…

Default third-party review/payment URL removedMigration forcibly resets stored review URL to emptyBackground extension update/install no longer queries remote pay_link for pricing
77cc2276by Vlad Stan+208−1313 files
No security note in commit
Moderate 60 AI analysisMessage 55 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: packaging/builds (#4319)

This commit fixes a packaging/build issue in LNbits, but the code changes also harden how sensitive funding-source settings (wallet seeds, API keys, macaroons) are exposed and edited through the admin web interface. Previously, non-super a…

Authorization boundary tightened: funding-source credentials restricted to superuser in API and UISeed-integrity check added: configured mnemonic must match persisted seed.dat before settings are writtenBackup confirmation reset when funding seed changes, preventing silent wallet substitution
fe2b0a98by Arc+913−6918 files
No security note in commit
Critical 100 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat: Add superuser action to reset all wallet keys (#4320)

This commit adds a recovery feature that lets the LNbits superuser instantly replace every wallet's secret keys, including keys for deleted wallets, and clear any cached copies of the old keys. The vendor says this is needed because of a r…

Vendor describes the change as a recovery control for a security incident involving exposed wallet credentialsVendor states all versions before 1.7.0 are affected and funds are at risk of theftNew superuser-only endpoint can rotate every wallet's admin and invoice keys, including deleted wallets
45a25b24by Vlad Stan+523−58 files
Vendor flagged security relevance
Moderate 63 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat: Automatically update extensions on startup and on a schedule (#4314)

This commit adds an automatic extension update feature to LNbits. By default, it checks for and installs newer versions of installed extensions when the server starts, and can repeat that check every 24 hours. Because extensions are downlo…

Automatic download and execution of third-party code is enabled by defaultUpdate source is the extension's configured source_repo, not a vendor-curated storeNo code signature or hash verification is visible in the diff beyond existing archive validation helpers
a16d7752by Vlad Stan+836−1511 files
No security note in commit
Critical 89 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: harden SSRF checks and use explicit local LNURL route opt-ins (#4313)

This commit is a security hardening patch for LNbits, a Bitcoin Lightning wallet platform. It fixes weaknesses in the server's outgoing web-request protections (SSRF, or Server-Side Request Forgery) that could let an attacker trick the LNb…

SSRF hardening: multicast, IPv6 transition/embedded addresses, and EC2 IPv6 metadata endpoint blockedLocal LNURL routing moved from hard-coded regex allow-list to explicit per-route openapi_extra opt-inBackslash path traversal blocked in private HTTP endpoint checks
fc5e0b60by Arc+168−408 files
Vendor flagged security relevance
Critical 90 AI analysisMessage 85 · Strong
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: centralize SSRF protection and block self-targeted requests (#4310)

This is a major security patch for LNbits released after a November incident. It fixes two broad weaknesses: attackers could trick the server into making requests to itself or to internal/cloud services (SSRF), and new user accounts could …

New centralized SafeHttpClient with DNS pinning, redirect limits, and destination validationNew outbound.py blocks requests to the instance hostname and locally assigned/supplied IP addressesSSRF protection applied to LNURL, NIP-05, webhooks, WASM extension HTTP, and WebSockets
7a176c59by Arc+2076−30332 files
Vendor flagged security relevance
Low 35 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix(corelightningrest): compute payment status fee as sent minus amount (#4300)

This commit fixes a bug in how LNbits calculates the fee for a completed Core Lightning REST payment. The old code incorrectly subtracted a negative 'amount sent' value, which produced the wrong fee. The fix changes the formula so the fee …

Incorrect arithmetic in financial/fee calculationTest fixture updated to match corrected sign conventionWallet backend payment status logic changed
45a8704fby Amartya Vikram Singh+2−22 files
No security note in commit
Moderate 52 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: ignore failed payments in daily withdraw limit (#4297)

This commit fixes a bug in LNbits where failed outgoing payments were incorrectly counted against a wallet's daily withdrawal limit. Because failed payments never actually moved money out of the wallet, counting them could wrongly block le…

Business-logic flaw in access-control / spending limitIncorrect state filter on financial transaction queryDenial-of-service-like effect: legitimate withdrawals blocked by stale failed payment records
206477d4by Amartya Vikram Singh+54−02 files
No security note in commit
Low 34 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix(lnpay): return checking_id from create_invoice (#4295)

This commit fixes a bug in the LNPay wallet integration where newly created Lightning invoices were not returning their internal tracking ID ('checking_id'). Without this ID, LNbits could not reliably match future payment updates to the co…

Missing correlation identifier in payment responsePotential invoice state desynchronization between LNbits and LNPay backendRegression test added for payment identifier handling
918b38dcby Amartya Vikram Singh+22−02 files
No security note in commit
Moderate 60 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: prevent duplicate BOLT12 offer payments on retry (#4287)

This commit fixes a bug where retrying a BOLT12 offer payment could accidentally pay the same offer twice. It adds an idempotency check using an external_id so that retries return the original payment instead of creating a duplicate, while…

Duplicate payment prevention for BOLT12 offersIdempotency keyed on wallet_id + external_idConflict detection when external_id reused with different payment details
ea2686d1by Vlad Stan+426−89 files
No security note in commit
High 79 AI analysisMessage 55 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: mempool urls (#4286)

This commit fixes a security gap in LNbits' on-chain (Bitcoin) wallet feature. Previously, a wallet owner could point their wallet at any Mempool-style block explorer URL, including internal or attacker-controlled addresses. The server wou…

Server-Side Request Forgery (SSRF) mitigation: unapproved mempool endpoints are rejected before httpx.AsyncClient is instantiatedOpen redirect / redirect-to-attacker mitigation: follow_redirects=False on mempool requestsInput validation: Pydantic validator strips paths, rejects credentials, fragments, query strings, control chars, backslashes, and invalid ports
f9dd17f3by Vlad Stan+354−2212 files
Vendor flagged security relevance
Low 45 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: payment ws notifications (#4282)

This commit fixes how LNbits notifies the user interface about incoming Lightning payments. Previously, the same paid invoice could be processed and announced multiple times, causing duplicate or confusing wallet notifications. The change …

Race condition in payment status update between polling loop and paid-invoice streamDuplicate WebSocket notifications for the same settled invoiceRefactoring to atomic DB-lock guarded update of incoming payment status
aa041306by Vlad Stan+388−297 files
No security note in commit
Low 39 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

chore: bump to pydantic 2 (#4253)

This is a large dependency upgrade from Pydantic 1 to Pydantic 2 across the LNbits project. Most changes are mechanical renames (e.g., dict() to model_dump(), parse_obj() to model_validate()). A few small functional changes are mixed in: i…

Dependency major-version upgrade (Pydantic 1 -> 2) with broad validation behavior changesRemoval of Pydantic v1 duplicate-validator cache workaround in extension route registrationJWT account resolution reordered to prefer 'usr' claim over 'sub' claim
2ab7662eby Vlad Stan+1548−753119 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat: make onchain dialog more readeable (#4269)

This commit is a user-interface redesign of the on-chain Bitcoin receive dialog. It splits the dialog into two screens: one to enter an amount and note, and another to display the QR code. The changes are purely cosmetic and do not alter h…

0e0ee6edby Tiago Vasconcelos+144−804 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

AI review queuedfeat: first macos signed build (#4175)by Vlad Stan · 1bd801c9 · Sep 22, 2026 · 31 filesMessage 80 · StrongInformational 15Details
Commit message · Vlad Stan

feat: first macos signed build (#4175)

Co-authored-by: Arc <33088785+arcbtc@users.noreply.github.com>

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit adds the first Apple Developer ID signed and notarized macOS desktop build pipeline for LNbits. It is a feature commit introducing packaging scripts, GitHub Actions workflows, code-signing helpers, entitlements, DMG creation, smoke tests, and documentation. There is no vulnerability fix or security patch in the diff; the changes are purely about producing a trusted macOS app bundle.

Security candidatefix: paid install QR code never shown for WASM extensions with permissions (#4195)by Bitkarrot · 6e27984f · Sep 21, 2026 · 2 filesMessage 85 · StrongInformational 16Details
Commit message · Bitkarrot

fix: paid install QR code never shown for WASM extensions with permissions (#4195)

Co-authored-by: bitkarrot <bitkarrot@users.noreply.github.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege state
AI analysis · Informational 16/100

This commit fixes a UI bug where the QR code for paying to install a 'WASM' extension was never shown if the extension required special permissions. The change is a one-line logic fix in the JavaScript that controls the extension installation dialog. It is a functional bug fix rather than a security vulnerability, and there is no evidence in the commit of malicious behavior or a disclosed security issue.

Security candidatefeat: asset refactor, phoenixd/sparkl2 included, add dmg (#4167)by Arc · bdd0aa96 · Sep 17, 2026 · 22 filesMessage 70 · AdequateInformational 24Details
Commit message · Arc

feat: asset refactor, phoenixd/sparkl2 included, add dmg (#4167)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Informational 24/100

This commit is a feature release for the LNbits desktop packaging system. It adds the ability to bundle external Bitcoin/Lightning 'funding' programs (Spark L2 and Phoenixd) directly into the desktop app, adds macOS DMG packaging, and makes a small fix so failed payments report their actual error message. Most of the changes are build scripts, packaging workflows, and tests. There is no obvious remote attack introduced, but the new code does download and execute external binaries, manage wallet seeds, and run local daemons, which increases the app's security surface area.

AI review queuedDelete cliche (#4118)by Vlad Stan · 3e62f681 · Sep 14, 2026 · 8 filesMessage 36 · OpaqueInformational 17Details
Commit message · Vlad Stan

Delete cliche (#4118)

36/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit removes support for an old Lightning wallet backend called 'Cliche' from the LNbits project. It deletes the dedicated code file, removes configuration options, and updates documentation and the admin UI so Cliche no longer appears as a funding source. There is no indication in the commit that this fixes a security vulnerability; it appears to be routine cleanup of an unmaintained feature.

Security candidateMerge commit from forkby monasco · 69bcd391 · Sep 14, 2026 · 2 filesMessage 28 · OpaqueLow 46Details
Commit message · monasco

Merge commit from fork

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication pathmerge-commit duplicate discount
AI analysis · Low 46/100

This commit adds missing safety checks to two password-related features in LNbits. It now verifies that the new password and its confirmation match, and that chosen usernames follow the allowed format. These are defensive hardening changes rather than fixes for a known active attack, but they close gaps that could let a user accidentally (or via a manipulated client) set a mismatched password or an invalid username during account setup or password change.

AI review queuedCustom memo for Credit/Debit flows. (#4162)by DrShift · 6fb8b97a · Sep 14, 2026 · 13 filesMessage 68 · AdequateInformational 21Details
Commit message · DrShift

Custom memo for Credit/Debit flows. (#4162)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 21/100

This commit lets administrators add a custom note (memo) when crediting or debiting a wallet, instead of always using the fixed labels 'Admin credit' or 'Admin debit'. It also fixes a small display bug where the balance shown in admin notifications was not updated to reflect the new amount. The change is a user-facing feature improvement, not a security fix, and does not appear to introduce a meaningful vulnerability.

AI review queuedfix: fiat wallet type (#4165)by Arc · afb343de · Sep 11, 2026 · 20 filesMessage 65 · AdequateLow 45Details
Commit message · Arc

fix: fiat wallet type (#4165)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 45/100

This commit introduces a new 'fiat wallet' type in LNbits, a Bitcoin Lightning wallet platform. It adds controls so fiat wallets can only receive money (not send it), restricts who can create them, and excludes their balances from total balance calculations. The changes are mostly defensive: they prevent fiat wallets from being used to spend funds they don't actually hold in Lightning. There is no clear evidence this fixes an active security breach, but it closes a design gap where a fiat-denominated wallet might otherwise be treated like a real Lightning wallet.

AI review queuedfix(nwc): resolve in-flight request futures when relay disconnects (#4161)by Nathan Day · ac153ef1 · Sep 10, 2026 · 1 fileMessage 93 · StrongLow 42Details
Commit message · Nathan Day

fix(nwc): resolve in-flight request futures when relay disconnects (#4161)

Co-authored-by: dadofsambonzuki <dadofsambonzuki@noemail.com>
Co-authored-by: Arc <33088785+arcbtc@users.noreply.github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 42/100

This change fixes a bug in LNbits' Nostr Wallet Connect (NWC) integration where pending payment or invoice requests could hang forever if the relay connection dropped. The fix ensures these waiting requests are properly marked as failed with a timeout when the connection is down, instead of leaving them stuck until the server is restarted. It is a reliability/availability fix rather than a direct theft-of-funds vulnerability, but the hang could be abused to deny service or confuse automated services.

AI review queuedfix(nwc): prevent false payment failures on NWC provider sync delay (#4066)by Nathan Day · 2dbfca9f · Sep 8, 2026 · 4 filesMessage 85 · StrongModerate 57Details
Commit message · Nathan Day

fix(nwc): prevent false payment failures on NWC provider sync delay (#4066)

Co-authored-by: dadofsambonzuki <dadofsambonzuki@noemail.com>
Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 57/100

This commit fixes a bug in LNbits' NWC (Nostr Wallet Connect) wallet integration where payments could be incorrectly marked as failed due to delays in the NWC provider updating its records. The fix makes the wallet wait longer and use cached proof of payment before declaring a payment failed. It also adds better handling for missing fee information and lost payment responses. The bug could have caused users' successful payments to be reported as failed, potentially leading to duplicate payments or accounting errors, but it does not appear to allow an external attacker to steal funds directly.

AI review queuedchore: update lock (#4157)by Arc · 5ca442bb · Sep 8, 2026 · 5 filesMessage 55 · ThinInformational 17Details
Commit message · Arc

chore: update lock (#4157)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This is a routine dependency lock-file update for the LNbits project. It bumps versions of several third-party libraries (such as wasmtime, nostr-sdk, bitarray, cffi, certifi, charset-normalizer, coverage, and pyln-client) and makes one tiny code change in the Cliche wallet error message to use safer string quoting. There is no direct evidence in the commit that this fixes a known security vulnerability, and the project describes it only as a chore. The small code change improves error-message formatting but does not, by itself, represent a security fix.

AI review queuedfix(wallet): handle ?lightning= urls and restore LNURL-pay payer details (#4122)by Anton Kovalenko · bf341740 · Sep 7, 2026 · 5 filesMessage 93 · StrongLow 31Details
Commit message · Anton Kovalenko

fix(wallet): handle ?lightning= urls and restore LNURL-pay payer details (#4122)

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>
Co-authored-by: Arc <ben@arc.wales>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 31/100

This commit fixes two wallet bugs in LNbits: it now correctly handles Bitcoin Lightning URLs that use a '?lightning=' query parameter (common when scanning QR codes from websites), and it restores payer details when paying via LNURL-pay. The changes are mostly frontend JavaScript plus a small backend Blink wallet test update. There is no clear security vulnerability being patched; it reads as a normal bug-fix for user-facing payment flows.

AI review queuedBlink funding source: Reduce payment-status polling, add caching and backoff (#4042)by Nathan Day · 30d94046 · Sep 7, 2026 · 2 filesMessage 81 · StrongLow 27Details
Commit message · Nathan Day

Blink funding source: Reduce payment-status polling, add caching and backoff (#4042)

Co-authored-by: dadofsambonzuki <dadofsambonzuki@noemail.com>
Co-authored-by: Arc <33088785+arcbtc@users.noreply.github.com>

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 27/100

This commit rewrites how LNbits talks to the Blink Bitcoin Lightning wallet provider. It adds a rate limiter (to avoid hammering Blink's API), caches payment-status answers, spaces out repeated status checks with increasing delays, and fixes a bug where a failed BOLT11 invoice decode could crash a payment. The changes are defensive: they reduce API load and make payment handling more robust, but they also introduce new concurrency and caching logic that could hide edge-case bugs.

Security candidatefix: wallet details (#4153)by Vlad Stan · c888d1f0 · Sep 7, 2026 · 9 filesMessage 55 · ThinModerate 64Details
Commit message · Vlad Stan

fix: wallet details (#4153)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Moderate 64/100

This commit fixes a privacy and authorization issue in LNbits where wallet secret keys (admin and invoice keys) were being returned to API clients even when the client was authenticated with a restricted access-control token that only had read permission. The change introduces a new helper that masks those keys unless the current request has write access to the endpoint, and applies it to several wallet-listing API responses. It also adds tests confirming the masking behavior.

AI review queuedfeat: phoenixd node page (#4146)by Arc · c52333c1 · Sep 7, 2026 · 12 filesMessage 65 · AdequateLow 33Details
Commit message · Arc

feat: phoenixd node page (#4146)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 33/100

This commit adds a new admin/superuser page for managing a Phoenixd Lightning wallet backend in LNbits. It introduces API endpoints that let authorized administrators view node status, estimate liquidity fees, get receive addresses, and—only for the superuser—perform on-chain withdrawals, cooperative channel closures, fee bumps, and CSV exports. The code is a feature addition rather than a bug fix, and the privileged actions are gated behind existing admin/superuser decorators. There is no direct evidence in the commit of a security vulnerability, but any code that can move funds or close channels warrants careful review and hardening.

Security candidatefix: settings ui refector + blockexplorer tweaks (#4144)by Arc · e66236bf · Sep 7, 2026 · 38 filesMessage 85 · StrongLow 27Details
Commit message · Arc

fix: settings ui refector + blockexplorer tweaks (#4144)

Co-authored-by: Tiago Vasconcelos <talvasconcelos@gmail.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy path
AI analysis · Low 27/100

This commit refactors the LNbits settings user interface and makes small adjustments to the built-in Bitcoin block explorer. It adds a new paginated API endpoint for listing transactions inside a block, splits public and authenticated block explorer pages, and introduces a new setting to show the block explorer in the user menu. It also changes the default maximum number of assets per user from 1 to 10. There is no clear security fix or vulnerability being patched in the visible code changes.

Security candidatefeat: UI for credetials update threshold (#4136)by Vlad Stan · ee74ed29 · Aug 31, 2026 · 3 filesMessage 65 · AdequateLow 45Details
Commit message · Vlad Stan

feat: UI for credetials update threshold (#4136)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 45/100

This commit adds a user-interface setting for a 'credentials update threshold' and, more importantly, fixes a security gap in the authentication cache. Previously, when a user's login was cached for performance, API-token permissions were not re-checked on every request. That meant a cached session could continue using an API token even after the token had been deleted or its permissions had been reduced. The patch now re-validates the API token's permissions on each cached request and adds tests to prove it.

Security candidatefix: forward ip (#4132)by Vlad Stan · 4109aa1f · Aug 25, 2026 · 33 filesMessage 48 · ThinHigh 75Details
Commit message · Vlad Stan

fix: forward ip (#4132)

48/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · High 75/100

This commit is a large security-focused patch for LNbits. It replaces the external library's LNURL handling with custom code that validates URLs, blocks private/internal IP addresses by default, limits redirects, and prevents credential leaks. It also hardens webhooks, login throttling, database backup commands, callback URL checks, and fixes Stripe/PayPal currency handling. The default authentication method is changed to username+password only, removing the weaker 'user-id-only' default.

AI review queuedfeat: adds blockexplorer api, frontend via electrum (#4020)by dni ⚡ · 5592a602 · Aug 4, 2026 · 40 filesMessage 70 · AdequateLow 27Details
Commit message · dni ⚡

feat: adds blockexplorer api, frontend via electrum (#4020)

Co-authored-by: alan <alan@lnbits.com>

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Low 27/100

This commit adds a new optional Bitcoin block explorer feature to LNbits. It introduces settings, backend services, REST API endpoints, WebSocket feeds, and frontend pages. The feature is disabled by default and can be restricted to authenticated users. The supplied diff does not show an obvious security vulnerability, but it is a large new surface area that touches authentication, external network calls, and WebSocket handling, so it warrants normal review rather than being treated as a confirmed security fix or flaw.

AI review queuedfix: probe Blink fee before paying to avoid max-fee reserve (#4076)by pretyflaco · 02d87445 · Jul 31, 2026 · 4 filesMessage 97 · StrongLow 36Details
Commit message · pretyflaco

fix: probe Blink fee before paying to avoid max-fee reserve (#4076)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

97/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 36/100

This change updates LNbits so that when using the Blink Bitcoin Lightning wallet, it first asks Blink's backend to estimate the routing fee before sending a payment. Previously, Blink would reserve the maximum possible fee and later refund any overpayment. The new behavior helps avoid tying up extra funds in fee reserves. It also adds a safety check that cancels the payment if the estimated fee exceeds the user's fee limit, and provides a fallback setting to send anyway when fee probing is not possible (for example, with certain invoice types).

AI review queuedfix: harden ambiguous payments (#4110)by Arc · d1a431af · Jul 31, 2026 · 30 filesMessage 80 · StrongHigh 72Details
Commit message · Arc

fix: harden ambiguous payments (#4110)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · High 72/100

This commit hardens how LNbits decides whether a Lightning payment succeeded, failed, or is still pending. Previously, many wallet adapters treated unclear or ambiguous provider responses (network errors, HTTP 500s, timeouts, malformed JSON, unknown swap states, etc.) as definite failures. That could let a user be refunded for a payment that actually went through, or let a payment be marked failed when it was only delayed. The patch makes almost all ambiguous responses 'pending' instead, only marking a payment as failed when the backend clearly rejected it before dispatching funds. It also fixes handling of checking IDs returned by backends and adds many tests for these edge cases.

AI review queuedAdd lightning addresses for wallets in core (#4035)by blackcoffeexbt · e6a61faf · Jul 31, 2026 · 29 filesMessage 73 · AdequateLow 32Details
Commit message · blackcoffeexbt

Add lightning addresses for wallets in core (#4035)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 32/100

This commit adds a new feature that lets every LNbits wallet have its own Lightning Address (like an email-style address for receiving Bitcoin payments). It includes database changes, new API endpoints, validation rules, and admin settings. The commit itself is a feature addition, not a stated security fix. There are no obvious critical vulnerabilities in the diff, but the new code introduces several areas where security assumptions matter, such as who can set an address, what characters are allowed, and how payments are created when someone pays the address.

AI review queuedfix(wallet): use payment_processing i18n key for NFC pay spinner (#4097)by Bartok · 37430f6a · Jul 27, 2026 · 2 filesMessage 85 · StrongInformational 15Details
Commit message · Bartok

fix(wallet): use payment_processing i18n key for NFC pay spinner (#4097)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a tiny user-interface wording fix. It changes the loading message shown while paying with an NFC tag from the generic English text 'Processing...' to a translatable key called 'payment_processing', so it can appear in the user's chosen language. There is no security issue here.

Security candidateUsers should be allowed to downgrade payout permission (#4083)by Arc · b15478ac · Jul 27, 2026 · 2 filesMessage 73 · AdequateLow 26Details
Commit message · Arc

Users should be allowed to downgrade payout permission (#4083)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
update trustcredential or privilege state
AI analysis · Low 26/100

This commit updates minified JavaScript files related to extension components in LNbits. The visible title suggests it allows users to 'downgrade payout permission' for extensions. The actual diff is a large minified bundle change that is hard to read, and no clear security-relevant code pattern is directly visible. It likely fixes a UI/permission workflow issue where users could not reduce an extension's payout permission level.

AI review queuedfix: REST contract implementation between lnbits sparkL2 wallet and sparkL2 sidecar (#3952)by BrunswickBTC · 7258bd32 · Jul 27, 2026 · 1 fileMessage 85 · StrongLow 31Details
Commit message · BrunswickBTC

fix: REST contract implementation between lnbits sparkL2 wallet and sparkL2 sidecar (#3952)

Co-authored-by: Arc <33088785+arcbtc@users.noreply.github.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 31/100

This commit fixes a bug in LNbits' SparkL2 wallet where, after making a payment, the system would use the payment hash as the internal tracking ID if the response from the sidecar service did not provide one. The change makes the system rely only on the sidecar's returned tracking ID. This could prevent bookkeeping mismatches or duplicate/confused payment records, but the commit itself does not describe a security vulnerability.

Security candidatefeat: add wasm manifest (#4089)by Vlad Stan · 8723d327 · Jul 24, 2026 · 19 filesMessage 65 · AdequateLow 31Details
Commit message · Vlad Stan

feat: add wasm manifest (#4089)

Co-authored-by: Arc <ben@arc.wales>

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 31/100

This commit adds support for a new category of browser-based extensions ('WASM extensions') in LNbits. It introduces a second manifest list, fetches extra configuration from URLs, and wires up permission checks before installing these extensions. There is no clear security bug in the diff, but the change expands the attack surface by adding a new extension type and by fetching remote config files. The code also contains a small duplication bug where the WASM manifest list is added twice in one place, which is likely harmless but shows the patch is fresh and partially incomplete.