-
Notifications
You must be signed in to change notification settings - Fork 38.7k
B: Get rid of Params().RequireStandard() #16527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
ce380b9 to
1dc2536
Compare
|
Rebased |
1dc2536 to
5a5df16
Compare
5a5df16 to
b11d740
Compare
|
Decoupled from #16524 |
|
This means that non std txs aren't propagated on testnet, so tend to NACK |
|
Well, only if users don't set acceptnonstdtxn=1, we could say it in the release notes. |
|
It makes sense to default to |
|
Closing for now due to lack of interest. |
Based on #16524Alternative to #16526
This goes further and just like in #16524 it removes the different defaults for each chain.
In my opinion, one thing is to want to prevent people from shooting themselves in the food like AllowAcceptNonstd()/IsTestChain() allows for mainnet and a very different one is having per chain defaults for each parameter.
testnet3 and regtest users will now need to modify their config files, at most, in the following way:
I don't think that's much to ask from the advanced users regtest and testnet users are supposed to be.
Maybe this is different for testnet3, I would like to hear why.