[#985] Create a ZIP Draft to document Regtest mode #986
Conversation
pacu
force-pushed
the
regtest-zip-draft
branch
from
8a33bbb to
e4b17fc
Compare
nuttycom
left a comment
nuttycom
left a comment
There was a problem hiding this comment.
Partial review; I have not yet reviewed beyond the section Behavior for ZIP-200 Network Upgrade Mechanism.
In general, specification language needs to be somewhat more precise than most of what is presented in this draft. In particular, the affected components and actors should be clearly identified in each portion of the specification, and particular care should be taken with respect to any conditionals. Focus on what has to happen more than the actor in each section.
|
Thank you very much for your comments @nuttycom. I've included your feedback and in-line suggestions. |
| have a consensus node on a local network with a private state that a developer | ||
| can control in order to reproduce certain situations deterministically for | ||
| testing purposes. Regtest, as it was implemented on Zcashd, is similar to a | ||
| “testnet” but without miners and remote peers. |
There was a problem hiding this comment.
If I recall correctly many of the qa/rpc-tests in zcash acually have more than local "peer".. I wonder whether the "remote-vs-local" distinction here, might be somewhat orthogonal to the purpose of regtest mode, which though frequently used with multiple nodes in the same ip:tcp space, could be used more "remotely" with the same regtest properties.
|
|
||
| ## Motivation | ||
| It is necessary to define Regtest mode so that different implementations of Zcash | ||
| Full Nodes provide the same capabilities so that testing infrastructure can be |
There was a problem hiding this comment.
Again it seems to me that "regtest" has utility for relatively low-capability "nodes". That is, less than "full".
There was a problem hiding this comment.
what is a "low-capability" node?
| specifically designed to avoid requirement 1 in Testnet and Mainnet | ||
| 1. Developers MUST specify the activation heights of the different Network | ||
| Upgrades on launch via parameters or configuration file. | ||
| 1. Remote Peer-to-Peer connections MUST NOT be allowed. All peers MUST be local |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
daira
left a comment
daira
left a comment
There was a problem hiding this comment.
NACK due to a ZIP 0 violation in the Owners field.
Co-authored-by: Daira-Emma Hopwood <daira@jacaranda.org>
|
@zancas could you kindly review the follow-ups to your comments? much appreciated! |
4 participants
closes #985