Backport missing PRs from Bitcoin 0.13 - Part 1#1770
Merged
UdjinM6 merged 58 commits intodashpay:developfrom Dec 19, 2017
Merged
Backport missing PRs from Bitcoin 0.13 - Part 1#1770UdjinM6 merged 58 commits intodashpay:developfrom
UdjinM6 merged 58 commits intodashpay:developfrom
Conversation
aa3d93f to
2d81191
Compare
Got added due to wrong merge conflict resolution
086ee67 Switch to a more efficient rolling Bloom filter (Pieter Wuille)
6e76587 rpc: remove cs_main lock from `createrawtransaction` (Wladimir J. van der Laan)
5e10922 Combine common error strings for different options so translations can be shared and reused (Luke Dashjr)
6cd198f Removed comment about IsStandard for P2SH scripts (Marcel Krüger)
3a9dfe9 Fix typo, wrong information in gettxout help text. (paveljanik)
0331aa3 Fixing typos on security-check.py and torcontrol.cpp (calebogden)
64360f1 Make max tip age an option instead of chainparam (Wladimir J. van der Laan)
da6d18b devtools: replace github-merge with python version (Wladimir J. van der Laan)
…n to wallet/ code dd2dc40 [RPC, Wallet] Move RPC dispatch table registration to wallet/ code (Jonas Schnelli)
96efcad Improved readability of sorting for coin selection. (Murch)
…eive coins table df6e8e1 [Qt] rename "amount" to "requested amount" in receive coins table (Jonas Schnelli)
2409865 Reduce inefficiency of GetAccountAddress() (Chris Moore)
e279038 Use createrawtx locktime parm in txn_clone (Tom Harding)
…hub-merge 17b5d38 devtools: show pull and commit information in github-merge (Wladimir J. van der Laan)
…extra whitespace 5ed2f16 [devtools] github-merge get toplevel dir without extra whitespace (Andrew C)
00eb70c to
38c12ff
Compare
Author
|
I disabled check-doc.py on Travis for now. I'll fix errors reported by check-doc.py after all PRs have been merged. |
UdjinM6
requested changes
Dec 10, 2017
There was a problem hiding this comment.
Nice job! 👍
Few general comments:
- Technically, f840708 fixes the bug introduced in #888 and shouldn't be a part of this PR but ok, let's keep it;
- bitcoin#7583 is incomplete, changes in
doc/shared-libraries.mdare missing; - ba290c7 is weird - its content doesn't match the description (
Merge #7482: [P2P] Ensure headers count is correct) and it feels like it's a mix of two other PRs/commits.
- see inline comments
configure.ac
Outdated
There was a problem hiding this comment.
Needs [https://dash.org/] like in original PR https://github.com/bitcoin/bitcoin/pull/7192/files#diff-67e997bcfdac55191033d57a16d1408aR11
contrib/macdeploy/custom_dsstore.py
Outdated
There was a problem hiding this comment.
Lines 48, 49, 57 should probably be dashified
share/qt/Info.plist.in
Outdated
There was a problem hiding this comment.
Should keep Bitcoin Core copyright here
src/clientversion.h
Outdated
There was a problem hiding this comment.
Should keep Bitcoin Core copyright here
src/qt/res/dash-qt-res.rc
Outdated
This was referenced Dec 19, 2017
This was referenced Dec 27, 2017
This was referenced Jan 11, 2018
This was referenced Jan 19, 2018
andvgal
added a commit
to energicryptocurrency/gen2-energi
that referenced
this pull request
Oct 4, 2019
andvgal
added a commit
to energicryptocurrency/gen2-energi
that referenced
this pull request
Oct 4, 2019
andvgal
added a commit
to energicryptocurrency/gen2-energi
that referenced
this pull request
Oct 4, 2019
andvgal
added a commit
to energicryptocurrency/gen2-energi
that referenced
this pull request
Oct 4, 2019
andvgal
added a commit
to energicryptocurrency/gen2-energi
that referenced
this pull request
Oct 4, 2019
andvgal
pushed a commit
to energicryptocurrency/gen2-energi
that referenced
this pull request
Oct 4, 2019
dashpay#1770 - SPORK 17 - block time enforcement See merge request energi/dev/gen2/core/energi!333
andvgal
added a commit
to energicryptocurrency/gen2-energi
that referenced
this pull request
Oct 4, 2019
andvgal
added a commit
to energicryptocurrency/gen2-energi
that referenced
this pull request
Oct 4, 2019
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
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.
This is the first batch of backported PRs from Bitcoin which are still missing in Dash.
I've got a total of ~780 PRs (including 0.13+0.14 PRs) in my local branches, so the amount of changed code is huge. I was thinking alot about how large the individual batches should be and decided to make them ~50 PRs per batch. This way we'll have around 16 huge PRs instead of hundreds of small ones. I understand that reviewing these batches will be hell, but having smaller batches won't really change the amount of work required and only prolong everything.
I've gone through all PRs and tried my best to omit PRs for features we do not want in Dash or which conflict with Dash specific features/changes. If I mistakenly included something that should have been omitted, please tell me and I remove these changes.
As the splitting of main.cpp->net_processing.cpp/validation.cpp was done out-of-order, I had to do a lot of manual copy+paste conflict resolution. This poses a high risk of loosing changes. My plan is to do a full-tree diff when all PRs are merged and if anything was lost, I'll hopefully catch it this way.