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 48 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: run blocking SMTP calls in a thread to avoid blocking the event loop (#3988)by Nathan Day · 0ce2501e · Jun 17, 2026 · 1 fileMessage 82 · StrongTriage 0Details
Commit message · Nathan Day

fix: run blocking SMTP calls in a thread to avoid blocking the event loop (#3988)

82/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedfix: stop updating internal invoices inside the listener unlike external one (#3984)by dni ⚡ · f2351145 · Jun 17, 2026 · 8 filesMessage 85 · StrongLow 46Details
Commit message · dni ⚡

fix: stop updating internal invoices inside the listener unlike external one (#3984)

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 · Low 46/100

This commit reworks how LNbits updates the status of internal (same-system) invoices versus external (Lightning network) invoices. Previously, both kinds were run through the same update path inside a background listener, which could mark internal fiat-backed invoices as paid before the fiat provider actually confirmed payment. The change separates the two flows: external invoices are still updated from the Lightning stream, while internal invoices are now only looked up and dispatched to listeners, relying on the payment service to have already updated them. It also fixes a few related LND REST wallet bugs, such as using the newer 'state' field instead of the deprecated 'settled' field and handling malformed responses more safely.

Lower-priorityfeat: use cached rate from exchange_rate_history_setting (#4001)by dni ⚡ · 2eb7d67b · Jun 17, 2026 · 2 filesMessage 85 · StrongTriage 0Details
Commit message · dni ⚡

feat: use cached rate from exchange_rate_history_setting (#4001)

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-priorityfeat: electrum util for onchain data (#3999)by dni ⚡ · a82093b7 · Jun 17, 2026 · 4 filesMessage 65 · AdequateTriage 0Details
Commit message · dni ⚡

feat: electrum util for onchain data (#3999)

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: revolut unsubscribe (#4009)by Vlad Stan · ee595eed · Jun 16, 2026 · 3 filesMessage 55 · ThinTriage 0Details
Commit message · Vlad Stan

fix: revolut unsubscribe (#4009)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedfix(lnd): enable MPP via max_parts=16 and time_pref in SendPaymentV2 (#3916)by Morata · dfdce54e · Jun 8, 2026 · 1 fileMessage 85 · StrongInformational 19Details
Commit message · Morata

fix(lnd): enable MPP via max_parts=16 and time_pref in SendPaymentV2 (#3916)

Co-authored-by: dni ⚡ <office@dnilabs.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 19/100

This change adjusts how LNbits sends Lightning payments through LND by enabling multi-part payments (splitting a payment across up to 16 routes) and slightly favoring faster routes over cheaper ones. It is a functional/performance fix, not a security patch. There is no direct evidence in the commit that it fixes a vulnerability or that it was disclosed as a security issue.

Lower-priorityopen href on new tab on QR click (#3989)by Tiago Vasconcelos · 1367480e · Jun 8, 2026 · 2 filesMessage 53 · ThinTriage 0Details
Commit message · Tiago Vasconcelos

open href on new tab on QR click (#3989)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityfeat: add boltz-client (#3997)by Arc · e2d83b51 · Jun 5, 2026 · 3 filesMessage 65 · AdequateTriage 0Details
Commit message · Arc

feat: add boltz-client (#3997)

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: update to v1.5.5-rc2 (#3998)by dni ⚡ · 83699289 · Jun 4, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · dni ⚡

chore: update to v1.5.5-rc2 (#3998)

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: CSV export limit (#3996)by Vlad Stan · f04e88d8 · Jun 3, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · Vlad Stan

fix: CSV export limit (#3996)

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 candidatefix: do not hit sso provider on user missmatch (#3995)by Vlad Stan · 564edfc4 · Jun 3, 2026 · 2 filesMessage 70 · AdequateModerate 59Details
Commit message · Vlad Stan

fix: do not hit sso provider on user missmatch (#3995)

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
authentication path
AI analysis · Moderate 59/100

This patch fixes a security gap in LNbits' single-sign-on (SSO) login flow. Previously, an attacker could start an SSO login for someone else's user ID, potentially tricking the system into linking an external identity to an account they do not own. The fix now checks that the requested user ID matches the currently authenticated user before redirecting to the SSO provider. The commit message and tests confirm the issue was a 'user mismatch' that caused an unwanted SSO-provider hit.

AI review queuedchore: update pyright to latest and fix new issues (#3978)by dni ⚡ · b98515df · Jun 3, 2026 · 17 filesMessage 70 · AdequateInformational 15Details
Commit message · dni ⚡

chore: update pyright to latest and fix new issues (#3978)

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 pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine developer maintenance task: upgrading the Pyright static type checker to a newer version and fixing the new type-check warnings it produced. There are no functional code changes intended to alter behavior, and nothing in the commit suggests a security fix or vulnerability.

Lower-priorityFix: Allow the LNURL spec fallback scheme for LNURLw (#3961)by Tiago Vasconcelos · 1e0fc845 · Jun 3, 2026 · 2 filesMessage 70 · AdequateTriage 0Details
Commit message · Tiago Vasconcelos

Fix: Allow the LNURL spec fallback scheme for LNURLw (#3961)

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-prioritychore(deps): bump idna from 3.14 to 3.15 (#3981)by dependabot[bot] · a1d94834 · Jun 3, 2026 · 1 fileMessage 88 · StrongTriage 0Details
Commit message · dependabot[bot]

chore(deps): bump idna from 3.14 to 3.15 (#3981)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

88/100 · StrongMessage clarity
✓ 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-priorityfix: revolut subscriptions (#3994)by Arc · 5de4239f · Jun 3, 2026 · 2 filesMessage 70 · AdequateTriage 0Details
Commit message · Arc

fix: revolut subscriptions (#3994)

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

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Lower-priorityfix: theming was slowing frontend (#3992)by Arc · c404666d · Jun 2, 2026 · 4 filesMessage 65 · AdequateTriage 0Details
Commit message · Arc

fix: theming was slowing frontend (#3992)

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: update_payment should return the updated payment (#3983)by dni ⚡ · 190a466c · May 25, 2026 · 2 filesMessage 70 · AdequateTriage 0Details
Commit message · dni ⚡

fix: update_payment should return the updated payment (#3983)

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
AI review queuedMerge commit from forkby Riccardo Balbo · d01e3523 · May 25, 2026 · 1 fileMessage 28 · OpaqueHigh 70Details
Commit message · Riccardo Balbo

Merge commit from fork

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · High 70/100

This commit adds safety checks to LNbits' NWC (Nostr Wallet Connect) wallet code. It now verifies that invoice lookups return the expected payment hash, and that Nostr events come from the expected service public key and have valid signatures. These changes close paths where a malicious relay or third party could return fake invoice data or impersonate the wallet service.

Lower-priorityfix: make payments tags chart display dependant on showPaymentTags (#3943)by krvi · 88672501 · May 25, 2026 · 1 fileMessage 70 · AdequateTriage 0Details
Commit message · krvi

fix: make payments tags chart display dependant on showPaymentTags (#3943)

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-prioritychore: update to v1.5.5-rc1 (#3990)by dni ⚡ · ce57d081 · May 24, 2026 · 2 filesMessage 65 · AdequateTriage 0Details
Commit message · dni ⚡

chore: update to v1.5.5-rc1 (#3990)

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-priorityfeat: allow extra appending (#3974)by Tiago Vasconcelos · 52304e07 · May 22, 2026 · 5 filesMessage 65 · AdequateTriage 0Details
Commit message · Tiago Vasconcelos

feat: allow extra appending (#3974)

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
Lower-priorityfeat: add visibility toggle to inputs (#3940)by Tiago Vasconcelos · 6664eebf · May 22, 2026 · 3 filesMessage 65 · AdequateTriage 0Details
Commit message · Tiago Vasconcelos

feat: add visibility toggle to inputs (#3940)

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
Lower-priorityfeat: hide burger bg toggle (#3969)by Arc · 2a2af818 · May 22, 2026 · 15 filesMessage 80 · StrongTriage 0Details
Commit message · Arc

feat: hide burger bg toggle (#3969)

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
Lower-priorityfIx: pyinstrument import needed for nix (#3985)by Arc · 9b47f632 · May 22, 2026 · 3 filesMessage 65 · AdequateTriage 0Details
Commit message · Arc

fIx: pyinstrument import needed for nix (#3985)

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: square integration (#3962)by Vlad Stan · a61807a2 · May 22, 2026 · 23 filesMessage 55 · ThinLow 28Details
Commit message · Vlad Stan

feat: square integration (#3962)

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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 28/100

This commit adds new integrations for Square and Revolut as fiat payment providers in LNbits. It also introduces an 'external_id' field on payments to track external provider references. The changes are primarily feature additions: new API clients, webhook handlers, subscription flows, and database/schema updates. There is no explicit security fix or vulnerability disclosure in the commit message or diff. Some routine security-relevant patterns are present (HMAC webhook signature verification, input length validation), but the commit is a large feature patch rather than a documented security patch.