Deploying the test version of the NNS governance canister in local test enviornments

Developers Command Line Tools
1

The dfx nns extension deploys the test version of the NNS governance canister (rrkah-fqaaa-aaaaa-aaaaq-cai) to local test environments (after running dfx nns install) and this test version of the canister exposes an extra test-only endpoint update_neuron to override a neuron (almost) arbitrarily.

Now we wonder if this functionality is actually used in practice or if the production version of the NNS governance canister is sufficient in local test environments.

Using the production version instead of the test version would simplify ongoing work to automate NNS canister version bumps to keep local test environments up-to-date. Hence, we would like to ask you for your feedback if we could proceed with the production version of the NNS governance canister in local test environments.

3 Likes
2

AFAIK, the NNS Dapp development and testing environment is relying on the test version of the NNS Governance for:

  1. Getting maturity for a certain neuron through update_neuron
  2. Getting new functionalities (usually enabled through the test version first) before they are ready on the mainnet

cc @yhabib @mstrasinskis

3

Yes, @jasonzhu is right — the NNS Dapp relies on the test governance canister for update_neuron and early feature access, both for development and e2e tests.

4

Thanks for your feedback! We’ve updated the automation to keep track of the test version of the NNS governance canister so we could use in PocketIC after all.

1 Like