Dry Run Phase 2 Gov Proposal

Mainnet Ops
1

Hello everyone! Using this thread to discuss the governance proposal for enabling Phase 2 with inflation for staking and PGF!

The gov proposal code is here: namada-governance-upgrades/phase2/src/lib.rs at main · anoma/namada-governance-upgrades · GitHub

In short, what it does:

  • Set proof-of-stake max annual inflation to 5%
  • Set target staked ratio of NAM to 40%
  • Set proof-of-stake inflation gain parameters
  • Set PGF annual inflation to 5%
  • Set annual inflation for each PGF steward to 0.5%
10 Likes
2

Perfect , we support this . :rocket: :rocket:

1 Like
3

The proposal is now live on-chain with proposal ID 0!

> namadac query-proposal --proposal-id 0 
Last committed epoch: 0
Proposal Id: 0
Type: Default with Wasm
Author: tnam1qqgll8x8rz9fvtdv8q6n985za0vjvgyu0udxh7fp
Content: {"abstract": "Initialize phase 2 of the dry-run by enabling inflation for Proof-of-stake (PoS) and Public Goods Funding (PGF)", "discussions-to": "https://forum.namada.net/t/dry-run-phase-2-gov-proposal/1068", "title": "Phase 1 -> 2"}
Start Epoch: 1
End Epoch: 13
Activation Epoch: 14
Status: pending
Data: Hash: EAF15308CEC6A657EE42FC599259A3F8A7D629991EEF1E0917653C36176CA5FC
7 Likes
4

Now we need to verify the hash

5 Likes
6

yesss! appreciate you

1 Like
7

There are 3 steps involved in verifying the proposal.

1. Check the source code
Verify that the source code is correct and does what is described.

2. Calculate the hash of the WASM source code
The code that was posted may not match the WASM that has been submitted with the proposal on-chain.

3. Calculate the hash of the on-chain WASM
@brentstone could have posted an incorrect hash. There is a tool called WASM Proposal Checker in a subfolder of the namada-governance-upgrades repository. It downloads the proposal WASM from the chain and then calculates the SHA256 hash. An easier way is to mimic brentstone’s command to get the hash from the command line: namadac query-proposal --proposal-id 0 Compare this hash with the hash from step 2.

1 Like
8

I went about this with a more manual approach, but I used earthly and sha256sum to confirm the hash:

~/namada-governance-upgrades/artifacts# sha256sum phase2.wasm
eaf15308cec6a657ee42fc599259a3f8a7d629991eef1e0917653c36176ca5fc  phase2.wasm

It matches.

1 Like
9

Yes, the hash matches, and it is easy to verify.

Another thing people can do: the CI on github builds the wasms as artifacts. For example, here are the wasm artifacts from the latest main (commit 8e5d5b1): Merge pull request #20 from anoma/brent/phase3-token-map · anoma/namada-governance-upgrades@8e5d5b1 · GitHub.

If you download that WASM file, then run sha256sum phase2.wasm, your output will be the same as the hash reported from namadac query-proposal (just in all lowercase)

3 Likes
10

Congrats everyone on the milestone :slight_smile:

1 Like