forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
backport: bitcoin#15584, #16060, #16465, #16477, #16680, #16714, #16941, #16991, #17453, #17696, #19058 (last batch for v19) #5255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
a778ddd
Merge #16477: build: skip deploying plugins we dont use in macdeployq…
fanquake d5d3c3e
Merge #16680: Preparations for more testchains
6ea9349
Merge #16714: gui: add prune to intro screen with smart default
jonasschnelli e75d5b7
Merge #17696: qt: Force set nPruneSize in QSettings after the intro d…
fanquake 78e475a
Merge #17453: gui: Fix intro dialog labels when the prune button is t…
jonasschnelli d4bc451
Merge #15584: build: disable BIP70 support by default
laanwj 3e0160b
Merge #19058: doc: Drop protobuf stuff
fanquake dc5da97
Merge #16941: travis: Disable feature_block in tsan run due to OOM
laanwj 2307f97
Merge #16991: qa: Fix service flag comparison check in rpc_net test (…
laanwj 3e1c8a6
Merge #16465: test: Test p2sh-witness and bech32 in wallet_import_rescan
6ad9bdf
Merge #16060: Bury bip9 deployments
d26b07a
feat: burry DIP0001 deployment to follow-up bitcoin#16060
knst 8457336
feat: burry DIP0008 deployment to follow-up bitcoin#16060
knst File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| Low-level RPC changes | ||
| ---------------------- | ||
|
|
||
| - Soft fork reporting in the `getblockchaininfo` return object has been | ||
| updated. For full details, see the RPC help text. In summary: | ||
| - The `bip9_softforks` sub-object is no longer returned | ||
| - The `softforks` sub-object now returns an object keyed by soft fork name, | ||
| rather than an array | ||
| - Each softfork object in the `softforks` object contains a `type` value which | ||
| is either `buried` (for soft fork deployments where the activation height is | ||
| hard-coded into the client implementation), or `bip9` (for soft fork deployments | ||
| where activation is controlled by BIP 9 signaling). | ||
|
|
||
| - `getblocktemplate` no longer returns a `rules` array containing `CSV` | ||
| (the BIP 9 deployments that are currently in active state). |
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
other deployments have been buried as well no? Should do those in another PR at least