We have just cross-checked hashes from the governance proposal and the one from the phase 3 proposal code on namada-governance-upgrades repository, and both match.
sha256sum phase3.wasm
7d5dba237c6dd79e4da79c2fd00150a9e758ed2fb0474fa5b87ea770b7aefdc7 phase3.wasm
So, we support the proposal. LFG!
Yes, hash matches!
sha256sum phase3.wasm
7d5dba237c6dd79e4da79c2fd00150a9e758ed2fb0474fa5b87ea770b7aefdc7 phase3.wasm
Just a small FYI: the commit version in the link above ( INCORRECT.a4d6906a0dca2cbf4ddd55f066a0f09cc58aec26) doesn’t result in the same hash, but the commit that’s on main atm does (3af24bc51eea7db30bd3b8c77f584f217b5ae509).
@zenodeapp this does not seem true, I just checked by redownloading from github commit a4d6906a0dca2cbf4ddd55f066a0f09cc58aec26. The link to the file in that commit here that contains the relevant CI run behind the green check mark has phase3.wasm as an artifact, which has the same sha256sum here.
@brentstone you’re right. Weird, I can’t reproduce what happened before now. Can’t see what I did wrong either. if I look at my history, I literally did the same (pull, checkout, earthly +build, sha256sum). Perhaps it had something to do with caching since it was an old clone I keep reusing to check these things.
Editing the above! Thanks for double checking.
Support proposal , we are all waiting success
We, EmberStake, have reviewed the code of the Phase 3 Proposal at GitHub. Based on our understanding, it performs as described in the proposal and does not exhibit any malicious behavior.
We also verified that the checksum of the compiled code matches the on-chain hash:
7d5dba237c6dd79e4da79c2fd00150a9e758ed2fb0474fa5b87ea770b7aefdc7
Proposal supported. Have voted on chain. 
I support this proposal. On-chain - voted 
TuDudes supports this proposal. 
voted
did my first Namada voting with tokens. 
Excited we are live 
Huge thanks everyone for all the hard work!
ZecHub just dropped a quick demo on shielding some OSMO 