diff options
| author | Andrew Chow <github@achow101.com> | 2023-08-15 10:03:51 -0400 |
|---|---|---|
| committer | Andrew Chow <github@achow101.com> | 2023-08-15 10:15:22 -0400 |
| commit | cd43a8444ba44f86ddbb313a03a2782482beda89 (patch) | |
| tree | eb546535fe4adafce1c998bf3584a82759c1c925 /ci | |
| parent | 80d70cb6b04b5a3c13e661c0718a4b5108d55869 (diff) | |
| parent | fa776e61cd64a5ffd9a4be589ab8efeb5421861a (diff) | |
| download | bitcoin-cd43a8444ba44f86ddbb313a03a2782482beda89.tar.xz | |
Merge bitcoin/bitcoin#27460: rpc: Add importmempool RPC
fa776e61cd64a5ffd9a4be589ab8efeb5421861a Add importmempool RPC (MarcoFalke)
fa20d734a29ba50cd19b78cb4fe39a2d826131b7 refactor: Add and use kernel::ImportMempoolOptions (MarcoFalke)
fa8866990dba7817427977bfe834efdb17114d37 doc: Clarify the getmempoolinfo.loaded RPC field documentation (MarcoFalke)
6888886cecf6665da70b3dc3772b3c12ef06ad76 Remove Chainstate::LoadMempool (MarcoFalke)
Pull request description:
Currently it is possible to import a mempool by placing it in the datadir and starting the node. However this has many issues:
* Users aren't expected to fiddle with the datadir, possibly corrupting it
* An existing mempool file in the datadir may be overwritten
* The node needs to be restarted
* Importing an untrusted file this way is dangerous, because it can corrupt the mempool
Fix all issues by adding a new RPC.
ACKs for top commit:
ajtowns:
utACK fa776e61cd64a5ffd9a4be589ab8efeb5421861a
achow101:
ACK fa776e61cd64a5ffd9a4be589ab8efeb5421861a
glozow:
reACK fa776e61cd64a5ffd9a4be589ab8efeb5421861a
Tree-SHA512: fcb1a92d6460839283c546c47a2d930c363ac1013c4c50dc5215ddf9fe5e51921d23fe0abfae0a5a7631983cfc7e2fff3788b70f95937d0a989a203be4d67546
Diffstat (limited to 'ci')
0 files changed, 0 insertions, 0 deletions