diff options
| author | glozow <gzhao408@berkeley.edu> | 2021-04-27 14:43:48 -0700 |
|---|---|---|
| committer | glozow <gzhao408@berkeley.edu> | 2021-05-24 15:48:32 +0100 |
| commit | 9ef643e21b44f99f4bce54077788d0ad4d81f7cd (patch) | |
| tree | dce986182b09a26e6ee40b0a0f56e4bb1fa7db3b /doc | |
| parent | c4259f4b7ee23ef6e0ec82c5d5b9dfa9cadd5bed (diff) | |
[doc] add release note for package testmempoolaccept
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release-notes-20833.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/release-notes-20833.md b/doc/release-notes-20833.md new file mode 100644 index 0000000000..9a02bbd275 --- /dev/null +++ b/doc/release-notes-20833.md @@ -0,0 +1,12 @@ +Updated RPCs +------------ + +- The `testmempoolaccept` RPC now accepts multiple transactions (still experimental at the moment, + API may be unstable). This is intended for testing transaction packages with dependency + relationships; it is not recommended for batch-validating independent transactions. In addition to + mempool policy, package policies apply: the list cannot contain more than 25 transactions or have a + total size exceeding 101K virtual bytes, and cannot conflict with (spend the same inputs as) each other or + the mempool, even if it would be a valid BIP125 replace-by-fee. There are some known limitations to + the accuracy of the test accept: it's possible for `testmempoolaccept` to return "allowed"=True for a + group of transactions, but "too-long-mempool-chain" if they are actually submitted. (#20833) + |