You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be productive and valuable to require that a ZIP may not reach a certain maturity state without the presence of a persistent feature-gated testnet (assuming the ZIP alters consensus rules)?
If this were a requirement of the ZIP process, it would ensure people know early on this will be a necessary step, and as the ZIP matures this would help ensure the testnet exists prior to the community decision time about including the ZIP features into an upcoming upgrade.
OTOH, adding another requirement may inhibit some people from proposing ZIPs. Is there any way we could encourage "pre-testnet" ZIP proposals anyway?
In the status quo, it's often node implementers who set up testnets rather than ZIP authors (although that's changing!) so even with this new testnet process requirement, the labor could still be divided that way. Maybe node dev teams or other developers could proactively "sponsor" early ZIP ideas for which they would contribute to testnet deployments?
The text was updated successfully, but these errors were encountered:
Would it be productive and valuable to require that a ZIP may not reach a certain maturity state without the presence of a persistent feature-gated testnet (assuming the ZIP alters consensus rules)?
If this were a requirement of the ZIP process, it would ensure people know early on this will be a necessary step, and as the ZIP matures this would help ensure the testnet exists prior to the community decision time about including the ZIP features into an upcoming upgrade.
OTOH, adding another requirement may inhibit some people from proposing ZIPs. Is there any way we could encourage "pre-testnet" ZIP proposals anyway?
In the status quo, it's often node implementers who set up testnets rather than ZIP authors (although that's changing!) so even with this new testnet process requirement, the labor could still be divided that way. Maybe node dev teams or other developers could proactively "sponsor" early ZIP ideas for which they would contribute to testnet deployments?
The text was updated successfully, but these errors were encountered: