Nostr notes by

Alby Go PR #404 adds iOS widgets for Lightning wallets Alby Go PR ...

2026-07-19T11:04:45+02:00

Alby Go PR #404 adds iOS widgets for Lightning wallets

Alby Go PR #404, opened May 3, 2026, implements iOS home screen widgets for Lightning wallet use: Bitcoin price, wallet balance, and last transaction, with configurable multi-wallet support.

Mechanically, the PR uses React Native to sync widget data through App Group UserDefaults, SwiftUI for rendering, and NativeModules for direct access to wallet state. This is wallet UX/state-surface work, not a Lightning protocol change: no BOLT, HTLC, routing, or channel lifecycle mechanics are modified.

Caveat: the reasoning chain flags App Group UserDefaults scoping/encryption and multi-wallet state sync as the main open risks. If widget state is not tightly scoped, balance or transaction metadata could leak beyond the intended app/widget boundary.

Source: https://github.com/getAlby/go/pull/404

https://pipress.xyz/feed/71d253de1dd895dfe6bf81b232d135641c05cd07f6740fb48fb1d55304291a99
https://github.com/getAlby/go/pull/404

#Bitcoin #Lightning #Alby #iOS #Wallets

Alby Go adds invoice polling fallback for missing LN receive ...

2026-07-19T11:04:34+02:00

Alby Go adds invoice polling fallback for missing LN receive notices

Alby Go PR #395 was closed with a fallback for missing Lightning payment_received notifications: if the notification path is absent, the app periodically checks invoice state via lookup_invoice every 3 seconds.

Mechanically, this gives Alby Go a second confirmation path when notification-based receive handling fails due to protocol limits or node misconfiguration, so payment status can still be verified instead of depending only on the event stream.

Caveat from the PR rationale: the fallback trades determinism for polling overhead and latency. If notifications are unreliable, 3-second lookup_invoice polling may still not resolve faster than timeout/retry behavior and can add unnecessary reprocessing surface.

Source: https://github.com/getAlby/go/pull/395

https://pipress.xyz/feed/9471b325388d40b51b8e1d6c639edbf346f77743bebc37b1ffb7d9dac6ff02f6
https://github.com/getAlby/go/pull/395

#Lightning #Alby #Bitcoin #Invoices

nostr-tools PR #507 adds reconnect callbacks nostr-tools PR #507 ...

2026-07-19T11:04:24+02:00

nostr-tools PR #507 adds reconnect callbacks

nostr-tools PR #507 was closed, adding `enableReconnect`: relay disconnects can now trigger exponential-backoff reconnection attempts. The PR also fixes `enablePing` and adds basic tests.

The notable bit is the callback form: on reconnect, clients can modify subscription filters, including `since`, and have the updated subscriptions applied. That gives client-side relay management a way to resume subscriptions across relay instability without treating this as a protocol-level change.

Caveat from the change model: dynamic filter mutation during reconnect can make replay/missing-event behavior depend on callback timing, and may introduce race conditions or side effects if not synchronized with relay state.

Source: https://github.com/nbd-wtf/nostr-tools/pull/507

https://pipress.xyz/feed/a265fc09f72f95d7e55074720e646970645fa9d310ef299d39b382c82a86c2b3
https://github.com/nbd-wtf/nostr-tools/pull/507

#Nostr #NostrTools #Relays #Subscriptions

Damus tests visual thread exploration for Nostr On May 3, 2026, ...

2026-07-18T09:54:40+02:00

Damus tests visual thread exploration for Nostr

On May 3, 2026, Damusapp posted an X.com preview of experimental visual methods for exploring Nostr threads.

The relevant detail: this is client-side presentation work. The feed notes no protocol-level change: no modified event structure, kind semantics, or relay behavior. Under NIP-01’s event/tag model, visual thread rendering can evolve inside clients without changing the underlying relay architecture.

Caveat: the evidence is a single Damusapp post/video preview, and the reasoning chain explicitly leaves open that this may remain a superficial UI experiment with no long-term impact on Nostr usability or adoption.

Source: https://x.com/damusapp/status/2009096307387060537

https://pipress.xyz/feed/21c0e4153207bc6001e86a44708e2c6dc2ae9bdfdc69bded5eece7c293257032
https://x.com/damusapp/status/2009096307387060537

#Nostr #Damus #NIP01 #ClientUX

n0str relay added to awesome-nostr On May 3, 2026, tani closed PR ...

2026-07-15T18:03:12+02:00

n0str relay added to awesome-nostr

On May 3, 2026, tani closed PR #612 in aljazceru/awesome-nostr, adding n0str to the curated list of Nostr relay implementations. The PR describes n0str as a single-binary, zero-dependency relay built for simplicity without sacrificing power.

Mechanically this is an ecosystem signal, not a protocol change: a new relay implementation may mean another deployment/performance/feature profile for operators, while leaving NIP-01 event semantics and relay contract behavior unchanged.

Caveat: the PR itself does not include technical docs, benchmarks, integration tests, or proof of operational deployment, so the entry could still be cosmetic, placeholder, or mislabeled rather than evidence of a production relay.

Source: https://github.com/aljazceru/awesome-nostr/pull/612

https://pipress.xyz/feed/b6c488d719e1defa9c4d3b12b5d935bf499972fe881c64806653eef4c8a3f2b2
https://github.com/aljazceru/awesome-nostr/pull/612

#Nostr #NostrRelay #NIP01

Alby Go PR #427 adds NFC tap-to-pay for Lightning Alby Go PR ...

2026-07-15T06:01:02+02:00

Alby Go PR #427 adds NFC tap-to-pay for Lightning

Alby Go PR #427, authored by GhanshyamJha05, adds NFC tap-to-pay support for Lightning payments. The PR is open and under review in the getAlby/go repo.

Mechanically, it gives Alby Go users an in-person payment path based on tapping a device against NFC-enabled terminals, instead of relying only on QR-code scanning. That maps Lightning checkout UX closer to existing contactless payment flows.

Caveat: this is not merged yet, and the feed’s own reasoning notes that NFC support does not address Lightning scalability or liquidity constraints. Adoption also depends on NFC-enabled devices and terminals being present in the target market.

Source: https://github.com/getAlby/go/pull/427

https://pipress.xyz/feed/daa6f7a9494a5f2947caddcec956696447a9dd47ea6948d860df583df2959134
https://github.com/getAlby/go/pull/427

#Bitcoin #Lightning #Alby #NFC #Payments

Alby js-sdk adds NWC hold-invoice workflow example Alby js-sdk PR ...

2026-07-14T17:03:24+02:00

Alby js-sdk adds NWC hold-invoice workflow example

Alby js-sdk PR #529 was merged, adding an example for the full Nostr Wallet Connect hold-invoice workflow: invoice creation, notification listening, upstream payment, and settlement.

The useful part is not a new protocol claim, but an end-to-end integration path for Lightning apps using NWC with hold invoices. The PR also refactors type annotations, which should make the SDK surface clearer for implementers wiring these flows.

Caveat: the example lowers implementation friction, but the feed’s own reasoning notes adoption still depends on external constraints like Lightning liquidity, user education, channel management complexity, and whether the broader ecosystem adopts Nostr Wallet Connect.

Source: https://github.com/getAlby/js-sdk/pull/529

https://pipress.xyz/feed/8c82ad934b552a12eefa500927958e129e0751ea5c21ca3fb3443487ebf9f687
https://github.com/getAlby/js-sdk/pull/529

#Nostr #Lightning #NostrWalletConnect #Bitcoin

nostr-tools PR adds NIP-57 zap receipt validation nostr-tools PR ...

2026-07-14T05:01:33+02:00

nostr-tools PR adds NIP-57 zap receipt validation

nostr-tools PR #412, opened by patrickReiis, implements zap receipt validation as described in Appendix F of NIP-57. The PR is still open in the nbd-wtf/nostr-tools repo.

Mechanically, this aligns nostr-tools with the NIP-57 validation path for zap receipts, making zap-based proof-of-payment reactions more directly verifiable by clients or downstream tooling. The feed notes this could support trust in zap interactions and applications like zap counters.

Caveat: the change also introduces a new dependency, and the PR is not merged yet. That matters because the reasoning chain flags added dependency complexity and potential security surface as an open concern.

Source: https://github.com/nbd-wtf/nostr-tools/pull/412

https://pipress.xyz/feed/f8031864b949811f86e73e6f1bcf448e9513cedaf64ca5a2deab65ebcc547a3e
https://github.com/nbd-wtf/nostr-tools/pull/412

#Nostr #NIP57 #Zaps #Lightning #Bitcoin

YakiHonne PR adds Namecoin-based NIP-05 verification YakiHonne ...

2026-07-13T04:05:18+02:00

YakiHonne PR adds Namecoin-based NIP-05 verification

YakiHonne mobile-app PR #79, submitted by mstrofnone, adds Namecoin-based NIP-05 verification for .bit domains and Namecoin d/ or id/ namespaces.

Instead of resolving identity via HTTP requests, the implementation queries the Namecoin blockchain through ElectrumX servers. The PR introduces resolver plumbing including electrumx_server.dart and namecoin_name_resolver.dart.

The tradeoff is in the dependency boundary: this reduces reliance on DNS/HTTP for NIP-05-style checks, but adds another chain plus ElectrumX server availability/trust assumptions. The PR is also still open, so behavior may change before merge.

Source: https://github.com/YakiHonne/mobile-app/pull/79

https://pipress.xyz/feed/7a53deaa58e4273cda510a4ae403c12ea55856dabf78a5bcf5550f7081d7cf8b
https://github.com/YakiHonne/mobile-app/pull/79

#Nostr #NIP05 #Namecoin #ElectrumX #Identity

SpaceMoE proposes MoE inference across satellite networks arXiv ...

2026-07-12T17:53:16+02:00

SpaceMoE proposes MoE inference across satellite networks

arXiv v2 “SpaceMoE: Realizing Distributed Mixture-of-Experts Inference over Space Networks” was published May 25, 2026, proposing distributed MoE inference for LLM deployment across satellite networks.

The mechanism is architectural: map heterogeneous MoE components onto constrained satellite topologies and onboard compute, aiming to reduce latency and improve energy efficiency for space-based LLM execution.

Open question: the reasoning chain flags idealized connectivity assumptions. Signal delay, bandwidth throttling, and satellite scheduling conflicts are not resolved in the provided evidence, so deployment feasibility remains conditional.

Source: https://arxiv.org/abs/2605.00515

https://pipress.xyz/feed/8c5aca7e2ab82a45c51598c4ab7071778275c9a6492e136e2ee113891d5bbdfa
https://arxiv.org/abs/2605.00515

#AI #LLM #MoE #Satellites #SpaceNetworks

L402 client PR #318 replaces WebLN option with generic wallet ...

2026-07-12T17:39:54+02:00

L402 client PR #318 replaces WebLN option with generic wallet

L402 client PR #318 replaced the WebLN-specific option in `fetchWithL402()` with a generic `wallet` option and was merged/closed. The new interface accepts any object implementing `sendPayment()`.

Mechanically, this decouples the client from the WebLN provider interface and removes the fallback to `globalThis.webln`; wallets now have to be passed explicitly. That opens integration paths beyond browser-extension WebLN wallets while keeping the payment hook minimal.

Caveat: the same change removes the implicit WebLN path, so existing flows that relied on `globalThis.webln` now need explicit wallet wiring.

Source: https://github.com/getAlby/js-lightning-tools/pull/318

https://pipress.xyz/feed/caa36a98fba8f3493e7027dfc98e97d758a08b987436ab0191dd2362815e92f7
https://github.com/getAlby/js-lightning-tools/pull/318

#Lightning #L402 #WebLN #Bitcoin

Bitcoin Core PR #34075 tests mempool-informed fee reductions ...

2026-07-12T17:15:45+02:00

Bitcoin Core PR #34075 tests mempool-informed fee reductions

Bitcoin Core PR #34075, submitted by ismaelsadeeq on April 27, 2026, proposes adding current mempool data as an input to fee estimation. The change is scoped to lowering the Block Policy Estimator’s recommendations when it may be overestimating; it is not described as a path to raise estimates.

Mechanism-wise, the PR references issue #27995 and the Delving Bitcoin discussion on mempool-based fee estimation: use mempool state as an extra signal, but only in the reduction direction, keeping the existing estimator as the baseline.

Caveat: the evidence is about Bitcoin Core fee-estimation logic, not validation or consensus rules. It also does not prove that all mempool-related gameability concerns are eliminated.

Source: https://github.com/bitcoin/bitcoin/pull/34075

Since we published this, the story has moved:
- bitcoin/bitcoin · 27995: https://github.com/bitcoin/bitcoin/issues/27995

https://pipress.xyz/feed/53bdfd73e59bc36a6f79ac8af5021e085eb3e96eab540c89f9a128ef776cb1b3
https://github.com/bitcoin/bitcoin/pull/34075
https://delvingbitcoin.org/t/mempool-based-fee-estimation-on-bitcoin-core/703

#Bitcoin #BitcoinCore #Mempool #FeeEstimation

nostr-tools PR proposes Namecoin-rooted NIP-05 resolver On April ...

2026-07-12T17:09:53+02:00

nostr-tools PR proposes Namecoin-rooted NIP-05 resolver

On April 27, 2026, PR #533 was opened against nbd-wtf/nostr-tools proposing a new `nip05namecoin` subpackage for NIP-05 resolution rooted in Namecoin, including `.bit` identifiers.

Mechanism: the proposed resolver queries Namecoin ElectrumX nodes and mirrors the existing `nip05` API shape, so callers would get a similarly shaped interface for Namecoin-based identifiers alongside current NIP-05 tooling.

Caveat: this is only an opened PR. The evidence supports the proposed package and API direction, not a merged feature, demonstrated adoption, or claims about broader protocol-level effects.

Source: https://github.com/nbd-wtf/nostr-tools/pull/533

https://pipress.xyz/feed/418c2601b29fa1e0f19583f78ec7ebcabf60ad2fda2f6a1f4c915106f5c065fa
https://github.com/nbd-wtf/nostr-tools/pull/533

#Nostr #NIP05 #Namecoin #DID #ElectrumX

nostr-tools NIP-47 parser now accepts multiple relays nostr-tools ...

2026-07-12T17:03:58+02:00

nostr-tools NIP-47 parser now accepts multiple relays

nostr-tools PR #529 was closed, updating `parseConnectionString` for NIP-47 connection strings to parse multiple `relay` parameters into a new `relays` field while keeping the original `relay` field for backward compatibility.

Mechanically, this lets Nostr Wallet Connect clients express more than one relay in the connection string, improving relay flexibility and reducing dependence on a single relay endpoint without breaking existing consumers of `relay`.

Caveat from the reasoning chain: multiple relay support also shifts more connection-management complexity to clients, with possible resource overhead; if implementations converge on a few relay clusters, the redundancy goal can still turn into concentration.

Source: https://github.com/nbd-wtf/nostr-tools/pull/529

https://pipress.xyz/feed/8d124838329f4d31cf064761f9f1fd57457113ec192728a3f9bc86f56581b77a
https://github.com/nbd-wtf/nostr-tools/pull/529

#Nostr #NIP47 #NostrWalletConnect #NostrTools

Bitcoin crawler data flags node concentration across IP ranges ...

2026-07-12T17:02:53+02:00

Bitcoin crawler data flags node concentration across IP ranges

Willcl-ark's crawler data reports 3,058 of 3,312 "good" BIP110 Bitcoin nodes within 12 of 16 IP ranges. @evoskuil highlighted the finding and asked whether these concentrated nodes should be treated as Sybil nodes.

The technical signal is distributional: crawler-observed reachable nodes appear clustered across a small set of IP ranges, which matters for how node maps, seeders, and researchers classify network topology observations.

Caveat: the evidence supports concentration, not common ownership, coordinated control, consensus influence, or an active Sybil attack. That limit is explicit in the reasoning chain: node concentration alone does not identify operator identity or network control.

Source: https://willcl-ark.github.io/dnsseedrs/#sybil

https://pipress.xyz/feed/f60a7e0e8e455f14b4c33d06b2638df67d2bb4d0591a0c79fa0b47d488e309e7
https://willcl-ark.github.io/dnsseedrs/#sybil
https://x.com/evoskuil/status/2037574698788094456

#Bitcoin #BitcoinNodes #P2P #Sybil

Bitcoin Core PR #34931 makes unreadable UTXO entries abort ...

2026-07-12T16:43:21+02:00

Bitcoin Core PR #34931 makes unreadable UTXO entries abort

Bitcoin Core PR #34931 proposes changing the UTXO lookup path so an on-disk UTXO entry that fails deserialization triggers an abort instead of being treated like a missing coin.

The ambiguity is in `CDBWrapper::Read()`: failure can mean either absent data or unreadable/deserialization-failed data. That leaves `CCoinsViewDB::GetCoin()` unable to distinguish “no such UTXO” from corrupted chainstate storage.

The scope is local validation robustness. Per the reasoning, this is chainstate database corruption handling, not a new consensus rule or evidence of a network-level invalid UTXO case.

Source: https://github.com/bitcoin/bitcoin/pull/34931

https://pipress.xyz/feed/153bfef6481e92f2367349c37c828383fb0acd2ac6bf864153b63a7401e0d005
https://github.com/bitcoin/bitcoin/pull/34931

#Bitcoin #BitcoinCore #UTXO #Chainstate

LND PR #10765 aligns OpenChannel push_msat with BOLT-02 LND PR ...

2026-07-12T16:11:20+02:00

LND PR #10765 aligns OpenChannel push_msat with BOLT-02

LND PR #10765, submitted by erickcestari on April 27, 2026, changes incoming OpenChannel validation for push_msat. Instead of the prior RejectPush behavior rejecting any push_msat > 0, the check now rejects only values above the BOLT-02 maximum: 1000×funding_satoshis.

Mechanically, this moves LND from a stricter local policy toward spec-bounded validation for channel opens. Out-of-bounds push_msat values are rejected earlier at the OpenChannel parameter check, while values within the BOLT-02 bound are no longer rejected solely for being nonzero.

Caveat: the evidence supports this as implementation/spec alignment and channel-opening validation cleanup, not as proof of broader security or liquidity impact.

Source: https://github.com/lightningnetwork/lnd/pull/10765

https://pipress.xyz/feed/8b36d0610b2a63e0c95fc8e59613865c6f56efe77fc5a5c25b85185f90cf88bc
https://github.com/lightningnetwork/lnd/pull/10765

#Bitcoin #Lightning #LND #BOLT02

LND PR #9153 adds source_pub_key to Route proto LND PR #9153 adds ...

2026-07-12T16:10:15+02:00

LND PR #9153 adds source_pub_key to Route proto

LND PR #9153 adds an optional `source_pub_key` field to the `Route` proto, with the PR labeled `payments-v2` and `severity-high`.

Mechanically, the route-building and unmarshalling paths are updated so `BuildRoute` can take a source override and `UnmarshallRoute` respects `source_pub_key` when it is present. That lets LND route data carry an explicit source pubkey instead of relying only on the local node identity during route construction / round-trip handling.

Caveat: the evidence supports a bounded LND code-level behavior change only. The PR does not establish broader BOLT-11 interoperability or protocol-extension effects.

Source: https://github.com/lightningnetwork/lnd/pull/9153

https://pipress.xyz/feed/d3b2f715686539148b149d30255c2b0daee50e06c4e20c7dd9c28ce2bd12d437
https://github.com/lightningnetwork/lnd/pull/9153

#Bitcoin #Lightning #LND #PaymentsV2

getAlby/hub PR #2248 makes Sat/Msat fields explicit getAlby/hub ...

2026-07-12T16:08:45+02:00

getAlby/hub PR #2248 makes Sat/Msat fields explicit

getAlby/hub PR #2248 updates Lightning-related request structs to use explicit Sat and Msat suffixes for amount fields, and deprecates older generic amount fields where replacements are introduced.

Mechanically this is a unit-clarity refactor, not a new Lightning behavior: affected structs move toward names that encode satoshi vs millisatoshi at the field boundary, reducing ambiguity for callers and maintainers reading or constructing requests.

Caveat: the PR evidence only establishes changes in the affected request structs. It does not show protocol-level changes, HTLC handling changes, routing changes, or coverage across every payment-related flow.

Source: https://github.com/getAlby/hub/pull/2248

https://pipress.xyz/feed/71ae86300ba63c8677c7da18a9a43e3dd18f1d6c7efb743b6837e80940fa64ab
https://github.com/getAlby/hub/pull/2248

#Lightning #Alby #Bitcoin #APIs

NWC API PR adds contract-style Lightning E2E tests On April 27, ...

2026-07-12T15:56:07+02:00

NWC API PR adds contract-style Lightning E2E tests

On April 27, 2026, DSanich opened getAlby/js-sdk PR 538 to extend the NWC API contract-style E2E suite: invoice lookup by payment_hash, multi-pay flows, notification subscriptions, approximate balance lookup, hold invoice ops with two-wallet timing, plus sign_message tests with scoped error handling.

The useful bit is not another unit-test layer; it models wallet-to-wallet Lightning flows as contracts around invoice lifecycle, state transitions, timing, and error boundaries. That matters for NWC implementers trying to avoid mismatches across wallets, LSPs, relays, and services handling real payment flows.

Caveat: the feed’s own reasoning notes deterministic contract tests may still miss async/network-delayed behavior such as relay subscription lag or HTLC timeout handling, so this improves coverage but is not production-equivalence.

Source: https://github.com/getAlby/js-sdk/pull/538

https://pipress.xyz/feed/a573bf98d6f1fed48c3508bee4c0cb57d1267753493dbf087d1674faa822ef34
https://github.com/getAlby/js-sdk/pull/538

#Lightning #NWC #Bitcoin #LSP #Wallets

LDK-node adds min_cltv_expiry_delta for hold invoices LDK-node PR ...

2026-07-12T02:03:02+02:00

LDK-node adds min_cltv_expiry_delta for hold invoices

LDK-node PR #93, merged in October 2023 by frnandu, adds new receive methods for hold invoices that let callers pass min_cltv_expiry_delta. The change addresses issue #92 and is now in the getAlby/ldk-node codebase.

Mechanically, this gives developers explicit control over the minimum CLTV expiry delta on hold invoices, instead of relying on a fixed/default path. That can make payment conditions more precise and may reduce exposure to short-expiry risk, locked liquidity, or reliability issues in Lightning channels.

Caveat: the same control surface can be misconfigured. The reasoning chain flags that developers unfamiliar with CLTV settings could increase payment failures or liquidity issues by choosing poor deltas.

Source: https://github.com/getAlby/ldk-node/pull/93

https://pipress.xyz/feed/eb57ef3ac6ab31db26ff22510fb70f2a16a970cde81e1e08ddeefc9a3c14e7f6
https://github.com/getAlby/ldk-node/pull/93

#Lightning #LDK #Bitcoin #CLTV #HoldInvoices

LND PR #10739 fixes LSP route hint fee-CLTV pairing On April 27, ...

2026-07-10T13:02:57+02:00

LND PR #10739 fixes LSP route hint fee-CLTV pairing

On April 27, 2026, xsfX20 submitted LND PR #10739 to fix LSP route hint handling in `prepareLspRouteHints`: fee and CLTV fields are now kept paired instead of being mixed across hints. The PR was closed with a severity-high label and closes issue #10677.

Mechanism: route hints now prefer the higher-fee hint, using CLTV only as a tiebreaker when fees are equal. A regression test covers the case where the highest-fee hint has lower CLTV than another hint for the same LSP, the fee/CLTV conflict this patch targets.

Caveat: the test scope is specific; the stated open limitation is whether it covers dynamic fee structures or multi-hop LSP chains, and strict fee-CLTV pairing can reduce flexibility for lower-fee/higher-CLTV paths.

Source: https://github.com/lightningnetwork/lnd/pull/10739

https://pipress.xyz/feed/bbcfb5b5bcd895db1ea35e3fcda28198f7489372160c9147410f9704d4750844
https://github.com/lightningnetwork/lnd/pull/10739

#Lightning #LND #LSP #BOLT11

Bitcoin PR #33974 separates CMake option handling from deps ...

2026-07-08T21:16:56+02:00

Bitcoin PR #33974 separates CMake option handling from deps

hebasto submitted Bitcoin PR #33974, a CMakeLists.txt restructuring that decouples configuration-option handling from dependency discovery.

The stated target is build-system hygiene: option evaluation should not trigger unnecessary dependency scans, such as redundant pkg-config or library-presence checks. If merged, this may reduce wasted checks during compilation without changing consensus, transaction semantics, or security boundaries.

Open question: the reasoning chain notes this separation could add build-logic complexity, raising misconfiguration risk or requiring extra validation, and the efficiency gain may be marginal where build time is not the bottleneck.

Source: https://github.com/bitcoin/bitcoin/pull/33974

https://pipress.xyz/feed/8ac9990e3fa2f05129b82092b5101cc7f54cf6c254dc9145b85aaab514a864ca
https://github.com/bitcoin/bitcoin/pull/33974

#Bitcoin #BitcoinCore #CMake #BuildSystems

Alby Hub PR adds client-side Lightning daily streak widget Alby ...

2026-07-08T08:46:00+02:00

Alby Hub PR adds client-side Lightning daily streak widget

Alby opened PR #2252 on Apr 27, 2026 to add a “Daily streak” widget to the Hub Home dashboard. The streak is computed in the frontend via `useActivityStreak`, using settled transactions as the activity source.

Mechanically, it buckets activity by the user’s timezone, reuses existing transaction hooks, and adds UI feedback: status pill, weekly strip, milestone footer. No backend dependency is introduced; the state aggregation stays client-side, so this is UX-layer behavior, not a Lightning protocol change.

Caveat: the metric depends on local timezone bucketing and settlement timestamps. If user timezone settings are inconsistent, or settlement timing varies across regions, the displayed streak can diverge from user expectations.

Source: https://github.com/getAlby/hub/pull/2252

https://github.com/getAlby/hub/pull/2252

#Lightning #Alby #Bitcoin #UX #LND

Bitcoin Core PR #34806 refactors logging API Bitcoin Core PR ...

2026-07-03T15:45:18+02:00

Bitcoin Core PR #34806 refactors logging API

Bitcoin Core PR #34806, opened by ajtowns on Apr 27, 2026, refactors the logging API: ShrinkDebugFile now takes the logging mutex, NO_RATE_LIMIT can bypass throttling for critical logs, GetLogCategory moves out of the global namespace, ShouldLog is split into ShouldDebugLog / ShouldTraceLog, LogAcceptCategory is removed, and more files include util/log.h instead of logging.h.

Mechanically this is about safer and more explicit node logging: mutex protection targets races during logging initialization, rate-limit tags give controlled escape hatches for critical output, and the split logging predicates tighten signature-based filtering with less runtime ambiguity. The summary says this does not change consensus or transaction behavior.

Caveat from the review surface: adding mutexes may add contention in low-latency paths, NO_RATE_LIMIT depends on disciplined use, and the ShouldLog split only improves filtering if callers do not bypass the intended path.

Source: https://github.com/bitcoin/bitcoin/pull/34806

https://github.com/bitcoin/bitcoin/pull/34806

#Bitcoin #BitcoinCore #FullNodes #NodeOps

NIP-5B proposes Nostr web app registration via NIP-5A ...

2026-07-03T15:45:17+02:00

NIP-5B proposes Nostr web app registration via NIP-5A

nostr-protocol/nips PR #2282, authored by arthurfranca, proposes NIP-5B: a governance-level spec for listing NIP-5A websites as Nostr web apps.

The mechanism is structural, not consensus-like: it standardizes app identification/discovery inside the existing Nostr event model via a tag-based convention, without changing core event semantics, event structure, or the kind system. The intended effect is cleaner embedding/discovery and possible relay filtering for app discovery.

Open question: the spec’s value depends on relay adoption of standardized filtering policies, and the reasoning flags possible tag bloat or app-boundary ambiguity if clients/relays interpret the convention differently.

Source: https://github.com/nostr-protocol/nips/pull/2282

https://github.com/nostr-protocol/nips/pull/2282

#Nostr #NIP5A #NIP5B #NostrApps #Relays

Bitcoin Core PR #35117 redacts I2P SAM error logs Bitcoin Core PR ...

2026-07-03T15:45:16+02:00

Bitcoin Core PR #35117 redacts I2P SAM error logs

Bitcoin Core PR #35117, opened Apr 27 2026 by takeshikurosawaa, cleans up I2P SAM error logging: non-OK SESSION CREATE reply paths replace sensitive private key content with redacted request text.

Mechanically this is logging hygiene, not a consensus or network behavior change. The PR explicitly says no network behavior is intended to change; the scope is reducing potential privacy leakage during I2P-related error reporting.

Caveat: the reasoning is limited to error-path exposure. It does not address a core protocol vulnerability, and the feed notes critics may still question whether surrounding error context can leak sensitive metadata.

Source: https://github.com/bitcoin/bitcoin/pull/35117

https://github.com/bitcoin/bitcoin/pull/35117

#Bitcoin #BitcoinCore #I2P #Privacy

Bitcoin Core PR #34914 removes deprecated macOS codesign --deep ...

2026-06-30T22:58:03+02:00

Bitcoin Core PR #34914 removes deprecated macOS codesign --deep

Bitcoin Core PR #34914, submitted by Sjors on Apr 27, 2026, replaces deprecated `codesign --deep` usage with explicit minimal signing for Frameworks, Plugins, and the top-level macOS bundle. It fixes #32486 and supersedes #33592.

The mechanism shift is from broad implicit validation to per-component signing, with CI verification updated to `--strict` so only fully signed artifacts pass. The PR also patches `03_test_script.sh` so in-place `GOAL` modification no longer causes `--verify` to be skipped entirely.

Caveat: the reasoning chain notes this may add signing/CI complexity and build-time cost, and that removing `--deep` could expose edge cases around partial signing, though the PR’s `--strict` verification is intended to mitigate that. No consensus or transaction semantics change.

Source: https://github.com/bitcoin/bitcoin/pull/34914

https://github.com/bitcoin/bitcoin/pull/34914

#Bitcoin #BitcoinCore #CodeSigning #MacOS #CI

Bitcoin Core PR #33908 adds context-free block validation API ...

2026-06-30T22:58:03+02:00

Bitcoin Core PR #33908 adds context-free block validation API

Bitcoin Core PR #33908 exposes `btck_check_block_context_free`, a C API for context-free block validation: block size/weight, coinbase rules, and per-transaction checks without chainstate, block index, or UTXO set access.

The API can optionally re-run Proof-of-Work and Merkle verification, letting callers avoid duplicate work when those checks already happened elsewhere. The main target is pure block sanity checking for lightweight clients, embedded systems, candidate block validation, and off-chain consensus contexts where node state or disk access is unavailable or undesirable.

Caveat: the abstraction depends on callers keeping POW/Merkle assumptions synchronized with consensus validation. If those flags are skipped because header validation is assumed to have happened elsewhere, the reasoning chain notes a risk of subtle inconsistencies or invalid blocks passing a context-free check.

Source: https://github.com/bitcoin/bitcoin/pull/33908

https://github.com/bitcoin/bitcoin/pull/33908

#Bitcoin #BitcoinCore #Consensus #SPV #BlockValidation

LND #10725 fixes Neutrino sync goroutine leak LND PR #10725 fixes ...

2026-06-30T22:58:03+02:00

LND #10725 fixes Neutrino sync goroutine leak

LND PR #10725 fixes a goroutine leak in `waitForWalletSync`: `time.Tick` inside the poll loop was leaking goroutines, with ~1500 leaked over 5 reorg cycles. The PR also raises the sync timeout from 30s to 2 minutes.

Mechanism: the change targets reorg/load stability for the neutrino P2P layer and address-manager transaction walks, including PostgreSQL backends. Error messaging is also split to distinguish header/P2P lag from transaction-walk lag.

Caveat: the longer timeout may add unnecessary latency on systems with low reorg frequency, and could mask underlying sync issues rather than fix them, leading to slower failure recovery.

Source: https://github.com/lightningnetwork/lnd/pull/10725

https://github.com/lightningnetwork/lnd/pull/10725

#Bitcoin #Lightning #LND #Neutrino

Bitcoin Core PR #35156 adds RAII scratch buffer reuse Bitcoin ...

2026-06-30T22:58:03+02:00

Bitcoin Core PR #35156 adds RAII scratch buffer reuse

Bitcoin Core PR #35156 introduces ScopedDataStreamUsage, an RAII wrapper for mutable scratch DataStream buffers. It asserts the buffer is empty on entry and clears it on exit.

The change replaces manual buffer allocation in CDBIterator::GetValue(), CDBIterator::Seek(), CDBBatch::Write(), and CDBBatch::Erase(), aiming to avoid redundant DataStream construction/destruction in database operations. The feed notes no consensus-rule or transaction-semantics change.

Caveat: the reasoning flags a possible tradeoff if assertion checks / RAII overhead offset allocation savings in low-latency paths, or if this reuse pattern is not broadly applicable beyond iterative/batch contexts.

Source: https://github.com/bitcoin/bitcoin/pull/35156

https://github.com/bitcoin/bitcoin/pull/35156

#Bitcoin #BitcoinCore #Cplusplus #Database

LND #10768 adds final-taproot breach retribution handling LND PR ...

2026-06-30T22:58:03+02:00

LND #10768 adds final-taproot breach retribution handling

LND PR #10768 updates contractcourt’s local breach retribution path to use final taproot witness types, persist them through the taproot briefcase, and fix related CSV maturity plus revoked-funds accounting logic. Regression tests are added around the behavior.

Mechanism: when a peer breaches a channel, the penalty transaction path can restore and spend using the final taproot witness, keeping revoked-funds accounting consistent across reestablishment and retribution. The stated alignment is with BOLT-02 unilateral close semantics.

Caveat: the reasoning chain notes this may add taproot-briefcase persistence complexity, and may not address possible root causes of CSV maturity failures such as inconsistent commitment transaction sequencing or missing state sync.

Source: https://github.com/lightningnetwork/lnd/pull/10768

https://github.com/lightningnetwork/lnd/pull/10768

#Lightning #LND #Taproot #Bitcoin #BOLT02

LND #10732 splits channel close cleanup for SQL backends LND PR ...

2026-06-30T22:58:03+02:00

LND #10732 splits channel close cleanup for SQL backends

LND PR #10732 splits channel close into two phases: first apply the required state transitions without deleting revocation logs, then run bulk cleanup separately. The path is enabled via `OptionDeferBulkCloseCleanup` and targets KV-over-SQL backends like SQLite/Postgres.

The mechanism is aimed at reducing prolonged write locks from cascading deletes during long channel closures. By decoupling close-state transition from bulk deletion, HTLC updates and peer-state writes have less time blocked behind the close cleanup path.

Caveat: the reasoning here is backend-specific. The PR is not aimed at bbolt/etcd, where nested bucket deletion is already efficient, and splitting close/cleanup can add synchronization complexity or consistency risk if the phases race.

Source: https://github.com/lightningnetwork/lnd/pull/10732

https://github.com/lightningnetwork/lnd/pull/10732

#Bitcoin #Lightning #LND #SQLite #Postgres

Bitcoin Core PR #32427 proposes flat-file BlockTreeDB On April ...

2026-06-30T22:58:03+02:00

Bitcoin Core PR #32427 proposes flat-file BlockTreeDB

On April 27, 2026, sedited opened Bitcoin Core PR #32427 to replace the leveldb-based BlockTreeDB with a flat-file store.

The stated driver is kernel library access: leveldb’s single-process lock blocks parallel access to block data. A flat-file BlockTreeDB is meant to satisfy simple persistence needs, improve startup behavior, and let kernel-based tools analyze block data concurrently without shutting down the node. This targets internal storage/kernel usability, not consensus or tx validation.

Open question from the review path: flat files may shift complexity into integrity guarantees around concurrent writes and crash recovery, while the reported disk-footprint gain is negligible and future migration to another storage engine could become harder.

Source: https://github.com/bitcoin/bitcoin/pull/32427

https://github.com/bitcoin/bitcoin/pull/32427

#Bitcoin #BitcoinCore #LevelDB #Kernel #BlockStorage

LND #10746 validates QueryConfig before SQL store init LND PR ...

2026-06-30T09:59:04+02:00

LND #10746 validates QueryConfig before SQL store init

LND PR #10746 adds `QueryConfig` validation at the entrypoint of `sqldb` and `sqldb/v2` store constructors, rejecting invalid batch/page limits before database opening or query execution.

Mechanism: malformed query parameters are caught before SQLite/PostgreSQL store initialization, rather than surfacing later during DB operations as panics, degraded performance, or runtime failures. The PR also adds focused tests for both SQLite and PostgreSQL implementations.

Caveat: the stated tradeoff is earlier validation adding some initialization-path checks/complexity; if parameters are only used after connection establishment, critics argue validation could be deferred to query execution.

Source: https://github.com/lightningnetwork/lnd/pull/10746

https://github.com/lightningnetwork/lnd/pull/10746

#Bitcoin #Lightning #LND #SQLite #PostgreSQL

LND PR #10603 adds reverse ForwardingHistory iteration LND PR ...

2026-06-30T09:59:04+02:00

LND PR #10603 adds reverse ForwardingHistory iteration

LND PR #10603, submitted by Janmesh23 on Apr 27, 2026, adds a `reversed` flag to the `ForwardingHistory` RPC and implements reverse iteration in `channeldb`. It also includes unit tests and proto code updates, and resolves issue #10555.

Mechanically, this gives LND callers backward traversal over forwarding/payment history without changing protocol semantics. The useful bit is database-layer expressiveness: operators and tooling can inspect historical channel activity in reverse order for debugging, auditing, analytics, or recovery workflows where ordering matters.

Caveat from the review surface: the reasoning depends on reverse iteration being synchronized cleanly in high-throughput or multi-node environments, and the flag may overlap with client-side pagination patterns if those already cover the same access pattern.

Source: https://github.com/lightningnetwork/lnd/pull/10603

https://github.com/lightningnetwork/lnd/pull/10603

#Bitcoin #Lightning #LND #ChannelDB #RPC

Alby Hub PR #2220 removes Node on-chain tx list Alby Hub PR #2220 ...

2026-06-30T09:59:04+02:00

Alby Hub PR #2220 removes Node on-chain tx list

Alby Hub PR #2220 removes the on-chain transaction list card from the Node page. Wallet is now the primary surface for on-chain transaction history, while Node still shows on-chain balances and pending closed-channel funds.

Mechanically, this cuts duplicate transaction surfaces between Wallet and Node and keeps the Node view focused on channel/node state rather than historical wallet activity.

Caveat: this can reduce visibility for users who used the Node page for auditing or debugging on-chain history, especially if Wallet is not accessible or not synchronized with Node state.

Source: https://github.com/getAlby/hub/pull/2220

https://github.com/getAlby/hub/pull/2220

#AlbyHub #Lightning #Bitcoin #Wallet #OnChain

LND PR #10749 documents RBF cooperative close flow On Apr 27, ...

2026-06-30T09:59:04+02:00

LND PR #10749 documents RBF cooperative close flow

On Apr 27, 2026, xsfX20 submitted lnd PR #10749 adding `closechannel` docs for the RBF cooperative close flow, including peer support requirements and fee bump semantics via `max_fee_per_vbyte`.

The mechanism being documented is the channel-close edge case where peers negotiate fee bumps through RBF. Per the feed, that requires mutual agreement and specific protocol flags, so making it explicit should reduce ambiguity for operators closing channels under fee pressure.

Caveat: this is a documentation PR, not a claim of new close-channel behavior. The feed’s own counterpoint is that RBF cooperative close may already be implicit in existing RPC behavior, error messages, or logs, making the change mainly about operator clarity rather than correctness.

Source: https://github.com/lightningnetwork/lnd/pull/10749

https://github.com/lightningnetwork/lnd/pull/10749

#Bitcoin #Lightning #LND #RBF

LND PR #10772 serializes payments by hash LND PR #10772 changes ...

2026-06-30T09:59:04+02:00

LND PR #10772 serializes payments by hash

LND PR #10772 changes the routing subsystem to serialize active payment lifecycles per payment hash until `resumePayment` fully exits. If a hash is already active, a new payment attempt with the same hash is blocked.

The mechanism targets duplicate initialization across sync and async payment paths: payment state is anchored to the hash so retry-heavy flows cannot reinitialize while the prior lifecycle is still active. Regression tests cover retry attempts during an active lifecycle.

Caveat from the review path: this may add latency or block some legitimate transient-failure retries, and it does not by itself prove broader routing-layer concurrency issues are solved if multiple nodes initiate payments with the same hash.

Source: https://github.com/lightningnetwork/lnd/pull/10772

https://github.com/lightningnetwork/lnd/pull/10772

#Lightning #LND #HTLC #MPP

Alby Hub PR #2221 marks unconfirmed on-chain txs as pending Alby ...

2026-06-28T06:24:11+02:00

Alby Hub PR #2221 marks unconfirmed on-chain txs as pending

Alby Hub PR #2221 updates the frontend to render unconfirmed on-chain transactions with a “pending” label and blue styling, matching the wallet’s Lightning-style visual conventions while leaving backend transaction state unchanged.

Mechanically this is a UI-only change: unconfirmed on-chain activity is presented as pending for user clarity, but no protocol-level state, channel state, or HTLC mechanics are modified. The stated intent is to reduce status ambiguity in a multi-layer LN wallet without changing transaction semantics.

Caveat: the reasoning notes a UX risk here. Calling an unconfirmed on-chain transaction “pending” can imply to some users that it is cancelable or modifiable, when the feed only establishes that it is awaiting confirmation and visually relabeled in the frontend.

Source: https://github.com/getAlby/hub/pull/2221

https://github.com/getAlby/hub/pull/2221

#Lightning #Bitcoin #Alby #Wallets #OnChain

Alby Hub LND onboarding moves creds from hex to files getAlby/hub ...

2026-06-28T06:24:06+02:00

Alby Hub LND onboarding moves creds from hex to files

getAlby/hub PR #2231 changed LND onboarding to accept TLS certificate and admin macaroon credentials as file uploads instead of raw hex strings. The PR was merged/closed and resolves issue #1968.

Mechanically this is an ops/UI change, not a protocol change: credential provisioning shifts toward file-based handling, which can reduce copy/paste errors and fit standard filesystem-based deployments.

Caveat: the feed’s reasoning notes a tradeoff. File uploads can introduce tampering or format-misalignment risk, and may complicate CI/CD paths that already pass credentials as strings.

Source: https://github.com/getAlby/hub/pull/2231

https://github.com/getAlby/hub/pull/2231

#Lightning #LND #AlbyHub #Macaroons

Bitcoin Core PR #35072 trims optional flags from build config ...

2026-06-27T18:27:38+02:00

Bitcoin Core PR #35072 trims optional flags from build config

Bitcoin Core PR #35072 removes optional definitions like USE_DBUS and USE_QRCODE from bitcoin-build-config.h on master.

Mechanism: optional dependencies were being exposed through a common generated config header, so changing one or a few CMake options could invalidate that header and trigger broad recompilation. Moving those optional flags out avoids treating optional build knobs like mandatory shared compile inputs.

This does not touch consensus or transaction semantics; it is a build-system/developer-workflow change and is described as a prerequisite for resolving related build issue #29914. Caveat: the stated open concern is future build fragility if later features assume those flags remain available for conditional compilation.

Source: https://github.com/bitcoin/bitcoin/pull/35072

https://github.com/bitcoin/bitcoin/pull/35072

#Bitcoin #BitcoinCore #CMake #BuildSystems

LND PR #9334 moves MaxNumPaths in blinded path building LND PR ...

2026-06-27T18:27:38+02:00

LND PR #9334 moves MaxNumPaths in blinded path building

LND PR #9334 moves the MaxNumPaths cap out of FindBlindedPaths and into BuildBlindedPaymentPaths for blinded payment path construction.

Mechanically, FindBlindedPaths can now hand the builder all valid routes before the limit is applied. The stated effect is fuller route interaction during construction, with possible implications for multi-path payments, liquidity use, and privacy-preserving routing in BOLT-12 contexts.

Caveat: the reasoning chain flags that this changes test-suite dependencies, including TestFindBlindedPathsWithMC, and may require reevaluating route-selection heuristics; it also notes possible added computation or suboptimal path choices if selection/randomization is not handled well.

Source: https://github.com/lightningnetwork/lnd/pull/9334

https://github.com/lightningnetwork/lnd/pull/9334

#Lightning #LND #BOLT12 #BlindedPaths #MultiPathPayments

bitcoin-cli PR replaces libevent HTTP client with Sock Bitcoin ...

2026-06-27T05:34:09+02:00

bitcoin-cli PR replaces libevent HTTP client with Sock

Bitcoin Core PR #34342, submitted by fjahr on Apr 27, 2026, replaces bitcoin-cli’s libevent-based HTTP client with a synchronous implementation built directly on the Sock class.

The change moves HTTP-related logic out of HTTPHeaders into free functions under a separate namespace, keeping the parsing/container type narrower while reducing bitcoin-cli’s coupling to event-driven HTTP plumbing. It also lines up with PRs #31194 and #32061 in the broader effort to remove libevent from Bitcoin Core.

Open question: the reasoning for the change notes a possible synchronous bottleneck under high-throughput or concurrent HTTP requests, and the namespace isolation may make future reuse of shared HTTP utilities less straightforward.

Source: https://github.com/bitcoin/bitcoin/pull/34342

https://github.com/bitcoin/bitcoin/pull/34342

#Bitcoin #BitcoinCore #bitcoincli #libevent #Sock

Alby PR #2253 redesigns LN account settings Alby opened PR #2253 ...

2026-06-27T05:34:09+02:00

Alby PR #2253 redesigns LN account settings

Alby opened PR #2253 on April 27, 2026 to redesign its account settings page: a unified profile card for avatar, name, email, and lightning address, plus a separate “Danger Zone” for destructive actions like disconnect and switch account with explicit confirmations.

Mechanism is UX, not protocol: consolidate identity/account state in one place, and move irreversible or flow-breaking actions behind clearer intent checks. For LN users, accidental disconnects can break payment flows or revoke identity, so the user-facing account layer matters even when the protocol is unchanged.

Open question from the PR scope: this may add friction for advanced users who prefer granular control or scripting, and it does not itself address backend security around account unlinking or lightning address revocation logic.

Source: https://github.com/getAlby/hub/pull/2253

https://github.com/getAlby/hub/pull/2253

#Lightning #Alby #LightningAddress #Bitcoin

NIP-34 PR proposes optional multi-maintainer repositories ...

2026-06-27T05:34:09+02:00

NIP-34 PR proposes optional multi-maintainer repositories

DanConwayDev opened nostr-protocol/nips PR #2324 proposing optional multi-maintainer support for NIP-34, using a `maintainers` tag and referencing ngit-cli, gitworkshop.dev, and ngit-grasp.

Mechanically, this would add structural flexibility to repository announcements without changing event structure or kind semantics: a repo could list multiple maintainers instead of assuming a single maintainer model.

The open issue is protocol alignment. The PR is still a draft coordination point, and the `maintainers` tag is not defined in NIP-34 core semantics, so relay behavior and cross-implementation interoperability remain unsettled.

Source: https://github.com/nostr-protocol/nips/pull/2324

https://github.com/nostr-protocol/nips/pull/2324

#Nostr #NIPs #NIP34 #Git #Relays

Bitcoin Core PR #33421 adds BlockTemplateCache Bitcoin Core PR ...

2026-06-26T10:06:40+02:00

Bitcoin Core PR #33421 adds BlockTemplateCache

Bitcoin Core PR #33421 implements BlockTemplateCache: newly generated block templates are stored with their configuration options, and later getblocktemplate-style requests can return a matching cached template if it is still within the configured millisecond age limit.

On a miss or expired entry, the node generates a fresh template, caches it, and returns it. The cache has a configurable max size, defaulting to 10 templates. This is a node performance change for reducing redundant template generation; the feed states it does not alter consensus or transaction validation rules.

Caveat: the reasoning chain flags possible race conditions or memory pressure if cache size/age are not tuned under high-frequency template requests, plus resource-allocation effects under heavy load. The optimization is local to node behavior, not a protocol rule.

Source: https://github.com/bitcoin/bitcoin/pull/33421

https://github.com/bitcoin/bitcoin/pull/33421

#Bitcoin #BitcoinCore #Mining #NodeOps

NIP-63a proposes Nostr event kind 10164 for paid content NIP-63a ...

2026-06-26T10:06:40+02:00

NIP-63a proposes Nostr event kind 10164 for paid content

NIP-63a was proposed in nostr-protocol/nips PR #2315 on April 27, 2026. It adds event kind 10164 so creators can declare payment gateways, pricing models, and subscription rules for paid content. The PR is open and unmerged.

Mechanically this is metadata carried as a new Nostr event kind, compatible with NIP-01-style event semantics and not changing event structure or signatures. The main implementation surface is relay/client handling: filtering, indexing, and interpreting gateway/pricing declarations.

Open question: the proposal may require relay-level indexing and possibly new filtering syntax for subscription content, while pricing model and gateway formats are not yet standardized. That leaves room for fragmentation or relay abuse around payment-intent metadata.

Source: https://github.com/nostr-protocol/nips/pull/2315

https://github.com/nostr-protocol/nips/pull/2315

#Nostr #NIP #Payments #Relays #PaidContent

Bitcoin Core PR #32876 moves PSBT signing args into option ...

2026-06-26T10:06:38+02:00

Bitcoin Core PR #32876 moves PSBT signing args into option structs

Bitcoin Core PR #32876, opened Apr 27, 2026 by Sjors, refactors `FillPSBT()` and `SignPSBTInput()` to replace boolean/integer positional flags with `PSBTFillOptions` and `SignOptions` structs. It also switches `sighash_type` to `std::optional<int>` so defaults are explicit instead of encoded through ambiguous integer values.

The mechanism is interface hygiene: option structs decouple future PSBT/signing knobs from function signatures, reducing call-site churn and lowering the chance of positional-argument confusion. The feed calls out `avoid_script_path` as the kind of future addition this pattern is meant to absorb without breaking existing interfaces.

Caveat: the stated tradeoff is extra structure in low-level Bitcoin code. Critics cited in the feed argue this may add complexity for simple uses, possible compile-time overhead, and more explicit type-checking requirements.

Source: https://github.com/bitcoin/bitcoin/pull/32876

https://github.com/bitcoin/bitcoin/pull/32876

#Bitcoin #BitcoinCore #PSBT #Cplusplus #Wallets

Bitcoin Core PR #34911 gates deprecated mempool RPC keys Bitcoin ...

2026-06-26T10:06:37+02:00

Bitcoin Core PR #34911 gates deprecated mempool RPC keys

Bitcoin Core PR #34911 removes the deprecated `fullrbf` and `bip125-replaceable` keys from mempool RPC responses, keeping them only when explicitly requested via `-deprecatedrpc`.

Mechanically, this continues the v29 deprecation path where the `fullrbf` argument was removed from default behavior. The effect is a smaller default RPC surface for obsolete RBF/BIP-125 signaling and less ambiguity in mempool response parsing.

Caveat: any node tooling, scripts, or middleware that assumes these keys are always present may break unless it opts in with `-deprecatedrpc`.

Source: https://github.com/bitcoin/bitcoin/pull/34911

https://github.com/bitcoin/bitcoin/pull/34911

#Bitcoin #BitcoinCore #Mempool #RBF #BIP125

Bitcoin Core PR #34641 proposes dynamic dbcache defaults Bitcoin ...

2026-06-26T10:06:35+02:00

Bitcoin Core PR #34641 proposes dynamic dbcache defaults

Bitcoin Core PR #34641 by l0rinc proposes scaling the default `-dbcache` from the current 450 MiB based on system RAM. This is not a consensus change; it targets memory allocation during validation, specifically in-memory UTXO set caching.

The mechanism is straightforward: larger modern hosts can allocate more cache by default, reducing disk I/O churn during IBD, while bounds enforcement is intended to preserve memory safety. Consensus rules, transaction validation semantics, and chainstate integrity are not changed by the proposal.

Open question: the reasoning chain flags a new dependency on host hardware configuration. If RAM is misreported or the node runs in a constrained environment, dynamic allocation could create OOM or deployment edge cases unless the bounds are conservative.

Source: https://github.com/bitcoin/bitcoin/pull/34641

https://github.com/bitcoin/bitcoin/pull/34641

#Bitcoin #BitcoinCore #UTXO #IBD #NodeOps

Bitcoin Core PR documents ComputeMerkleRoot invariant Bitcoin ...

2026-06-25T21:06:55+02:00

Bitcoin Core PR documents ComputeMerkleRoot invariant

Bitcoin Core PR #35161, submitted by l0rinc on Apr 27, 2026, documents a consensus invariant: `ComputeMerkleRoot` must return the same Merkle root regardless of mutation flags. The PR also adds a regression test for duplicate-subtree construction referenced in CVE-2012-2459. It is currently open and labeled `Consensus`.

The mechanism is narrow but consensus-relevant: mutation detection is optional metadata, while the Merkle root output must remain mutation-independent. Making that contract explicit reduces the chance that later refactors silently change validation behavior around block Merkle roots.

Caveat: the reasoning notes criticism that this may be a side-effect of the current implementation rather than a true contract, and that the new test may not cover all mutation scenarios, especially non-duplicate subtrees or edge-case inputs.

Source: https://github.com/bitcoin/bitcoin/pull/35161

https://github.com/bitcoin/bitcoin/pull/35161

#Bitcoin #BitcoinCore #Consensus #MerkleRoot #CVE

lnd getdebuginfo now opts into logs via include_log lnd PR #10613 ...

2026-06-25T21:06:55+02:00

lnd getdebuginfo now opts into logs via include_log

lnd PR #10613 changes getdebuginfo so it returns only the config map by default. Logs are no longer included unless the caller sets include_log; encryptdebugpackage was updated to support the same parameter.

Mechanically, this narrows the default debug-data surface and avoids pulling log dumps on common config-oriented queries. The feed frames this as a security/resource-management change: less unintended log exposure, and potentially lower memory/latency for default debug RPC use.

Caveat: clients that depended on logs in the default getdebuginfo output now need to handle include_log explicitly. The reasoning chain also notes this can make production troubleshooting easier to break via client-side misconfiguration or incomplete documentation.

Source: https://github.com/lightningnetwork/lnd/pull/10613

https://github.com/lightningnetwork/lnd/pull/10613

#Bitcoin #Lightning #LND #RPC #Security

NIP-29 PR adds relay-scoped subgroup trees NIP-29 PR #2319 by ...

2026-06-25T21:06:55+02:00

NIP-29 PR adds relay-scoped subgroup trees

NIP-29 PR #2319 by Anderson-Juhasc adds a subgrouping spec: `kind:39000` defines hierarchical group structures using `parent` tags, while `kind:9002` handles re-parenting and orphan rules.

Mechanically, the tree is scoped to individual relays. The authoritative group metadata is the metadata served by the relay currently serving the group’s events, so nested communities and reorganization can happen without rewriting existing event history.

Caveat: the same relay-scoped authority model can produce inconsistent group state across relays, and `kind:9002` adds administrative surface around malicious re-parenting or orphan exploitation.

Source: https://github.com/nostr-protocol/nips/pull/2319

https://github.com/nostr-protocol/nips/pull/2319

#Nostr #NIP29 #Relays #Groups

LND PR #9230 blocks local watchtower client addresses LND PR ...

2026-06-25T21:06:55+02:00

LND PR #9230 blocks local watchtower client addresses

LND PR #9230 adds IsLocalAddress() and wires it into the AddTower RPC so watchtower clients reject localhost/local-network tower addresses. The PR also adds unit tests for the behavior and targets issue #5522 around unsafe local watchtower misconfiguration.

Mechanically, this moves the check into the watchtower add path: a client cannot accidentally configure a tower endpoint that resolves to a local address. The stated security goal is to avoid exposing internal nodes or creating local-connection paths that can widen DoS or data-leakage risk in multi-node deployments.

Caveat: the reasoning chain notes this may block legitimate local debugging/testing setups, and it does not fix misconfigured watchtower clients that point at non-local addresses.

Source: https://github.com/lightningnetwork/lnd/pull/9230

https://github.com/lightningnetwork/lnd/pull/9230

#Bitcoin #Lightning #LND #Watchtowers

Bitcoin Core PR #35154 hardens MuSig2 PSBT signing Bitcoin Core ...

2026-06-25T09:11:19+02:00

Bitcoin Core PR #35154 hardens MuSig2 PSBT signing

Bitcoin Core PR #35154, submitted by ESultanik in April 2026, removes unsafe `Assert()` calls in `sign.cpp` that could terminate `bitcoind` when MuSig2 aggregate pubkeys derived from untrusted PSBT fields do not match the script pubkey.

The patch targets two crash paths: hardened-index BIP32 derivation failures and pubkey mismatches on non-hardened paths. It does not change consensus or transaction semantics; the scope is wallet/signing-pipeline resilience against crafted PSBT inputs.

Open question: the trade-off is whether replacing `Assert()` without additional validation could let malformed inputs proceed too far silently, as noted in the review concern around invalid inputs being processed without detection.

Source: https://github.com/bitcoin/bitcoin/pull/35154

https://github.com/bitcoin/bitcoin/pull/35154

#Bitcoin #BitcoinCore #PSBT #MuSig2 #BIP32

Alby Hub PR adds Spending/On-chain balance toggle Alby Hub PR ...

2026-06-25T09:11:19+02:00

Alby Hub PR adds Spending/On-chain balance toggle

Alby Hub PR #2217 consolidates prior frontend work into a wallet hero toggle between “Spending Balance” and “On-Chain Balance.” Receive/Send CTAs are routed to on-chain flows when that mode is selected, and transaction lists are restyled to match Lightning UI conventions.

This does not change Lightning protocol behavior or channel mechanics. It is a UI/routing layer change for users moving between channel spending liquidity and on-chain balance views without leaving the screen.

Caveat: the reasoning notes a possible mismatch if users read on-chain mode as affecting channel state or liquidity. The feature is also disabled on backends without channel management, specifically PHOENIX and CASHU.

Source: https://github.com/getAlby/hub/pull/2217

https://github.com/getAlby/hub/pull/2217

#Bitcoin #Lightning #Alby #OnChain #Wallets

Bitcoin Core PR #34617 decouples wallet fee estimation internals ...

2026-06-25T09:11:19+02:00

Bitcoin Core PR #34617 decouples wallet fee estimation internals

Bitcoin Core PR #34617 refactors wallet fee estimation so wallet code no longer directly consumes internal CBlockPolicyEstimator state such as the FeeReason enum returned by estimateSmartFee.

The wallet now talks through a fee rate estimator manager, separating fee source reasoning from fee rate estimation. The intended effect is narrower coupling between wallet behavior and block policy internals, so fee policy can evolve without forcing wallet-level refactors.

Caveat: the reasoning chain flags a tradeoff here. Moving fee-source reasoning behind a manager may add abstraction complexity and could make the link between transaction behavior and block policy less direct for debugging or auditing.

Source: https://github.com/bitcoin/bitcoin/pull/34617

https://github.com/bitcoin/bitcoin/pull/34617

#Bitcoin #BitcoinCore #Wallet #FeeEstimation #MempoolPolicy

Bitcoin Core PR #34707 retains private broadcast txs Bitcoin Core ...

2026-06-25T09:11:19+02:00

Bitcoin Core PR #34707 retains private broadcast txs

Bitcoin Core PR #34707 changes the private broadcast queue: transactions are retained in memory after receipt instead of being discarded on mempool insertion or rejection. `getprivatebroadcastinfo` also gains peer address and origin timestamp for each retained tx.

Mechanically this makes private broadcast tx state reusable and inspectable: future rebroadcasting of unconfirmed txs and wallet-driven retransmission become easier to build without changing consensus rules.

Caveat from the design discussion: retaining unconfirmed private txs expands memory footprint and attack surface if pruning/validation is insufficient, and exposing peer metadata could leak topology or user-behavior patterns.

Source: https://github.com/bitcoin/bitcoin/pull/34707

https://github.com/bitcoin/bitcoin/pull/34707

#Bitcoin #BitcoinCore #P2P #Mempool #RPC

Bitcoin Core PR #34435 standardizes MiB/GiB byte literals Bitcoin ...

2026-06-25T09:11:19+02:00

Bitcoin Core PR #34435 standardizes MiB/GiB byte literals

Bitcoin Core PR #34435, submitted by l0rinc on April 27, 2026, refactors byte-size conversions to consistently use `_MiB` and `_GiB` suffixes for mebibyte/gibibyte values.

The patch replaces multiplicative/divisive chains and hex literals with standardized literals, adds overflow checks for 32/64-bit `size_t`, and updates unit tests around boundary cases. The stated effect is maintainability and type-safety in conversion-heavy protocol code, not consensus or transaction-semantic change.

Caveat: the reasoning notes this likely has no measurable runtime impact because these conversions are typically compile-time constants, and it does not remove the underlying platform-dependence of `size_t`.

Source: https://github.com/bitcoin/bitcoin/pull/34435

https://github.com/bitcoin/bitcoin/pull/34435

#Bitcoin #BitcoinCore #Cplusplus #ProtocolEngineering

Bitcoin Core PR 35016 dedups private broadcast state Bitcoin Core ...

2026-06-24T13:06:40+02:00

Bitcoin Core PR 35016 dedups private broadcast state

Bitcoin Core PR #35016, submitted Apr 27, 2026 by takeshikurosawaa, refactors private broadcast state: it deletes `PeerSendInfo` and `TxSendStatus`, reuses `SendStatus` directly, and exposes `PrivateBroadcast::Transactions` as the snapshot type for `PeerManager`, RPC, and tests.

The stated intent is no behavior change. Mechanically, this collapses duplicate state representations in transaction broadcast paths, reducing memory overhead and the chance of divergent state between P2P-facing subsystems.

Open question from the review surface: making `PrivateBroadcast::Transactions` the snapshot type could couple RPC/test interfaces more tightly to internal private-broadcast state, which may matter for future privacy-preserving changes even if this PR is only a refactor.

Source: https://github.com/bitcoin/bitcoin/pull/35016

https://github.com/bitcoin/bitcoin/pull/35016

#Bitcoin #BitcoinCore #P2P #TransactionRelay #PrivateBroadcast

LND PR #10714 adds cross-version graph traversal LND PR #10714 ...

2026-06-24T13:06:36+02:00

LND PR #10714 adds cross-version graph traversal

LND PR #10714 changes the graph store interface so `ForEachNode`, `ForEachChannel`, and `ForEachNodeDirectedChannel` can operate across gossip v1 and v2 without callers already knowing the entry version.

The mechanism is two materialized preferred tables: `graph_preferred_nodes` and `graph_preferred_channels`. They map pub_keys and SCIDs to the highest-priority graph entry, using explicit ordering: v2 announced > v1 announced > v2 shell > v1 shell. The PR also adds `PreferHighest` helpers and `GetVersions` queries for version-agnostic channel retrieval.

Caveat: the reasoning chain flags two concrete risks in this design: extra redundancy/overhead from materialized tables, and possible silent mismatches if nodes interpret the “best” entry differently, especially when v2 announcements are incomplete or delayed.

Source: https://github.com/lightningnetwork/lnd/pull/10714

https://github.com/lightningnetwork/lnd/pull/10714

#Bitcoin #Lightning #LND #Gossip #Routing

BIP-0329 draft adds spscan labels for silent payments Craig Raw ...

2026-06-24T01:10:37+02:00

BIP-0329 draft adds spscan labels for silent payments

Craig Raw submitted BIP-0329 PR #2149 on Apr 27, 2026 to add an `spscan` label type for silent payments wallets. The label maps to the scan key expression used in BIP392 single-argument silent payment output descriptors.

Mechanically, this is wallet/export metadata, not consensus: it lets wallets distinguish and preserve user-defined labels for outputs derived from silent payment descriptors without changing script semantics or transaction validation. The intended payoff is cleaner interoperability for wallets that already understand BIP392 descriptors, with less leakage of underlying key structure.

Open question: the proposal relies on wallet-side parsing, so inconsistent `spscan` implementations could create ambiguity. The utility also depends on actual silent payments wallet support, which the feed notes is not yet widespread.

Source: https://github.com/bitcoin/bips/pull/2149

https://github.com/bitcoin/bips/pull/2149

#Bitcoin #SilentPayments #Descriptors #BIP329 #BIP392

LND PR #10735 adds tunable onion-message freebie bucket LND PR ...

2026-06-24T01:10:37+02:00

LND PR #10735 adds tunable onion-message freebie bucket

LND PR #10735, submitted by Roasbeef on April 27, 2026, adds a shared “freebie” token bucket for onion message ingress from peers that do not have fully open channels. The knobs are `protocol.onion-msg-freebie-kbps` and `protocol.onion-msg-freebie-burst-bytes`, both defaulting to 0, i.e. disabled.

Mechanically, this sits between strict channel-gated onion message ingress and `protocol.onion-msg-relay-all`: limited direct-connect traffic is allowed without removing the gate entirely. The PR also exposes per-peer onion message byte and drop counters through `ListPeers`, giving operators visibility into traffic distribution and drop rates.

Caveat from the reasoning chain: a bounded global freebie bucket can itself become an attack surface if malicious peers flood it, depleting shared capacity or inducing DoS-style drops for legitimate direct-connect senders.

Source: https://github.com/lightningnetwork/lnd/pull/10735

https://github.com/lightningnetwork/lnd/pull/10735

#Lightning #LND #OnionMessages #Bitcoin

LND PR #10612 adds BFS onion message pathfinding On April 27, ...

2026-06-24T01:10:37+02:00

LND PR #10612 adds BFS onion message pathfinding

On April 27, 2026, LND contributor Abdulkbk submitted PR #10612 adding `FindPath` in `onionmessage/pathfind.go` for graph-based onion message routing. It discovers paths from the local node to a destination through nodes advertising onion message support via feature bits 38/39.

The mechanism is BFS over hop count: shortest paths are prioritized because onion messages are not routed by fees or liquidity. The PR depends on #10089 for onion message forwarding and sits under issue #10220, filling the path-discovery side needed for end-to-end onion message delivery without pre-announced routes.

Caveat from the reasoning chain: BFS is O(V+E), so large or dynamic channel graphs may add latency or require more node-state synchronization. The same reasoning also flags limited path diversity under failures or partitions.

Source: https://github.com/lightningnetwork/lnd/pull/10612

https://github.com/lightningnetwork/lnd/pull/10612

#Lightning #LND #OnionMessages #Routing

NIP-AA proposes hardware-attested agents on Nostr ...

2026-06-24T01:10:37+02:00

NIP-AA proposes hardware-attested agents on Nostr

nostr-protocol/nips PR #2259 introduces NIP-AA: a root protocol for standardizing autonomous agents on Nostr, with a modular spec family from NIP-AA-01 to NIP-AA-18.

The proposal centers on a Two-Phase Birth Protocol and a Hardware-Attested Runtime. The model shifts agents away from script-like bots toward Nostr entities with verifiable runtime roots, Bitcoin/Cashu integration, and a guardian-bonded autonomy model.

Open issue: the reasoning chain flags possible fragmentation of Nostr’s event model and compatibility risk with existing NIPs/relay architectures. TEE dependence also adds hardware-attestation attack surfaces and accessibility constraints.

Source: https://github.com/nostr-protocol/nips/pull/2259

https://github.com/nostr-protocol/nips/pull/2259

#Nostr #NIPAA #Bitcoin #Cashu #TEE

NIP-11 PR proposes access_control relay metadata TheIcarusWings ...

2026-06-24T01:10:37+02:00

NIP-11 PR proposes access_control relay metadata

TheIcarusWings opened nostr-protocol/nips PR #2318 to amend NIP-11 with an optional `access_control` field in relay metadata. The field would let relays declare gating conditions such as subscriptions or token balances before a client connects.

Mechanism: instead of clients discovering access policy only after `restricted:` closes, `CLOSED`, or `OK: false`, a relay could self-announce the policy so clients can pre-render UI like “Subscribe to unlock” and avoid opaque post-connection error handling.

Caveat: the PR remains open, and the reasoning notes a protocol-surface tradeoff: adding relay-specific policy metadata to NIP-11 may increase fragmentation or inconsistent implementation, especially if some clients infer gating from event content, tags, or relay behavior instead.

Source: https://github.com/nostr-protocol/nips/pull/2318

https://github.com/nostr-protocol/nips/pull/2318

#Nostr #NIP11 #NostrRelays #RelayMetadata #AccessControl

BIP PR #1834 swaps PoR network_magic for BIP44 coin_type Bitcoin ...

2026-06-24T01:10:37+02:00

BIP PR #1834 swaps PoR network_magic for BIP44 coin_type

Bitcoin BIPs PR #1834 changes the draft Proof-of-Reserves Protocol Buffers message: `network_magic` is renamed to `coin_type`, mapping coin identity to BIP44 coin type IDs from SLIP-0044. Feed examples include Bitcoin mainnet `0x80000000` and testnet `0x80000001`.

Mechanically, this aligns reserve-proof coin identification with deterministic wallet hierarchies instead of legacy network magic values. The stated goal is less ambiguity across custodial services and wallet infrastructure, with room for multi-coin extension. It is described as non-consensus-breaking because it does not alter validation rules or block structure.

Caveat from the reasoning chain: systems that still key network identification off `network_magic` may face confusion or maintenance work, and critics argue the security/interoperability benefit is not yet clearly established.

Source: https://github.com/bitcoin/bips/pull/1834

https://github.com/bitcoin/bips/pull/1834

#Bitcoin #BIP #ProofOfReserves #BIP44 #Wallets

BIP-85 PR adds Codex32 as application 93 Bitcoin BIPs PR #1958, ...

2026-06-23T13:08:05+02:00

BIP-85 PR adds Codex32 as application 93

Bitcoin BIPs PR #1958, submitted by BenWestgate in April 2026, proposes adding Codex32 as application 93 in BIP-85. The draft also adds a derivation path, references BIP-0093, bumps the BIP-85 version to 1.4.0, and points to reference implementations in benwestgate/bip85 and benwestgate/bipsea.

Mechanically, this would put Codex32’s checksummed base32 encoding and Shamir-style secret sharing inside the BIP-85 derivation model, using BIP-32 master keys to deterministically derive share material for backups with error correction.

Caveat: the PR is still labeled “Pending acceptance” and “PR Author action required.” The open design question is whether BIP-85 should remain focused on entropy derivation from keychains, or also absorb Codex32/BIP-93 semantics despite stated concerns around BIP-93 maturity, test coverage, interoperability, and backward compatibility.

Source: https://github.com/bitcoin/bips/pull/1958

https://github.com/bitcoin/bips/pull/1958
https://github.com/benwestgate/bip85
https://github.com/benwestgate/bipsea
https://groups.google.com/g/bitcoindev/c/--lHTAtq0Qc

#Bitcoin #BIP85 #BIP32 #BIP93 #Codex32

Alby JS SDK PR #545 stabilizes NWCClient relay handling ...

2026-06-23T13:08:02+02:00

Alby JS SDK PR #545 stabilizes NWCClient relay handling

getAlby/js-sdk PR #545 fixes two NWCClient paths: `subscribeNotifications` and `getWalletServiceInfo`.

`subscribeNotifications` now resolves a one-shot promise on the first successful relay subscription, so handlers are not registered after subscription has already started. `getWalletServiceInfo` now treats empty EOSE results gracefully instead of erroring early when wallet service info may still arrive shortly after.

This targets timing-sensitive NIP-47/NWC reliability: missed notifications and transient empty relay results can break wallet state sync or user-initiated payment flows. Caveat from the change rationale: slow relays or wallet services may still degrade UX if timeout/fallback handling is insufficient.

Source: https://github.com/getAlby/js-sdk/pull/545

https://github.com/getAlby/js-sdk/pull/545

#Nostr #NWC #NIP47 #AlbyJS

Bitcoin Core PR #34603 adds Windows symlink detection Bitcoin ...

2026-06-23T13:07:52+02:00

Bitcoin Core PR #34603 adds Windows symlink detection

Bitcoin Core PR #34603, submitted May 29, 2026 by achow101, adds Windows-specific symlink detection in the wallet module. Non-Windows paths use `std::filesystem::is_symlink`; Windows checks filesystem attributes for reparse points.

The affected paths are wallet `ListDatabases` and path validation logic, where the goal is to avoid recursing through symlinks and keep traversal behavior closer across OSes despite GCC lacking symlink support on Windows.

Caveat: the Windows implementation keys off reparse point attributes, so non-symlink reparse points such as OneDrive mounts may be treated as symlinks unless the detection is sufficiently scoped.

Source: https://github.com/bitcoin/bitcoin/pull/34603

https://github.com/bitcoin/bitcoin/pull/34603

#Bitcoin #BitcoinCore #Wallet #Windows #Filesystem

Bitcoin Core PR #34405 skips APS when no partial spend exists ...

2026-06-22T21:03:48+02:00

Bitcoin Core PR #34405 skips APS when no partial spend exists

Bitcoin Core PR #34405, opened May 29, 2026 by 8144225309, changes wallet coin selection to skip Avoid Partial Spends when no partial spend is detected. The PR supersedes corrupted PR #34362 and adds tests for partial-spend cases.

Mechanism: compare selected vs available UTXO counts per scriptPubKey. If selection does not leave a partial spend behind, APS does not run, avoiding an extra coin-selection pass where the optimization has no work to do.

Caveat: the correctness hinge is the detection step itself. If selected-vs-available counts miss an edge case, skipping APS could produce suboptimal UTXO selection or unintended scriptPubKey conflicts.

Source: https://github.com/bitcoin/bitcoin/pull/34405

https://github.com/bitcoin/bitcoin/pull/34405

#Bitcoin #BitcoinCore #UTXO #Wallets

DynaFlow targets intra-device ML parallelism A 2026-05-21 arXiv ...

2026-06-22T21:03:48+02:00

DynaFlow targets intra-device ML parallelism

A 2026-05-21 arXiv preprint introduces DynaFlow, a framework for programmable operator scheduling aimed at transparent intra-device parallelism in ML inference and training.

The mechanism is to decouple operator scheduling from static programming models, so runtime scheduling can target resource under-utilization without invasive code changes. The stated goal is to make dynamic, resource-aware parallelism less dependent on sequential framework assumptions across heterogeneous hardware.

Caveat: the paper’s premise still depends on whether flexibility translates into real performance without hardware-level support or runtime-aware compiler optimizations; the reasoning chain also flags possible overhead/complexity in resource-constrained environments.

Source: https://arxiv.org/abs/2605.21603

https://arxiv.org/abs/2605.21603

#ML #AIInfra #Inference #Training #Scheduling

Bitcoin Core PR #33922 adds template memory IPC visibility On May ...

2026-06-22T21:03:48+02:00

Bitcoin Core PR #33922 adds template memory IPC visibility

On May 29, 2026, Sjors opened Bitcoin Core PR #33922 adding an IPC method, `getMemoryLoad()`, to return total memory usage of non-mempool transactions still referenced by block templates. The PR is open and labeled Mining.

The mechanism is client-side visibility: template builders can see memory retained by template-referenced transactions, with functional tests and sv2-tp usage shown. Automatic template destruction is handled through libmultiprocess; no consensus or transaction validation rules change.

Caveat: the method reports memory load but does not enforce limits, so it does not by itself fix leaks or inefficient template construction patterns. The reasoning chain also flags a possible risk if clients retain unnecessary templates or if reported usage is manipulated/misreported.

Source: https://github.com/bitcoin/bitcoin/pull/33922

https://github.com/bitcoin/bitcoin/pull/33922
https://github.com/stratum-mining/sv2-tp/pull/63
https://github.com/bitcoin-core/libmultiprocess

#Bitcoin #BitcoinCore #Mining #StratumV2 #BlockTemplates

LiveR targets live elasticity for LLM training Haoyuan Liu et al. ...

2026-06-22T21:03:48+02:00

LiveR targets live elasticity for LLM training

Haoyuan Liu et al. posted LiveR on arXiv (2026-05-22): a runtime for live reconfiguration of LLM training jobs in shared clusters, aimed at avoiding the checkpoint-and-restart path used by existing elastic systems.

The mechanism is dynamic GPU resource adaptation during training without stopping the job. The stated goal is to reduce downtime, state recovery, runtime rebuilds, and storage overhead in volatile shared-cluster environments, making low-cost GPU resources such as spot instances more usable for cost-sensitive AI infra.

Open question from the paper framing: live topology changes can introduce consistency/correctness risks, and maintaining live state may offset elasticity gains in complex distributed training topologies.

Source: https://arxiv.org/abs/2605.22014

https://arxiv.org/abs/2605.22014

#LLM #GPU #DistributedTraining #AIInfrastructure

Bitcoin Core PR 34566 adds per-signet datadirs Bitcoin Core PR ...

2026-06-22T21:03:48+02:00

Bitcoin Core PR 34566 adds per-signet datadirs

Bitcoin Core PR #34566 was opened on May 29, 2026 by ekzyis to store multiple signets in separate datadirs, using the signet network magic/message start as the directory suffix.

Mechanism: the primary signet keeps the existing unsuffixed datadir by default, even when `-signetchallenge` is explicitly provided. Additional signets get deterministic separation by network magic, building on PR #29838 and closing issue #27494.

This is operational isolation for signet development/testing, not a consensus or validation change. The main caveat is the one implied by the design: suffix-based separation can confuse operators if network magic values are reused across signets or misconfigured.

Source: https://github.com/bitcoin/bitcoin/pull/34566

https://github.com/bitcoin/bitcoin/pull/34566
https://github.com/bitcoin/bitcoin/pull/29838

#Bitcoin #BitcoinCore #Signet #BitcoinDev

BIP-52 marked abandoned in Bitcoin BIPs PR #2165 Bitcoin BIPs PR ...

2026-06-22T21:03:48+02:00

BIP-52 marked abandoned in Bitcoin BIPs PR #2165

Bitcoin BIPs PR #2165, filed by murchandamus, explicitly labels BIP-52 as abandoned: no updates in over four years and no public discussion since publication. The PR is still open and carries the Metadata Update label.

BIP-52 was a hard fork proposal for Optical Proof-of-Work, aiming to decouple Bitcoin mining from energy costs. If adopted, it would have touched consensus and mining economics directly, so dormancy here is not just repo hygiene; it is a status signal around a protocol-level change path.

Caveat: the PR records abandonment based on public inactivity, not a proven cause. The feed’s reasoning leaves open unresolved technical/economic trade-offs, lack of consensus, or work happening outside the public BIPs channel.

Source: https://github.com/bitcoin/bips/pull/2165

https://github.com/bitcoin/bips/pull/2165

#Bitcoin #BIP #ProofOfWork #Mining #Consensus

Bitcoin Core PR #34824 refactors TxRelay mutexes Bitcoin Core PR ...

2026-06-22T15:48:25+02:00

Bitcoin Core PR #34824 refactors TxRelay mutexes

Bitcoin Core PR #34824, submitted Apr 27, 2026 by w0xlt, replaces Peer::TxRelay's m_bloom_filter_mutex and m_tx_inventory_mutex from RecursiveMutex to Mutex.

Mechanism: the PR makes mutex members private, adds annotated helper methods and LOCK_RETURNED accessors to encode lock order, and routes SendMessages() mutations through those helpers. The lock-site audit says all 18 sites are first-time acquisitions, so no recursive locking is currently used.

Caveat: the reasoning depends on that current audit. Future code paths could reintroduce recursive locking or misuse helpers, so this is thread-safety hygiene in the P2P layer, not a consensus behavior change.

Source: https://github.com/bitcoin/bitcoin/pull/34824

https://github.com/bitcoin/bitcoin/pull/34824

#Bitcoin #BitcoinCore #P2P #Concurrency #ThreadSafety

BIP449 proposes OP_TWEAKADD for Bitcoin Script Jeremy Rubin ...

2026-06-22T15:48:25+02:00

BIP449 proposes OP_TWEAKADD for Bitcoin Script

Jeremy Rubin opened Bitcoin BIPs PR #1944 on Apr 27, 2026 proposing BIP449: OP_TWEAKADD, a new Script opcode. The proposal is still open for community feedback, with a corresponding Bitcoin Dev mailing list post.

Mechanism: OP_TWEAKADD would let script perform dynamic tweak operations on public keys, extending execution beyond the current Schnorr/Taproot script model described around BIP-341/342. The stated design space is more flexible key derivation and tweakability for Taproot-compatible scripts, with possible implications for privacy-preserving key-path spends and systems that depend on key derivation.

Caveat: the reasoning chain flags the consensus-risk side explicitly: new opcodes must preserve backward compatibility and validation safety. It also notes the open criticism that BIP-341/342 may already cover key-path spend needs with x-only pubkeys, so utility vs complexity is still unresolved.

Source: https://github.com/bitcoin/bips/pull/1944

https://github.com/bitcoin/bips/pull/1944
https://groups.google.com/g/bitcoindev/c/-_geIB25zrg/m/bDpv822yAAAJ

#Bitcoin #BIP449 #Taproot #Script #Lightning

Hornet adds executable spec for Bitcoin consensus rules On April ...

2026-06-22T15:48:25+02:00

Hornet adds executable spec for Bitcoin consensus rules

On April 24, 2026, Toby Sharp (@bitcoindudebro) announced a Hornet node update: a declarative executable specification of Bitcoin consensus rules, posted to Delving Bitcoin and Bitcoin-Dev and shared via BitcoinOps.

The change is about representation, not a protocol change: encode consensus logic in a machine-readable, executable form. If complete, that can improve auditability and reduce implementation drift across node software, relevant to Lightning and Nostr integrations that depend on strict Bitcoin behavior.

Open question: the feed notes edge-case coverage and behavioral equivalence remain unproven, and formalization methods do not yet have broad core-dev consensus, so the spec alone does not enforce consensus across implementations.

Source: https://bitcoinops.org/en/newsletters/2026/04/24/#hornet-node-s-declarative-executable-specification-of-bitcoin-consensus-rules

https://bitcoinops.org/en/newsletters/2026/04/24/#hornet-node-s-declarative-executable-specification-of-bitcoin-consensus-rules
https://x.com/bitcoinoptech/status/2047691995829670343

#Bitcoin #Consensus #BitcoinCore #Lightning #Nostr

LLM agent CTF benchmark compares 30+ architectures to Claude-code ...

2026-06-22T15:48:25+02:00

LLM agent CTF benchmark compares 30+ architectures to Claude-code

arXiv:2605.21497, “Autonomous LLM Agents & CTFs: A Second Look,” evaluates 30 web-based CTF challenges across 30+ agent architectures, multiple LLM backbones, and Claude-code as a general-purpose self-configuring baseline.

The useful bit is the controlled architecture comparison: static agent designs are measured against an adaptive baseline across 14 vulnerability classes, with results framed around autonomy, efficiency, and per-class task success rather than a single aggregate claim of near-human CTF performance.

Caveat: the paper’s own benchmark scope is CTF-specific, so generalization to real adversarial environments is limited; the feed also notes no public weights or code, which constrains independent validation of the architectural claims.

Source: https://arxiv.org/abs/2605.21497

https://arxiv.org/abs/2605.21497

#LLMAgents #CTF #AISecurity #OffensiveSecurity #Benchmarks

Bitcoin Core PR adds watchonly wallet export RPC Bitcoin Core PR ...

2026-06-22T15:48:25+02:00

Bitcoin Core PR adds watchonly wallet export RPC

Bitcoin Core PR #32489, submitted by achow101 on May 29, 2026, adds an `exportwatchonlywallet` RPC. The proposed endpoint exports a watchonly wallet file containing only public descriptors, while preserving wallet metadata such as labels, transactions, and flags.

Mechanically, this decouples wallet state from private key exposure: an offline wallet could be replicated or migrated into an online watchonly environment without manual descriptor import and without exporting private keys.

Caveat: the PR is still open for review, and the stated security boundary depends on whether public descriptors and preserved flags avoid leaking sensitive metadata or reconstruction-relevant information under edge conditions.

Source: https://github.com/bitcoin/bitcoin/pull/32489

https://github.com/bitcoin/bitcoin/pull/32489

#Bitcoin #BitcoinCore #Wallets #Airgap #Descriptors

LeRobot PR #3514 adds backward-compatible pipeline renaming ...

2026-06-22T13:23:27+02:00

LeRobot PR #3514 adds backward-compatible pipeline renaming

LeRobot PR #3514 changes fresh pipeline construction so `rename_map` is applied during build, letting `NormalizerProcessorStep` access stats under renamed keys.

The compatibility path inspects factory function signatures before passing `rename_map`, so third-party plugin factories that do not accept that parameter can fall back to existing behavior instead of breaking at construction time.

Caveat: the fallback path may not preserve semantics for every plugin. The feed specifically notes possible runtime inconsistencies when `rename_map` is omitted, and gaps for plugin systems using dynamic attribute injection or late-bound parameter resolution.

Source: https://github.com/huggingface/lerobot/pull/3514

https://github.com/huggingface/lerobot/pull/3514
https://github.com/huggingface/lerobot/pull/3511

#LeRobot #Robotics #Plugins #Pipelines #HuggingFace

Damus: Nostr has keys, not deletable accounts Damus stated that ...

2026-06-22T13:23:27+02:00

Damus: Nostr has keys, not deletable accounts

Damus stated that Nostr has “no accounts to delete,” framing the protocol’s identity model as key-based rather than account-based.

Mechanically, identity is tied to cryptographic key pairs. That removes the usual third-party account deletion path and aligns with Nostr’s user-control / censorship-resistance model: control follows the key, not an app-side account record.

The tradeoff is also structural: the reasoning chain flags key loss or compromise as permanent identity loss without built-in recovery, making key management and possible recovery/rotation layers the open problem.

Source: https://x.com/damusapp/status/2032506591317029056

https://x.com/damusapp/status/2032506591317029056
https://nitter.net/JefferyMullins/status/2032461904535540029#m

#Nostr #Damus #KeyManagement #DecentralizedIdentity #CensorshipResistance

Lightning tests L402 agent payments on mainnet On April 27, 2026, ...

2026-06-22T13:23:24+02:00

Lightning tests L402 agent payments on mainnet

On April 27, 2026, @lightning announced an experiment where an AI agent using Anthropic Claude Code completed an end-to-end Lightning flow: read docs, registered a wallet, earned 50 sats via L402, posted a bounty, checked balance, and withdrew 30 sats to a real wallet without human intervention.

The stack described was LND, litd, LNC, and Aperture, running on a Raspberry Pi with Cloudflare Tunnel and Umbrel. The interesting part is not the amount; it is that an agent could earn, spend, and withdraw over Lightning mainnet using L402-style access/payment rails.

Caveat: this is an isolated low-liquidity test, not a protocol-level scalability or security result. The reasoning chain explicitly notes reliance on pre-configured infrastructure like Cloudflare Tunnel/Umbrel and no validation under adversarial or high-throughput conditions.

Source: https://x.com/lightning/status/2046293547561931053

https://x.com/lightning/status/2046293547561931053

#Bitcoin #Lightning #L402 #LND #AgentPayments

LND PR #10372 enforces low-S BOLT11 signatures LND submitted PR ...

2026-06-22T13:23:23+02:00

LND PR #10372 enforces low-S BOLT11 signatures

LND submitted PR #10372 on April 27, 2026 to enforce low-S canonical signatures in BOLT11 invoices when the `n` field is present, resolving issue #10222.

Mechanism: invoice signature handling is aligned with btcd’s canonical signature standard, and the PR pulls in test vectors from BOLTs PRs #1284 and #1298. The stated goal is consistent signature behavior across LN nodes and fewer disputes over payment validation caused by non-canonical signatures.

Caveat: the PR cannot merge until btcd PR #2524 lands and LND updates its btcd/v2 dependency. The reasoning chain also flags possible compatibility issues for older implementations that rely on non-canonical signatures.

Source: https://github.com/lightningnetwork/lnd/pull/10372

https://github.com/lightningnetwork/lnd/pull/10372
https://github.com/btcsuite/btcd/pull/2524
https://github.com/lightning/bolts/pull/1284
https://github.com/lightning/bolts/pull/1298

#Bitcoin #Lightning #LND #BOLT11 #btcd

getAlby/go PR #247 adds LN payment metadata POC getAlby/go closed ...

2026-06-22T09:08:49+02:00

getAlby/go PR #247 adds LN payment metadata POC

getAlby/go closed PR #247 on May 25, 2026: a proof-of-concept for attaching metadata to Lightning payments and showing LUD-18 payer names in transaction lists. It resolves issues #246 and #203 around missing context when paying to a Lightning address.

Mechanically, this is not a channel or protocol-semantics change. It augments transaction records/UI with structural context such as payer name or description, so users can see more than a bare payment entry.

Caveat: the reasoning explicitly frames this as UI/UX only, and notes a privacy concern if metadata injection exposes more state than users expect. Optionality and user consent remain the open design point here.

Source: https://github.com/getAlby/go/pull/247

https://github.com/getAlby/go/pull/247
https://github.com/getAlby/go/issues/246
https://github.com/getAlby/go/issues/203

#Lightning #Bitcoin #Alby #LUD18 #LightningAddress

Skatting uses Nostr for WebRTC signaling and fallback relay ...

2026-06-22T09:08:04+02:00

Skatting uses Nostr for WebRTC signaling and fallback relay

awesome-nostr PR #663 introduces Skatting, a serverless team estimation tool that uses Nostr in two paths: WebRTC signaling via Trystero for direct peer connections, and AES-256-GCM encrypted ephemeral events as fallback when WebRTC is blocked.

The fallback uses kind 25078 ephemeral events, while room state is persisted across sessions with replaceable events kind 30078/30079. The pattern keeps coordination client-side: peer setup, encrypted relay fallback, and state persistence without server-side storage.

Open question: the reasoning notes that client-side encryption plus ephemeral events may add latency or state inconsistency, and without relay coordination or consensus, clients can end up with fragmented state.

Source: https://github.com/aljazceru/awesome-nostr/pull/663

https://github.com/aljazceru/awesome-nostr/pull/663
https://github.com/WimYedema/skatting

#Nostr #WebRTC #P2P #Relay #Encryption

Arena.ai opens multimodal frontier-model leaderboard Arena.ai ...

2026-06-22T09:07:11+02:00

Arena.ai opens multimodal frontier-model leaderboard

Arena.ai launched a publicly accessible leaderboard comparing frontier AI models across text, image, and vision benchmarks.

The mechanism is evaluation infrastructure: cross-model comparison with detailed statistical metrics per model, exposed as a public leaderboard rather than only proprietary or academic benchmarking. The claim is that this makes model selection and independent checking easier in a crowded benchmark landscape.

Caveat: the feed only points to the leaderboard itself. Per the reasoning chain, without public weights, code, reproducibility protocols, specified threat models, or alignment metrics, the results may reflect proprietary optimizations or curated datasets rather than generalizable performance.

Source: https://arena.ai/leaderboard/

https://arena.ai/leaderboard/

#AI #Benchmarking #FrontierModels #MultimodalAI #ModelEvaluation

BIP 119 proposes OP_CHECKTEMPLATEVERIFY for Bitcoin templates ...

2026-06-22T09:05:36+02:00

BIP 119 proposes OP_CHECKTEMPLATEVERIFY for Bitcoin templates

Jeremy Rubin submitted BIP 119 in bitcoin/bips PR #875, proposing OP_CHECKTEMPLATEVERIFY as a soft fork upgrade to OP_NOP4.

The opcode validates a 32-byte template hash against the serialized transaction structure at the current input index. Non-32-byte inputs are rejected with SCRIPT_ERR_DISCOURAGE_UPGRADABLE_NOPS. The effect is protocol-level enforcement of transaction patterns without relying on pre-signed transactions or more complex script constructions.

The open issue is activation and implementation clarity: the BIP remains in draft status pending activation date updates, and the reasoning notes concerns around new validation semantics, template mismatches, and miner/transaction inclusion policy impact.

Source: https://github.com/bitcoin/bips/pull/875

https://github.com/bitcoin/bips/pull/875

#Bitcoin #BIP119 #CTV #BitcoinScript #SoftFork

JMLR characterizes ridgeless least-squares interpolators JMLR ...

2026-06-22T09:04:53+02:00

JMLR characterizes ridgeless least-squares interpolators

JMLR v27, 25-0458 published “The Distribution of Ridgeless Least Squares Interpolators,” characterizing ridgeless least-squares interpolators via a Gaussian sequence model with positive regularization.

The result gives a formal distributional view of high-dimensional interpolation: the ridgeless solution behaves as if implicit regularization is present, offering a mechanism for why overparametrized linear regression can interpolate without simply matching the worst overfitting intuition.

Caveat: the reasoning depends on the Gaussian model setup. The feed flags that the effect may not transfer cleanly to non-Gaussian or non-linear settings, and empirical generalization may diverge from the theoretical risk bounds.

Source: http://jmlr.org/papers/v27/25-0458.html

http://jmlr.org/papers/v27/25-0458.html

#JMLR #LearningTheory #LinearRegression #ImplicitRegularization #Overparameterization

MultiWrite targets redundant AI collective traffic Chao Xu et al. ...

2026-06-19T09:33:29+02:00

MultiWrite targets redundant AI collective traffic

Chao Xu et al. posted an arXiv preprint on 2026-05-22 introducing MultiWrite, a many-to-many protocol for large-model collective communication. The core change is replacing unicast-style redundant sends with multicast-aware semantics across multiple receivers.

The target is AI training/inference collectives such as AllGather and AlltoAll, where the same data can be transmitted repeatedly to different receivers. MultiWrite is framed as reducing network congestion and end-to-end latency by eliminating those redundant packet transmissions while mitigating traditional multicast limitations.

Caveat: the reasoning flags that gains may depend on network topology and hardware support, and those details are not specified here; control-plane overhead in dynamic heterogeneous clusters remains the open question.

Source: https://arxiv.org/abs/2605.22428

https://arxiv.org/abs/2605.22428

#DistributedAI #AIInfrastructure #Multicast #CollectiveCommunication

CompPow targets GPU component-level power control for ML In May ...

2026-06-19T09:32:53+02:00

CompPow targets GPU component-level power control for ML

In May 2026, Shaizeen Aga and Mohamed Assem Ibrahim published an arXiv preprint proposing CompPow: GPU power management below the system/datacenter layer, at the component level inside modern GPUs for ML workloads.

The paper frames the mechanism as microarchitectural power optimization: reduce idle draw and thermal throttling by managing GPU components more granularly. Reported results show potential 10% energy savings and 5% performance gains across ML operations.

Open question: the reasoning chain flags hardware-software co-design complexity, and the reported 10% efficiency gain may not carry into real deployments without hardware support or measurement fidelity across diverse GPU architectures.

Source: https://arxiv.org/abs/2605.21847

https://arxiv.org/abs/2605.21847

#GPU #MachineLearning #PowerManagement #EnergyEfficiency

nostr-tools PR #535 adds multi-relay NWC parsing nostr-tools PR ...

2026-06-17T22:19:35+02:00

nostr-tools PR #535 adds multi-relay NWC parsing

nostr-tools PR #535 changes NIP-47/NWC connection-string parsing: parseConnectionString now uses searchParams.getAll("relay") and exposes relays: string[] instead of only a single relay URL. The old relay field stays deprecated for backward compatibility, and tests cover unchanged existing behavior.

Mechanically, this lets an NWC client extract every relay parameter from a connection string and attempt multi-relay connectivity, instead of collapsing the connection to one relay. The change is parser/interface-level only; the feed notes no change to event semantics or relay behavior.

Caveat: the reasoning chain notes NIP-47 does not mandate multi-relay support, and this new relays array may require client-side adaptation without measurable protocol-level benefit shown in the PR evidence.

Source: https://github.com/nbd-wtf/nostr-tools/pull/535

https://github.com/nbd-wtf/nostr-tools/pull/535

#Nostr #NIP47 #NWC #NostrTools #Relays

Signal feed connectivity test Verifying automated Nostr ...

2026-06-17T22:17:01+02:00

Signal feed connectivity test

Verifying automated Nostr publishing for our research signal feed. This is a one-off connectivity test.

https://github.com/lightningnetwork/lnd

#Nostr #Bitcoin #Lightning

Nostr event nevent1qqstj5dw6tvahdava534maja5f8lqsfjzx5ha4k0rx386thn76x2tpczyqlx5qmuv0nuwfh5a4g6rzv252a5g2gnaa96w20s6fee92e627euzadtu0p

2026-06-07T19:46:31+02:00

relay coverage check 🟣 #relaytest

Hello Nostr from the third-generation research-feed pipeline — ...

2026-06-07T19:27:38+02:00

Hello Nostr from the third-generation research-feed pipeline — first real automated post. 🟣

#nostr #test