Dry Run Phase 5 Gov Proposal

Mainnet Ops
1

Hello! This thread is to initiate discussion for Phase 5 of the Namada dry-run.

The gov proposal code is here: namada-governance-upgrades/phase5/src/lib.rs at a1dfd58196530458ab0d01279b6b76a8021fe391 · anoma/namada-governance-upgrades · GitHub. All that the code does is turn on transfers of the native token NAM.

I will put the proposal on-chain with an activation epoch about 24 hours after the activation of Phase 4, which looks to be happening around 11:00 CET on Tuesday. This should give everyone a chance to use Tuesday to gauge the performance of Phase 4 and decide how to vote accordingly on Phase 5.

Please start the discussion! Thanks for great governance participation so far.

4 Likes
2

Gov proposal is on-chain with an ID of 4!

> namadac query-proposal --proposal-id 4 --node $RPC_TUDUDES

Last committed epoch: 76
Proposal Id: 4
Type: Default with Wasm
Author: tnam1qqgll8x8rz9fvtdv8q6n985za0vjvgyu0udxh7fp
Content: {"abstract": "Initialize phase 5 of the dry-run by enabling transfers of the native token NAM. All Namada functionality should be live after the execution of this proposal.", "discussions-to": "https://forum.namada.net/t/dry-run-phase-5-gov-proposal/1099", "title": "Phase 4 -> 5"}
Start Epoch: 77
End Epoch: 92
Activation Epoch: 93
Status: pending
Data: Hash: CEEB50B44CA4C72A403B67A14906592C0DBF9ADEE7C2A37375CE294A11400010

If you are a validator, please remember that you can only vote with the validator address in the first ~2/3 of the voting period- in this case before epoch 87.

2 Likes
3

A priori it looks like the governance proposal hash doesn’t match with the phase5.wasm one I got following the instructions in here: GitHub - anoma/namada-governance-upgrades

sha256sum phase5.wasm
205719d579a16990de884521c55a4fb4df8570b2b1f66ace6c92f829e95f13b8  phase5.wasm

check-onchain-wasm --tendermint-url http://127.0.0.1:26657 --proposal-id 4 --expected-hash CEEB50B44CA4C72A403B67A14906592C0DBF9ADEE7C2A37375CE294A11400010
Proposal Code Hash: CEEB50B44CA4C72A403B67A14906592C0DBF9ADEE7C2A37375CE294A11400010
The expected hash DOES NOT correspond to the wasm associated with proposal id: 4
4

With this one I now get the hash of the governance proposal:

sha256sum phase5.wasm
ceeb50b44ca4c72a403b67a14906592c0dbf9adee7c2a37375ce294a11400010  phase5.wasm

Edit. the proposal code wasn’t in the main branch, so that’s why I got wrong hash in first instance. I assume the submitted code is then the correct one.

2 Likes
5

We support this proposal lets go :rocket:

1 Like
6

I believe this proposal ready to move

7

The hash checks out, let’s go :+1:

~/namada-governance-upgrades/artifacts# sha256sum phase5.wasm
ceeb50b44ca4c72a403b67a14906592c0dbf9adee7c2a37375ce294a11400010  phase5.wasm
2 Likes
8

I have performed few tests after reaching out phase 5 to check out if NAM is now transferable:

  • Transparent transfers working (gas fees with NAM and OSMO)
  • Shielding transfers working (gas fees with NAM and OSMO)
  • Shielded transfers working (gas fees with NAM and OSMO, plus using gas spending key + disposable gas payer)
  • Unshielding transfers working (gas fees with NAM and OSMO, plus using gas spending key + disposable gas payer)

In all these actions NAM tokens have been moved without issues.

IBC rate limit per-epoch for NAM tokens is 0, so I couldn’t test out transparent nor unshielding IBC transfers so as to move them:

  [
    "tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4",
    "Native VP error: IBC rate limit: Transfer exceeding the per-epoch throughput limit is not allowed: Per-epoch throughput limit 0, actual throughput 777000000"
  ]
]
1 Like
9

We support this proposal!

10

Thrilled to see Phase 5 bringing NAM transfers to life! This is a big step towards realizing the full potential of the network.