Sync with Upstream#1
Open
2a5A1Ghu1 wants to merge 1271 commits into
Open
Conversation
This commit adds a new boolean field, `V2Connection`, to the `getpeerinfo` RPC result. This field indicates whether the connection to the peer is using the v2 encrypted transport protocol. The `peer.StatsSnap` struct is updated to include this `V2Connection` field, which is populated based on the `UsingV2Conn` field in the peer's configuration. The `btcjson.GetPeerInfoResult` struct is also updated to include the corresponding JSON field `v2_connection`. Finally, the `handleGetPeerInfo` RPC handler is modified to copy this value from the peer's stats snapshot into the RPC response.
In this commit, we refactor the v2 -> v1 downgrade logic to: simplify the code in the server for reconnection, use a functional option to avoid breaking the connmgr API, and we also encapsulate the downgrade state in a new struct so it can be re-used elsewhere.
multi: introduce v2transport and implement BIP324
In this commit, we reduce the size of the v2transport module by shedding the dep on the wire package. This allows us to only depend on btcec/v2, which itself is a sub module, instead of the entire btcd module.
…ow-bug psbt: overflow checks when computing Taproot BIP32 derivation min size
v2transport: update to btcec v2.3.5, reduce module deps
In this commit, we fix the module path for the new `v2transport` package. It needs the repo prefix (btcsuite/btcd).
v2transport: fix module path
build: remove replace directives left over after BIP 324 PRs
In this commit, we add more detail to the invalid tapscript merkle proof error. Before this commit, the error was blank, making such a case hard to debug. We'll now log the expected witness program, what we derived, and also the passed in tapscript root.
txscript: add more detail to invalid tapscript merkle proof error
This commit provides a minor fix on the format.
A minor refactor on method `OnGetData`.
The preivous usage of two channels - by piping them together to create a semaphore effect, is difficult to follow and prone to bugs. This commit now refactors the method to explicitly implement a semaphore. Prior to this change, we would allow at max 3 concurrent goroutines - this is now bumped to 5.
Minor refactor to improve code health
rpcclient: clarify GetBlockCount description
Print a readable error before os.Exit(1) in btcctl
CI: add gemini assist for code reviews
In this commit, we drop the rc1 pre-release suffix, taking the version from v0.26.0-beta.rc1 to v0.26.0-beta for the final release.
version: bump to v0.26.0-beta for final release
multi: reject trailing characters when parsing inputs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.