diff options
author | MarcoFalke <falke.marco@gmail.com> | 2019-07-16 16:07:14 -0400 |
---|---|---|
committer | MarcoFalke <falke.marco@gmail.com> | 2019-07-16 16:10:17 -0400 |
commit | 24dbcf380844f326b6a4e59466dba892314d2843 (patch) | |
tree | c690aa9427d04382ac76896fdae7ae25cc74ae8f /doc | |
parent | 8f604361ebaa5263e614c21570a3256e4dbc3bcc (diff) | |
parent | fa89badf887dcc01e5bdece248b5e7d234fee227 (diff) | |
download | bitcoin-24dbcf380844f326b6a4e59466dba892314d2843.tar.xz |
Merge #15891: test: Require standard txs in regtest by default
fa89badf887dcc01e5bdece248b5e7d234fee227 test: Require standard txs in regtest (MarcoFalke)
fa9b4191609c3ef75e69d391eb91e4d5c1e0bcf5 test: Add test that mainnet requires standard txs (MarcoFalke)
fa613ca0a8f99c4771859de9e571878530d3ecb5 chainparams: Remove unused fMineBlocksOnDemand (MarcoFalke)
Pull request description:
I don't see a reason why regtest should allow non-standard txs, as it makes testing mainnet behaviour such as #15846 unnecessarily hard and unintuitive.
Of course, testnet policy remains unchanged to allow propagation of non-standard txs.
ACKs for top commit:
ajtowns:
ACK fa89badf887dcc01e5bdece248b5e7d234fee227
Tree-SHA512: c4c675affb054868850bd2683aa07f4c741a448cbacb2ea8334191e105f426b0790fe6a468be61e9c5880d24154f7bf1c7075051697172dce92180c1bc3a1c90
Diffstat (limited to 'doc')
-rw-r--r-- | doc/release-notes.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index 9efb6cbabb..83c84d34c9 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -103,6 +103,20 @@ Low-level Changes section below. Low-level changes ================= +RPC +--- + + +Tests +----- + +- The regression test chain, that can be enabled by the `-regtest` command line + flag, now requires transactions to not violate standard policy by default. + Making the default the same as for mainnet, makes it easier to test mainnet + behavior on regtest. Be reminded that the testnet still allows non-standard + txs by default and that the policy can be locally adjusted with the + `-acceptnonstdtxn` command line flag for both test chains. + Configuration ------------ |