diff options
author | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-02-08 22:05:00 +0100 |
---|---|---|
committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-02-08 22:19:53 +0100 |
commit | 67447ba06057b8e83f962c82491d2fe6c5211f50 (patch) | |
tree | 94c25e37dfe1e50db0f61f4537619f9ac8f4f494 /src/secp256k1/README.md | |
parent | d405beea26c1569f46cf50ef71b376c9487ce361 (diff) | |
parent | 669c9433cfbc6bc25243fcdb550009b2d4180cc9 (diff) | |
download | bitcoin-67447ba06057b8e83f962c82491d2fe6c5211f50.tar.xz |
Merge #12225: Mempool cleanups
669c943 Avoid leaking prioritization information when relaying transactions (Suhas Daftuar)
e868b22 fee estimator: avoid sorting mempool on shutdown (Suhas Daftuar)
0975406 Correct mempool mapTx comment (Suhas Daftuar)
Pull request description:
Following up on #12127 and #12118, this cleans up a comment that was left incorrect in txmempool.h, and addresses a couple of the observations @TheBlueMatt made about an unnecessary use of `queryHashes()` and a small information leak when prioritizing transactions.
Left undone is nuking queryHashes altogether; that would require changing the behavior of the `getrawmempool` rpc call, which I think I might be in favor of doing, but wanted to save for its own PR.
Tree-SHA512: c97d10b96dcd6520459287a4a2eda92774173757695100fcfe61e526aef86f394507c331d17f9e0c14b496c33ec46198a0f165a847762ca50f7c6780b993f162
Diffstat (limited to 'src/secp256k1/README.md')
0 files changed, 0 insertions, 0 deletions