diff options
| author | Wladimir J. van der Laan <[email protected]> | 2019-10-25 13:46:41 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <[email protected]> | 2019-10-25 13:47:28 +0200 |
| commit | 90ed98ae9a2ace4ea371d63ca7c3a83ea6224eab (patch) | |
| tree | 42bb308c66189fa5f33d479de7d4b9db4d01dcfb /src/validationinterface.cpp | |
| parent | Merge #17231: depends: fix boost mac cross build with clang 9+ (diff) | |
| parent | consensus: Explain why fCheckDuplicateInputs can not be skipped and remove it (diff) | |
| download | discoin-90ed98ae9a2ace4ea371d63ca7c3a83ea6224eab.tar.xz discoin-90ed98ae9a2ace4ea371d63ca7c3a83ea6224eab.zip | |
Merge #17080: consensus: Explain why fCheckDuplicateInputs can not be skipped and remove it
fa928134075220254a15107c1d9702f4e66271f8 consensus: Explain why fCheckDuplicateInputs can not be skipped and remove it (MarcoFalke)
Pull request description:
As a follow up to CVE-2018-17144, this removes the unused `fCheckDuplicateInputs` parameter and explains why the test can not be disabled. Apart from protecting against a dumb accident in the future, this should document the logic in the code. There is a technical write-up that explains how the underlying coins database behaves if this test is skipped: https://bitcoincore.org/en/2018/09/20/notice/#technical-details. However, it does not explicitly mention why the test can not be skipped. I hope my code comment does that.
ACKs for top commit:
jnewbery:
ACK fa928134075220254a15107c1d9702f4e66271f8
amitiuttarwar:
utACK fa928134075220254a15107c1d9702f4e66271f8
Empact:
Code review ACK https://github.com/bitcoin/bitcoin/commit/fa928134075220254a15107c1d9702f4e66271f8
promag:
ACK fa928134075220254a15107c1d9702f4e66271f8.
Tree-SHA512: fc1ef670f1a467c543b84f704b9bd8cc7a59a9f707be048bd9b4e85fe70830702aa560a880efa2c840bb43818ab44dfdc611104df04db2ddc14ff92f46bfb28e
Diffstat (limited to 'src/validationinterface.cpp')
0 files changed, 0 insertions, 0 deletions