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 18 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.

Lower-priorityfix: appimage build (#4139)by Arc · 5f427230 · Sep 2, 2026 · 4 filesMessage 55 · ThinTriage 0Details
Commit message · Arc

fix: appimage build (#4139)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-prioritychore: version bump `"1.6.0rc4"` (#4137)by Vlad Stan · a16dd7ce · Aug 31, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · Vlad Stan

chore: version bump `"1.6.0rc4"` (#4137)

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
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.

Lower-prioritychore: version bump to 1.6.0rc3 (#4135)by Vlad Stan · 845f6df6 · Aug 27, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · Vlad Stan

chore: version bump to 1.6.0rc3 (#4135)

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
Lower-priorityfix: restore the background blur on the drawers (#4134)by Tiago Vasconcelos · f0dc9cab · Aug 27, 2026 · 4 filesMessage 70 · AdequateTriage 0Details
Commit message · Tiago Vasconcelos

fix: restore the background blur on the drawers (#4134)

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
Lower-prioritytest: fix boltz test (#4133)by Vlad Stan · 5165de2f · Aug 25, 2026 · 6 filesMessage 75 · AdequateTriage 0Details
Commit message · Vlad Stan

test: fix boltz test (#4133)

75/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
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.

Lower-prioritychore(deps): bump dompurify from 3.4.12 to 3.4.13 (#4131)by dependabot[bot] · 1c253831 · Aug 20, 2026 · 4 filesMessage 93 · StrongTriage 0Details
Commit message · dependabot[bot]

chore(deps): bump dompurify from 3.4.12 to 3.4.13 (#4131)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: alan <alan@lnbits.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
automated dependency-update discount
Lower-priorityMerge commit from forkby blackcoffeexbt · 0e3246e6 · Aug 20, 2026 · 2 filesMessage 61 · AdequateTriage 0Details
Commit message · blackcoffeexbt

Merge commit from fork

The public payment status endpoint returned the stored preimage in the
pending-payment fall-through, leaking valid preimages of unpaid invoices
to unauthenticated callers on funding sources that generate the preimage
at invoice creation (FakeWallet, CoreLightning, CLNRest, LndRest,
LndGrpc, Eclair).

Only expose the preimage once the payment is actually successful and
scrub it from details in the exception branch. Adds a regression test
covering unauthenticated, invalid-key, non-owning-key, expired-invoice
and paid-control cases.

61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidencemerge-commit duplicate discount
Lower-priorityfix: update npm packages and fix markdown (showdown) with dompurify (#4128)by dni ⚡ · bf1977d0 · Aug 20, 2026 · 12 filesMessage 85 · StrongTriage 0Details
Commit message · dni ⚡

fix: update npm packages and fix markdown (showdown) with dompurify (#4128)

Co-authored-by: alan <alan@lnbits.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
Lower-priorityfix: inherit default color for href (#4125)by dni ⚡ · 8b64d370 · Aug 20, 2026 · 3 filesMessage 65 · AdequateTriage 0Details
Commit message · dni ⚡

fix: inherit default color for href (#4125)

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

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
Lower-priorityfix: make blockexplorer page public (#4124)by dni ⚡ · 0296c583 · Aug 20, 2026 · 5 filesMessage 65 · AdequateTriage 0Details
Commit message · dni ⚡

fix: make blockexplorer page public (#4124)

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

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
Lower-prioritychore(deps): bump aiohttp from 3.14.1 to 3.14.3 (#4120)by dependabot[bot] · 9495854d · Aug 10, 2026 · 1 fileMessage 93 · StrongTriage 0Details
Commit message · dependabot[bot]

chore(deps): bump aiohttp from 3.14.1 to 3.14.3 (#4120)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@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
automated dependency-update discount
Lower-priorityAdd security.md (#4126)by blackcoffeexbt · 43e42eb3 · Aug 7, 2026 · 1 fileMessage 41 · ThinTriage 0Details
Commit message · blackcoffeexbt

Add security.md (#4126)

41/100 · ThinMessage clarity
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritychore: update to v1.6.0-rc2 (#4121)by dni ⚡ · e6c7ebdf · Aug 5, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · dni ⚡

chore: update to v1.6.0-rc2 (#4121)

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
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.

Lower-priorityfeat :add a lightning bolt reaction (#4119)by Tiago Vasconcelos · a97c75ec · Aug 3, 2026 · 5 filesMessage 53 · ThinTriage 0Details
Commit message · Tiago Vasconcelos

feat :add a lightning bolt reaction (#4119)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
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.

Lower-prioritychore: version bump to `1.6.0-rc1` (#4117)by Vlad Stan · 04c130dc · Jul 31, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · Vlad Stan

chore: version bump to `1.6.0-rc1` (#4117)

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
Lower-priorityfix: direct fiat payments (#4116)by Vlad Stan · 51e585c7 · Jul 31, 2026 · 4 filesMessage 80 · StrongTriage 0Details
Commit message · Vlad Stan

fix: direct fiat payments (#4116)

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
Lower-priorityfix(admin): wire misc section + add_field i18n keys (#4111)by Bartok · f981ee2b · Jul 31, 2026 · 3 filesMessage 85 · StrongTriage 0Details
Commit message · Bartok

fix(admin): wire misc section + add_field i18n keys (#4111)

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
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.

Lower-priorityfix: extension metadata from non-github sources (#4109)by Vlad Stan · bae9e1bf · Jul 28, 2026 · 2 filesMessage 70 · AdequateTriage 0Details
Commit message · Vlad Stan

fix: extension metadata from non-github sources (#4109)

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
Lower-priorityfix: sanitize details_link (#4108)by Vlad Stan · 8b0413fa · Jul 28, 2026 · 4 filesMessage 55 · ThinTriage 8Details
Commit message · Vlad Stan

fix: sanitize details_link (#4108)

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

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
defensive validation