Operators are "blind" when voting for governance (contract changes)

[greenhat]

Although they vote for a particular pool contract hash it's hard to understand how refresh and update contracts are changed. The pool contract contain both refresh and update NFT, but these token can be anywhere.

Operators need a way to verify new refresh and update contracts.

Things to verify:

• refresh and update tokens are NFT (find mint box?);
• find the boxes that are guarding refresh and update NFTs;
• show how new refresh and update contracts are different from the current ones (which parameters are changed, is source changed);

With provided pool_config_updated.yaml (generated by prepare-update-pool command) and an ErgoScript pretty printer (ESPP) the following scenario on vote-update-pool command becomes feasible:

Verification workflow:

• verify passed pool hash against the pool contract in pool_config_updated.yaml;
• show new pool contract diff with ESPP;
• if the refresh token id is changed, find the minting box for the new refresh contract and show the diff with ESPP;
• if the update token id changed, find the minting box for the new update contract and show the diff with ESPP;