Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.
This is a large dependency upgrade for the LND Lightning node software. It moves LND from older btcd Bitcoin library packages to new 'v2' packages and updates related wallet and network libraries. The commit is almost entirely mechanical i…
Large dependency upgrade touching core Bitcoin primitives (wire, txscript, chainhash, btcutil, psbt, address)Migration to new v2 module layout with API changes in address handlingPins new upstream releases (btcd 0.26.0, btcwallet 0.17.0, neutrino 0.18.0, lightning-onion 1.4.0) that may include undisclosed fixes
This commit fixes a bug in btcd's test-network synchronization logic. A previous change accidentally allowed light clients (such as Neutrino wallets) to be chosen as sync peers on regtest/simnet. Because light clients advertise a recent bl…
Denial-of-service via sync livelock on regtest/simnetLight client eligible as sync peer due to missing service-flag checkPeer service flags not validated before sync election on test networks
This commit updates the software's dependency list for the Tor-related sub-package, bumping the btcd library from version 0.24.2 to a newer pre-release (0.26.0-beta.rc1) along with several supporting libraries. There are no actual code cha…
Dependency version bump for a core Bitcoin library (btcd) used in Tor integrationTransitive update of networking and cryptography libraries (golang.org/x/net, golang.org/x/crypto)No source code changes or patch logic visible in the commit
This is a routine dependency update for a small internal module of the LND Lightning node software. It switches from an older monolithic btcd package to newer, versioned submodules and updates a few related libraries. There is no indicatio…
This commit only updates user-facing documentation. It replaces hardcoded block heights with a new 'latest' shortcut URL for a third-party header-import service and removes an outdated warning about a broken testnet3 file. No code was chan…
This commit only changes build, test, and continuous-integration configuration files. It adds new Go packages to the test/coverage targets and updates how coverage report files are cleaned up. There is no change to the actual Bitcoin node …
This commit simply deletes two helper functions that were no longer being used anywhere in the code. It is a routine cleanup to silence a linter warning. There is no security issue here.
This is a one-line code cleanup that silences a Go linter warning by explicitly discarding the return value of a function call. It does not change program behavior or fix any security issue.
This is a large, routine refactoring commit. It updates the btcd project to use new 'v2' versions of its own Go modules (such as btcutil/v2, chaincfg/v2, wire/v2, txscript/v2, and a newly split-out address/v2 package) across the entire cod…
This commit is a routine code reorganization: it moves the PSBT (Partially Signed Bitcoin Transaction) package from a nested location under btcutil to a top-level module, updates internal import paths to use v2 module versions, and removes…
This commit is a routine internal restructuring of the btcd project's Go module layout. It switches the btcutil package and its subpackages from the old module path to a new 'v2' path, and updates imports throughout the code to point at ne…
This commit is a routine code reorganization: it splits the Bitcoin transaction-script library (txscript) into its own Go module and updates all internal references to use new v2 versions of related packages. There are no visible security …
No security-relevant signal: pure modularization and import-path migrationDependency on new address/v2 package introduced; behavior equivalent to prior btcutil address typesTest-only reimplementation of btcutil helpers to avoid import cycle
This commit is a routine Go module restructuring: it makes the chaincfg package its own versioned module (chaincfg/v2) and updates its internal imports to use versioned chainhash/v2 and wire/v2 modules. There are no code logic changes, no …
This commit is a routine Go module restructuring: it makes the `wire` package its own standalone Go module and updates its import path to version 2 (`github.com/btcsuite/btcd/wire/v2`). It also updates internal imports of the `chainhash` p…
This commit is a routine dependency update inside the btcd cryptocurrency project. It changes the btcec cryptographic package to use a newer version (v2) of the internal chainhash module instead of the older v1 path. No security bug is fix…
This commit is a large code reorganization: it moves the Bitcoin address-handling code into its own top-level Go module and upgrades its internal import path to version 2. The actual address/base58/bech32 logic appears to be copied over la…
Large refactor with no security-relevant commit messageNew address type added (P2A / pay-to-anchor)No changes to checksum, length, or validation logic visible in supplied diff
This commit is a pure refactoring move: the chainhash package is relocated from `chaincfg/chainhash` to a top-level `chainhash` directory and its Go module path is bumped to `github.com/btcsuite/btcd/chainhash/v2`. The actual source code, …
This commit changes how the btcd RPC client parses JSON string responses. Instead of using a full JSON parser to extract quoted strings, it now uses a custom helper that strips the surrounding quote characters directly. The stated goal is …
Removal of standard JSON parsing in favor of a custom string-stripping helperPotential acceptance of malformed or non-JSON input if the helper is naiveParsing of server-controlled hex data without intermediate validation
This commit adds a new client method to request and decode a Bitcoin proof that a transaction was included in a block. It also adds a small helper that strips surrounding quote characters from a JSON string response instead of fully parsin…
New RPC client helper parses JSON string by trimming quotes rather than unmarshallingParsing shortcut could mishandle escaped characters or malformed JSON, but only affects client-side decoding of a trusted RPC responseNo bounds checks or validation added around the trimmed payload length
This commit only adds a documentation hint showing which lncli command maps to the SignPsbt API. It changes comments in a .proto file, a generated swagger JSON file, and generated Go gRPC code. There is no functional code change and no sec…