Skip to content

Conversation

@jtimon
Copy link
Contributor

@jtimon jtimon commented Aug 1, 2019

Based on #16524
Alternative 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:

[main]
+acceptnonstdtxn=0
...

[test]
+acceptnonstdtxn=1
...

[regtest]
+acceptnonstdtxn=0
...

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.

@DrahtBot
Copy link
Contributor

DrahtBot commented Aug 1, 2019

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

Reviewers, this pull request conflicts with the following ones:

  • #17037 (Testschains: Many regtests with different genesis and default datadir by jtimon)
  • #17032 (Tests: Chainparams: Make regtest almost fully customizable by jtimon)
  • #16770 (Chainparams: Rename IsTestChain() to AllowAcceptNonstd() by jtimon)

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.

@jtimon jtimon changed the title Get rid of Params().RequireStandard() B: Get rid of Params().RequireStandard() Aug 1, 2019
@jtimon jtimon force-pushed the b19-chainparams-no-requirestd branch from ce380b9 to 1dc2536 Compare August 7, 2019 02:50
@jtimon
Copy link
Contributor Author

jtimon commented Aug 7, 2019

Rebased

@jtimon jtimon force-pushed the b19-chainparams-no-requirestd branch from 1dc2536 to 5a5df16 Compare August 7, 2019 07:51
@jtimon jtimon force-pushed the b19-chainparams-no-requirestd branch from 5a5df16 to b11d740 Compare August 31, 2019 16:10
@jtimon
Copy link
Contributor Author

jtimon commented Aug 31, 2019

Decoupled from #16524

@maflcko
Copy link
Member

maflcko commented Oct 3, 2019

This means that non std txs aren't propagated on testnet, so tend to NACK

@jtimon
Copy link
Contributor Author

jtimon commented Oct 3, 2019

Well, only if users don't set acceptnonstdtxn=1, we could say it in the release notes.
But yeah, that's, I think, the best argument against this.

@luke-jr
Copy link
Member

luke-jr commented Oct 8, 2019

It makes sense to default to -acceptnonstdtxn=1 on testnet. But it's also just testnet, so don't care too strongly.

@jtimon
Copy link
Contributor Author

jtimon commented Feb 4, 2020

Closing for now due to lack of interest.

@jtimon jtimon closed this Feb 4, 2020
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Feb 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants