anoma / namada

Rust implementation of Namada, a Proof-of-Stake L1 for interchain asset-agnostic privacy
https://namada.net
GNU General Public License v3.0
2.39k stars 948 forks source link

Became PGF Steward with Transparent Address #3048

Closed pvsairam closed 1 month ago

pvsairam commented 5 months ago

Description:

I became a PGF (Public Goods Funding) steward, but I used a transparent address instead of a multisig account, as outlined in the Namada documentation. Despite this deviation, my stewardship proposal was approved, and I have been receiving PGF steward rewards. However, I'm uncertain if this aligns with Namada's governance protocols.

image

image

root@vmi1633926:~# nano proposal.json
root@vmi1633926:~# namadac init-proposal --pgf-stewards --data-path $HOME/proposal.json --node $RPC_SE --memo $MEMO
Last committed epoch: 18
Enter your decryption password: 
Transaction added to mempool.
Wrapper transaction hash: B47E81B5553B249181B8403516481697E5EE7F4DC32B354AB6CAE8F6513E8463
Inner transaction hash: 260B91A22D32832C1561209EE77854BACFCFE3F2D0D48506EE0DF78A39DD9FE5
Wrapper transaction accepted at height 73497. Used 35 gas.
Waiting for inner transaction result...
Transaction was successfully applied at height 73498. Used 7552 gas.

Background:

According to Namada's documentation, individuals seeking stewardship are required to create a multisig account and submit a governance proposal for community decision-making. This process ensures transparency, security, and community participation in managing public funds.

Documentation used - https://docs.namada.net/users/public-goods-stewards/electing

Issue:

In my case, I used a transparent address instead of a multisig account when submitting my proposal. Despite this choice, my proposal was approved, and I've been receiving PGF rewards.

image

image

Additional Info:

Proposal ID: 238 Transparent Address Used: tnam1qqm7euwxqva3xllxjz3wt8pwmtcgcllg05cfekpn Memo: tpknam1qrhqdk3ryv5e0xjzpnnuyfj5k758xxszkv2jh4zzn2qmf6xl2r2g2af3yuy

pvsairam commented 5 months ago

I have included this GitHub issue in my S-Class submission - 2359 for further team review.