Governance Proposals
Phase 5 IBC transfers for NAM
Turning on IBC transfers for the native token NAM. This allows NAM to be transferred out of Namada over IBC and back into Namada the same way. The per-epoch throughput limit is set to 20M NAM. The code used to generate the WASM attached to this proposal can be found here: https://github.com/anoma/namada-governance-upgrades/blob/ea7e6f6d413a4f8399cb995e782b4aadbe6dda4f/phase5b/src/lib.rs. Please see the forum discussion linked here for more details.
Begin Phase 5: enable internal NAM transfers within Namada
Flipping the switch to turn on internal native token (NAM) transfers within Namada. This enables transparent transfers, shielded transfers, shielding, and unshielding of NAM within Namada. The code used to generate the WASM attached to this proposal can be found here: https://github.com/anoma/namada-governance-upgrades/blob/31e492c3cef25db6dc0dec0a005080d5ce2ace48/phase5a/src/lib.rs. Please see the forum discussion linked here for more details.
Update the transfer tx in on-chain storage ahead of Phase 5
The tx_transfer must be updated to prevent very large batch transfers. The code used to generate the WASM attached to this proposal can be found here: https://github.com/anoma/namada-governance-upgrades/blob/390cf675a603c251186e255686637a450109e629/update-tx-transfer/src/lib.rs. Please see the forum discussion linked here for more details.
Update the claim-rewards tx in on-chain storage ahead of Phase 5
The tx_claim_rewards must be updated to allow some select users with many redelegations to claim their rewards from specific validators. Currently, these claims enter a code path that iterates asymptotically and does not complete before the tx times out. The code used to generate the WASM attached to this proposal can be found here: https://github.com/anoma/namada-governance-upgrades/blob/6da3b4b1835ae531589bcef65602bf3a803e1de3/update-tx-claim-rewards-2/src/lib.rs. Please see the forum discussion linked here for more details.
Phase 4: enable shielding rewards
This proposal is to enable shielding rewards for an initial set of seven assets: Cosmos Hub (ATOM), Osmosis (OSMO), Celestia (TIA), the Stride liquid-staked versions of these tokens, and Noble’s USDC. Alongside this activation, it will set initial starting points for several key configurable parameters, including the maximum inflation rate, token deposit targets, Proportional Gain, and Derivative Gain. It should be clearly noted that these values are just initial settings, and they are fully configurable. The community can revisit and adjust these parameters through governance at any point in the future as needed. The proposal code that generated the attached wasm can be found here: https://github.com/anoma/namada-governance-upgrades/blob/5a69808c8b42f7f89b4344150f8db3078d8a6ba5/phase4/src/lib.rs. The proportional and derivate gain values are set to 50 and 85, respectively, for each token. The maximum annual inflation rate for USDC is set to 1.8%, while the annual inflation rate for all other tokens is set to 0.9%. The target pool amounts for each token are as follows: USDC: 2.2M OSMO: 8.7M ATOM: 421K TIA: 781K stOSMO: 625K stATOM: 27K stTIA: 70K
Signalling: coordinating mainnet software upgrade to namada v101.0.0 at height 2,176,000
Gathering social consensus to coordinate a software upgrade of namada nodes at block 2,176,000. This block is expected to occur at about 15:00 UTC on Tuesday, May 27, 2025.
Signalling - Support for Wormhole as Namada’s First New Bridge Integration
To make Namada the composable privacy layer of the multichain, we will need to expand the set of ecosystems we support. Proposal This is a proposal asking voters to signal preference for Wormhole to be Namada's first new bridge integration. Context Namada's core protocol is developed and maintained by Heliax, and Heliax is currently deciding their engineering resource priorities. Over the weekend, I created a forum post to discuss the need for a bridge integration - specifically, to begin with a Wormhole integration. @cwgoes and @brentstone have publicly supported the idea, and if voters agree with this direction, Heliax is ready to provide technical resources when needed. History Veil is aligned with Namada's mission to support a broad range of assets in order to expand access to composable privacy - being as meaningfully useful for as many uses as possible. We've previously submitted two asset support proposals and plan to propose many more. Integrating Wormhole would significantly grow the universe of assets and chains we can bring into the shielded set, unlocking new opportunities for privacy adoption across ecosystems. Potential Issue As noted in Namada Discord conversations, Wormhole suffered an exploit in early 2022, resulting in a ~$320M loss. However, the protocol has since facilitated tens of billions in volume and has become the default bridging solution for many new chains. While the exploit was significant, depositors were made whole. Wormhole's continued adoption, resilience and track record since, have made it (in our view) the most reliable and forward-compatible option available today. We're confident that Wormhole’s maturity and battle-tested infrastructure benefit from the Lindy effect and position it well for supporting Namada's growth. Additional Note While this integration is a top priority, it does not preclude or exclude future integrations such as IBC Eureka.
Whitelisting USDC, UM, NYM, and NTRN for Namada
This proposal seeks to add support for four new assets - USDC (via Noble), UM (Penumbra), NYM (Nym), and NTRN (Neutron) - to Namada's MASP and transparent platform. These assets were selected based on community feedback, ecosystem alignment, and ease of integration. Specifically, this proposal includes setting appropriate IBC rate limits and allowing these assets to be used for gas payment. The code used to produced the attached WASM can be found at: https://github.com/anoma/namada-governance-upgrades/blob/cccbb06948f258ceae935806ec17019f8838879e/phase3/src/lib.rs To summarize, the rate limit and gas parameters set for each token are: USDC: Global mint limit: 5M Per-epoch limit: 1M Gas price: 3 uusdc / gas unit UM: Global mint limit: 5M Per-epoch limit: 1M Gas price: 10 upenumbra / gas unit NYM: Global mint limit: 10M Per-epoch limit: 2M Gas price: 50 unym / gas unit NTRN: Global mint limit: 10M Per-epoch limit: 2M Gas price: 20 untrn / gas unit
Corrected - PGF - Discord Mod Allocations - 945k NAM
**This is a corrected proposal to replace Prop17--please vote 'nay' on Prop17.** Hello! 👋 I’m writing this on behalf of Luminara 🔅 ## Proposal This is a Public Goods Funding (PGF) proposal to allocate **945,000 NAM** in total to the Namada Discord moderators: * 180k NAM -- 0xGolden | deNodes `tnam1qz7mggh56wlljs0wfgkxj6r9xe36cacfkgnr99kc` * 180k NAM -- Tree `tnam1qpyrs8q9qzupca4gdalmwevkmdsyxenswq5xvstm` * 180k NAM -- kelpie `tnam1qqqdr4y4zymc3ctsthpy0fcezdn4jvjl6ye073k0` * 90k NAM -- Hoan Wu `tnam1qpnyherlyqel5x5xqyfqngpqymyeqrf5fgqvxc38` * 90k NAM -- Daniel | Mandragora `tnam1qzcgkzmddnru8w07zntd6wpywd8vptdgpu8mz44a` * 90k NAM -- sirouk | TuDudes `tnam1qq0t2s4dmqvxqwl25fm3eyckgekgftggfg9nfe5h` * 90k NAM -- TG `tnam1qq0ph5svjjspkaz2ntw49j2zq8855237qcfuupjt` * 45k NAM -- M | CryptoSJ `tnam1qpj9aye7zd86pgfpjh2pnal3yjzrfkff2s6n5fq4` This proposal code was tested successfully on the Housefire testnet: https://explorer75.org/namada-housefire/proposals/25 ## Context The people with mod roles in our Discord have stayed alert through quiet times, and helped us to weather storms through seasons of chaos. It’s been a long haul, and these folks have helped us chug along; 🚂 some since January 2023, others since January 2024. Mods were not included in the genesis proposal, but we think that this PGF proposal offers an opportunity to close that loop with gratitude and good faith. ## History Moderation hasn’t been a formal role in Namada. There was no understanding or agreement that mod privileges would come with compensation, and expectations were either left unspoken or were inconsistent across time, project phases, and responsible individuals. However, moderation *is* often compensated in other crypto communities, and some of these contributors moderate other crypto communities professionally. Others jumped in purely out of care and commitment to Namada’s early days. But all have supported our community through both calm and chaotic seasons. 🎢 While we haven’t treated this as a job, we do believe this is the right moment to recognize and thank them. This proposal acknowledges that ambiguity, and aims to resolve it cleanly. ## Future This isn’t about setting precedent. We believe moderation in our community, going forward, should not be transactional. Instead of moderators as enforcers or outsourced roles, we hope to encourage stewardship: welcoming newcomers, encouraging healthy dialogue, and supporting autonomy with the help of bots and tools to handle spam. This proposal will allow us to close the chapter on early moderation efforts with clarity, appreciation, and fairness, and move into our next chapter with stronger alignment. ## Thanks Thank you to @ke1pie, who has been instrumental in patiently carrying this forward for many months, and thank you to everyone who helped keep the lights on 💡
PGF - Discord Mod Allocations - 945k NAM
Hello! 👋 I’m writing this on behalf of Luminara 🔅 ## Proposal This is a Public Goods Funding (PGF) proposal to allocate **945,000 NAM** in total to the Namada Discord moderators: * 180k NAM -- 0xGolden | deNodes `tnam1qz7mggh56wlljs0wfgkxj6r9xe36cacfkgnr99kc` * 180k NAM -- Tree `tnam1qpyrs8q9qzupca4gdalmwevkmdsyxenswq5xvstm` * 180k NAM -- kelpie `tnam1qqqdr4y4zymc3ctsthpy0fcezdn4jvjl6ye073k0` * 90k NAM -- Hoan Wu `tnam1qpnyherlyqel5x5xqyfqngpqymyeqrf5fgqvxc38` * 90k NAM -- Daniel | Mandragora `tnam1qzcgkzmddnru8w07zntd6wpywd8vptdgpu8mz44a` * 90k NAM -- sirouk | TuDudes `tnam1qq0t2s4dmqvxqwl25fm3eyckgekgftggfg9nfe5h` * 90k NAM -- TG `tnam1qq0ph5svjjspkaz2ntw49j2zq8855237qcfuupjt` * 45k NAM -- M | CryptoSJ `tnam1qpj9aye7zd86pgfpjh2pnal3yjzrfkff2s6n5fq4` This proposal code was tested successfully on the Housefire testnet: https://explorer75.org/namada-housefire/proposals/25 ##Context The people with mod roles in our Discord have stayed alert through quiet times, and helped us to weather storms through seasons of chaos. It’s been a long haul, and these folks have helped us chug along; 🚂 some since January 2023, others since January 2024. Mods were not included in the genesis proposal, but we think that this PGF proposal offers an opportunity to close that loop with gratitude and good faith. ## History Moderation hasn’t been a formal role in Namada. There was no understanding or agreement that mod privileges would come with compensation, and expectations were either left unspoken or were inconsistent across time, project phases, and responsible individuals. However, moderation *is* often compensated in other crypto communities, and some of these contributors moderate other crypto communities professionally. Others jumped in purely out of care and commitment to Namada’s early days. But all have supported our community through both calm and chaotic seasons. 🎢 While we haven’t treated this as a job, we do believe this is the right moment to recognize and thank them. This proposal acknowledges that ambiguity, and aims to resolve it cleanly. ## Future This isn’t about setting precedent. We believe moderation in our community, going forward, should not be transactional. Instead of moderators as enforcers or outsourced roles, we hope to encourage stewardship: welcoming newcomers, encouraging healthy dialogue, and supporting autonomy with the help of bots and tools to handle spam. This proposal will allow us to close the chapter on early moderation efforts with clarity, appreciation, and fairness, and move into our next chapter with stronger alignment. ## Thanks Thank you to @ke1pie, who has been instrumental in patiently carrying this forward for many months, and thank you to everyone who helped keep the lights on 💡
PGF - Web3Privacy Now Donor Drop allocations
This is a PGF (public goods funding) proposal to distribute a total of 930,202 NAM 1. 905,202 NAM to the 241 Namada addresses listed here: https://docs.google.com/spreadsheets/d/1uMGqq1BtPlNP25DnCGmkw78DFFEW2le9BG0GgfueRAI/edit?gid=102995741#gid=102995741&range=A1 2. 25,000 NAM to Zenode tnam1qzpl026lpzugcukkrjam6n48vl9ycmp4zqdmrwvc Zenode is the creator of the Donor Drop front-end: https://github.com/zenodeapp/donor-drop-frontend We had several (missing) tnam addresses that were updated (please see the evidence provided here: https://docs.google.com/spreadsheets/d/1uMGqq1BtPlNP25DnCGmkw78DFFEW2le9BG0GgfueRAI/edit?gid=1821879449#gid=1821879449&range=A1). There were two participants that went over their maximum, and one that donated to Coin Center instead–Luminara 🔅 intends to reward these donations instead of requesting that from voters. If approved, this proposal will then take 50 days to execute and thus recipients will not receive their allocations until 50 days after the proposal passes. We are proposing a reduced delay from the original 60-day delay period because this proposal launched 10 days late, because it first required parameter change (see Prop15). ## History We (Luminara 🔅) launched Namada Prop13 (https://explorer75.org/namada/proposals/13), and are grateful that voters signalled support for a Donor Drop targeting the amazing Web3PrivacyNow team (https://web3privacy.info/) with additional support for Donor Drop front-end creator, Zenode. Attracting donations to the Web3Privacy Now team was an amazing opportunity. This is a team unrivalled in our space for pushing forward digital privacy and cypherpunk values: https://x.com/web3privacy/status/1901949939590021311 We were proud to use the newly open sourced, community built Donor Drop front-end to support the user experience: https://forum.namada.net/t/donor-drop-app-creator-allocations-340k-nam/1565 This was an incredible undertaking that has enabled the Donor Drop experience that we’ve come to love ❤️ When the Donor Drop window opened on Saturday, March 22, Web3Privacy Now’s ethereum address (https://etherscan.io/address/0xb8fbd9a43cc0ceb3d9ddd58b752979a77e6f0c1d) received nearly 300 donations in about 75 minutes, totalling 52 ETH, worth about $100k when the Donor Drop finished 👀 ## Future We’re excited to have again demonstrated this new way of attracting new community members while supporting impactful teams like Web3Privacy Now and Coin Center (https://forum.namada.net/t/donor-drop-success-36-78-eth-donated-to-coin-center/1492). Keep an eye out for future Donor Drops after Namada Mainnet Phase 5 👀 https://x.com/web3privacy/status/1903498584156156060 Please check out this forum post for almostFitz's summary of this campaign: https://forum.namada.net/t/donor-drop-progress-50-3-eth-donated-to-web3privacy-now/1628 Thanks to the many different kinds of participants 🙌 our second Donor Drop was a success 🎉 Special thanks to almostFitz for organizing this 🔆
Change max_proposal_period to 260 epochs
## Proposal This is a proposal to change `max_proposal_period` parameter to `260`. The Rust code used to make the wasm is here: <https://github.com/Luminara-Hub/govproposals/blob/main/testnet_max_proposal_period.rs> @brentstone (Heliax) has reviewed this code, @spork.Knowable has tested it--first locally and then we (Knowable) successfully tested the parameter change on the Housefire testnet: <https://explorer75.org/namada-housefire/proposals/23> ## Context Last week, I started [a discussion post](https://forum.namada.net/t/discuss-increasing-max-proposal-period-to-260/1637) about updating the max_proposal_period parameter to 260. Luminara committed to making a PGF proposal for the latest [Donor Drop allocations](https://forum.namada.net/t/web3privacy-now-donor-drop-allocations/1633) that waits a 60-day grace period before executing and distributing the allocations, but were not able to do so because `max_proposal_period` is 84 epochs (21 days), and 260 epochs (65 days) are needed. We (Knowable) would like to increase `max_proposal_period` to `260`--not just for Luminara to fulfill their commitment, but also for the betterment of Namada at large. ## History When Knowable [proposed the mainnet parameters](https://forum.namada.net/t/mainnet-parameter-discussions-knowables-proposal/753), we chose 84 epochs (21 days) because that's the longest we could imagine the community needing for a governance proposal. We hadn't anticipated that there could be novel ways of using enactment delays to distribute PGF. The benefit of increasing this parameter is that we could make a commitment in an up-front governance proposal, while having more control over delaying the proposal execution timing. ## Potential issue Someone could make a governance proposal with a very long voting period - this seems unlikely--at least until it's worth 2000 NAM to advertise something using a governance proposal - a future solution could be a new `max_proposal_voting_period` parameter to complement the existing `min_proposal_voting_period`, and then we could constrain the voting period without constraining the enactment delay There have been no concerns from the folks in the Validator Circle, 🟡 the replies on the forum post, and in messages with @brentstone and @cwgoes from Heliax.
PGF - Namada Builder Allocations
**This is a PGF (public goods funding) proposal asking voters to distribute a total of 2.05m NAM to the five (5) Namada addresses listed below,** in recognition of the Namada community builders. This proposal was tested and reviewed after being executed on the Housefire testnet: https://explorer75.org/namada-housefire/proposals/19 ## Specifics ✅ [Free and open-source](https://forum.namada.net/t/discussion-pgf-priorities-for-software-in-namada/1501) Namada software: * **Daniel / Mandragora - 750,000 NAM** - `tnam1qzcgkzmddnru8w07zntd6wpywd8vptdgpu8mz44a` - Namada indexing software, [Undexer](https://github.com/hackbg/undexer) -> [OSS licence](https://github.com/hackbg/undexer/blob/v4/LICENSE) - Namada IBC decoding library, [Fadroma](https://forum.namada.net/t/decoding-of-ibc-transaction-types-is-now-supported/1244) -> [OSS licence](https://github.com/hackbg/fadroma/blob/v2/LICENSE) ✅ Dedicated Namada explorer services: * **ProNodes - [Explorer75](https://explorer75.org/) - 300,000 NAM** - `tnam1qqd2ys42y2t5vgdtdx6epstnkykvjedxxsuc6lry` * **Bitszn - [Valopers](https://namada.valopers.com/) - 300,000 NAM** - `tnam1qzt4klml5za7zn05rx569s5hfcr4nfl8zc3d4fwu` * **Daniel / Mandragora - [Shielded Live](https://shielded.live/) - 250,000 NAM** - `tnam1qzcgkzmddnru8w07zntd6wpywd8vptdgpu8mz44a` * **[Coverlet Namada Explorer Beta](https://namada.coverlet.io/) - 250,000 NAM** - `tnam1qqsrhr894nnupdyu2fqrg290pyxd50pq5vrj8xtf` * **[Sproutstake Namada Explorer](https://namada-explorer.sproutstake.space/) - 200,000 NAM** - `tnam1qrfyg27adsuege6ef94rek5d6cvjcs2afyw9nrhq` These tnam addresses have been lifted from user profiles, Discord and/or the forum. If you use their services / software, you can tip them anytime! @shurinov @alx @Daniel @Leon @Oneplus ## Criteria If software is useful and being used by our community, **open sourcing it under an unrestrictive licence is kind of a big deal.** It's essentially giving the Namada community your work. I posted a bit about that here in https://forum.namada.net/t/discussion-pgf-priorities-for-software-in-namada/1501. ### Table stakes Namada's explorer services are not (yet) open source, so accuracy and reliability should be table stakes for consideration. The Namada community is totally dependent upon service providers to run the service and and to fix the issues, especially accuracy issues that may misinform Namada users and other stakeholders. There should also be a standard for what the service provides. It can be tempting to re-use a project across many Cosmos projects, for example, which can be fine if it's adding new value. Since Namada has a unique code-base, it can be hard to re-use code for querying and transacting, but we anticipate that a service worth recognizing will offer more advanced functionality than the very basics of network exploring, or the very basics of Namada transactions, especially if it's a service offering beyond Namada. As our ecosystem matures, this standard should also mature. For example, a niche service that provides shielded pool metrics and statistics is noteworthy if launched and running now, because this information is otherwise not easily accessible in a palatable way. Now imagine if these metrics were already fully integrated into the explorer services three months ago--launching such an app in this more mature ecosystem would not be adding new value. ### Differentiators Other key considerations we made for this proposal involved **impact** - how useful has this service / software been to those who use and/or contribute to Namada? how useful is it likely to be going forward? **advanced features** - is there something niche that's particularly useful? ie. solves a specific problem - is the entire set of features particularly useful? ie. a "one-stop shop" for a particular kind of activity **timing & activity** - how early and long-running is this service / software? - is functionality improving? do improvements reflect the needs of users and/or contributors or other stakeholders? ## Context Three weeks ago we called for what are essentially the first set of Namada Builder nominations: https://forum.namada.net/t/nominations-call-for-namada-apps-tools-and-services/1583 At this early stage of Namada, builders have primarily advanced Namada explorer code and services, critical to the Namada experience and ever-more important as we advance through Phases 4 and 5. These builders have dedicated their valuable attention and efforts to Namada, most of which did so before Namada was widely known, and are the earliest builders in our ecosystem. ## A bet on Namada's future Early stage builders in Namada have made risky bets, especially given the uncertainties around when Namada would launch. I remember saying I couldn't be part of our family vacation a few months before June 2023 because "Namada mainnet may be launching" 😅 Retroactive public goods funding is not just recognition--it's also a signal: 1) we're betting on a shared future with these builders 2) there's an opportunity for newcomers to attain a meaningful Namada position It could be that some of Namada's most important contributors haven't even joined yet. Namada PGF is a unique opportunity to drive Namada ownership toward **active** contributors, which benefits everyone invested in Namada's success. Let’s get these folks some more Namada ownership 🎊 and keep the PGF culture rolling. We're keeping an eye out for up-and-coming builders!
PGF Signalling - Donor Drop 2: Web3Privacy Now
**PGF Donor Drop - Web3Privacy Now** ## Signalling Proposal Hello 👋 I’m writing this on behalf of Luminara 🔅 We launched Namada Prop2 and Prop5: https://explorer75.org/namada/proposals/5 Voters signalled strong support for the first Donor Drop, which targeted the amazing Coin Center team 🦸 Now that the first Donor Drop is done, we’re proposing a second: **Web3Privacy Now 🎯** This is a **signalling proposal.** With your support, Donor Drop Round Two (R2) will look similar to Round One, but will include improvements and feedback suggested by you 🫵 ## Namada, will you support this? * Estimated 900k - 1.2M NAM total from Namada PGF * Aiming for 900k airdrop * 25k NAM for the creator of the Donor Drop front-end * 1.8% - 2.4% of the yearly PGF budget * Allocated to Web3Privacy Now donors (aiming to recognize ~47 ETH in donations) * Campaign estimated to last two weeks (Donor Drop window estimate ~3 days) * A follow-up rPGF proposal to distribute the NAM airdrop to donor addresses * airdrop should land approx. two months after the governance proposal passes Web3Privacy Now has an active group of builders, creators and policy advocates–they’ll be great partners, in addition to our own community efforts. Namada comms are prepped and ready to help with promotion, TuDudes is prepared to run our community-built Donor Drop app, and @almostFitz has an operations plan that he’s itching to launch 🔥🚀 What's neat is that the Donor Drop can be done before Phase 5, with the airdrop happening after Phase 5. ## Why Web3Privacy Now? Web3Privacy Now has become a cultural epicenter for teams, communities, and individuals answering the call to return to cypherpunk roots–namely, digital privacy. W3PN hosts events (https://docs.web3privacy.info/events/), creates educational content(https://docs.web3privacy.info/research/privacy-guides/) and research reports (https://docs.web3privacy.info/research/), enagages in advocacy, and creates social initiatives that bind us together as a community–beyond Namada, within crypto. They were our co-organizers for the Shielding Summit (https://shieldingsummit.org/) in Brussels ♥️ Check them out! and get involved (https://docs.web3privacy.info/get-involved/index) ## Donor Drop History The world’s first Donor Drop (https://forum.namada.net/t/namada-donor-drop-jan-18-15-00-utc/1465) was an experiment: **do public goods funding (PGF) more effectively using Namada’s novel PGF mechanism.** Coin Center was our donation target. Problem: orgs like Coin Center need runway, not a new token with no market. But there are people who *do* want a new pre-market token. Solution: the Namada community used Namada’s PGF technology to airdrop NAM to those who donated ETH to Coin Center 💡 People were surprised at how successful Donor Drop R1 was: - https://x.com/mineZcash/status/1880637283159908732 - https://forum.namada.net/t/donor-drop-success-36-78-eth-donated-to-coin-center/1492/3 - https://x.com/NeerajKA/status/1881344835246051364 - https://x.com/cwgoes/status/1880651442278858926 That’s because with hardly any promotion, ~200 donations were made to Coin Center in about 30 minutes, totalling 36.78 ETH (~$125k at that time). More recap here: https://forum.namada.net/t/donor-drop-success-36-78-eth-donated-to-coin-center/1492 And **we** were amazed at the grassroots community effort to build an app that supported the Donor Drop. In three weeks the app was done, and it was 🔥🤩 This is why we’d also like to include Zen’s Namada address in each subsequent proposal that we use this open-sourced Donor Drop front-end ❤️ https://github.com/zenodeapp/donor-drop-frontend ## Get involved We want to improve on operational processes, our partner relationship, community involvement, promotional reach within aligned communities, and we want to create a repeatable flow for MOOARR Donor Drops. Want to be involved? Any of these could help: 1. join the forum topic (https://forum.namada.net/t/signalling-donor-drop-round-two-web3privacy-now/1555) or Discord discussion (https://discord.com/channels/833618405537218590/1339662286436040854) with feedback (or advice) about the campaign and/or mechanism 2. tweet or tell a friend 3. something else that we haven't thought about PGF shouldn't be boring--let's usher in the new wave 🌊
PGF - Donor Drop app creator allocations
If voters approve this PGF (public goods funding) proposal, a total of 340,005.318008 NAM will be distributed to six (6) different Namada addresses: 1) tnam1qzpl026lpzugcukkrjam6n48vl9ycmp4zqdmrwvc - 237,192 NAM 2) tnam1qq9v0nxltxzktl5mz59yc7k32m4yczt8uqrhtpjs - 74,000 NAM 3) tnam1qqfvd2p3p204vnnr725cgq4u3lkjxqce6crgfpr5 - 13,800 NAM 4) tnam1qrqgs5e67esl3yjdq3dccls0470ctcm6m5kx4cal - 5.318008 NAM 5) tnam1qpyyq8ueltpa7kd9xq8twtymfq9886t4lsnterhs - 7,500 NAM 6) tnam1qr4va7cr0ag7s7zl3j70qsr5v3m9jxu6ucdktf4z - 7,500 NAM This proposal received strong community support (see replies): https://forum.namada.net/t/donor-drop-app-creator-allocations-340k-nam/1565 and was tested and verified on the Housefire testnet: https://explorer75.org/namada-housefire/proposals/12 ## Context To our knowledge, the Donor Drop was the first of its kind: https://forum.namada.net/t/donor-drop-success-36-78-eth-donated-to-coin-center/1492 The experience was made possible by some amazing folks that banded together to make an app to support the Donor Drop, an entirely grassroots effort. People were amazed at how successful the Donor Drop was, but were even more amazed at how engaged, dedicated, and talented our community is to be able to build and launch this app in ~3 weeks ❤️ ## Details It would be great to help recognize these amazing contributors with ✅ ~200k NAM for creating and supporting this Donor Drop app: - **Zen - 112,192 NAM** (56.1%) - tnam1qzpl026lpzugcukkrjam6n48vl9ycmp4zqdmrwvc - **Anon - 74,000 NAM** (37%) - tnam1qq9v0nxltxzktl5mz59yc7k32m4yczt8uqrhtpjs - **Bengt - 13,800 NAM** (6.9%) - tnam1qqfvd2p3p204vnnr725cgq4u3lkjxqce6crgfpr5 - **Rigorous - 5.318008 NAM** (~0%) - tnam1qrqgs5e67esl3yjdq3dccls0470ctcm6m5kx4cal Even though Anselm and Jojoraky didn’t end up being involved beyond the beginning, we’re grateful for their engagement and efforts 🎉 and want to help thank them with 15k NAM ❤️ ✅ Bonus thank you of 15k NAM for early Donor Drop app attempts: - **Anselm - 7,500 NAM** - tnam1qpyyq8ueltpa7kd9xq8twtymfq9886t4lsnterhs - **Jojoraky - 7,500 NAM** - tnam1qr4va7cr0ag7s7zl3j70qsr5v3m9jxu6ucdktf4z Zen recently *open-sourced his beautiful front-end,* 🤩 which can now be used to support future rounds 🎉 He is essentially giving it to our community. We’d like to ask voters to allocate an additional 125k NAM to Zen to help recognize him for giving our community (and the world) all of his front-end code 🎁 ✅ Free and open-source front-end software: - **Zen - 125,000 NAM** - tnam1qzpl026lpzugcukkrjam6n48vl9ycmp4zqdmrwvc We’d like to thank TuDudes for hosting this Donor Drop app, but perhaps it makes more sense to do this in a dedicated PGF proposal, since TuDudes has done so much Namada infrastructure work 🔥 ## Keep it up! Front-end work in general is predicted to be the kind of work that Namada will need most in the coming months and foreseeable future. Folks worked insanely hard on this, of their own accord, with no hint of compensation. The beauty of how Namada’s PGF works is that we can effectively drive increases in Namada network ownership toward active contributors. Let’s get these folks some more Namada ownership 🎊 and keep the PGF culture rolling.
Update the `claim-rewards` Tx WASM
Updating the `claim-rewards` tx wasm in the on-chain storage. Now when this tx is executed, an event will be emitted that contains the number of reward tokens claimed. This data will then be able to be indexed and integrated for a variety of service providers. This proposal is enabled by the recent Proposal #10 that raised the maximum block gas. The proposal code can be found at https://github.com/anoma/namada-governance-upgrades/blob/a9b40c048c4be587ac567bc65f59ffb5505b692d/update-tx-claim-rewards/src/lib.rs
Increase max block gas to 5M gas units
In anticipation of updating the claim-rewards tx wasm in the Namada on-chain storage, we first must increase the maximum allowed gas in a block. This must be done because the tx to initialize that proposal consumes about 4.3M gas units, whereas the current block maximum is 3M. This proposal increases the block maximum from 3M to 5M. The code used to produce the attached WASM can be viewed here: https://github.com/anoma/namada-governance-upgrades/blob/b26aff300654a791b91d8ff40483d7d2f0bf9d5f/max_block_gas/src/lib.rs
Give validators some more NAM to cover tx fees before Phase 5
Give 5 NAM to each validator that is currently not jailed or deactivated (inactive) with a one-time retroactive PGF payment. Also give this amount to a couple accounts that wish to use the NAM to pay fees for initializing a validator.
Phase 3: enable the flow of non-native assets into Namada and the Shielded Pool
Increase IBC rate limits (global mint and per-epoch throughput) for 6 different assets, allowing them to flow into and out of the Namada mainnet. Additionally, each of these assets is whitelisted for gas payment for any Namada transaction at a specific cost per gas unit. This proposal whitelists Osmosis, Cosmos Hub, Celestia, and the Stride liquid-staked versions of these tokens. These assets will also be able to flow into the Namada shielded pool. The code attached to this proposal to execute can be viewed at: https://github.com/anoma/namada-governance-upgrades/blob/a4d6906a0dca2cbf4ddd55f066a0f09cc58aec26/phase3/src/lib.rs. The details for each token, with their denomination strings, are: OSMO: transfer/channel-1/uosmo Mint limit: 10,752,692 OSMO Throughput limit per epoch: 2,150,539 OSMO Gas price: 10 uosmo / gas unit ATOM: transfer/channel-2/uatom Mint limit: 759,878 ATOM Throughput limit per epoch: 151,976 ATOM Gas price: 1 uatom / gas unit TIA: transfer/channel-3/utia Mint limit: 1,018,330 TIA Throughput limit per epoch: 203,666 TIA Gas price: 1 utia / gas unit stOSMO: transfer/channel-0/stuosmo Mint limit: 8,196,721 stOSMO Throughput limit per epoch: 1,639,344 stOSMO Gas price: 10 stuosmo / gas unit stATOM: transfer/channel-0/stuatom Mint limit: 512,821 stATOM Throughput limit per epoch: 102,564 stATOM Gas price: 1 stuatom / gas unit stTIA: transfer/channel-0/stutia Mint limit: 946,970 stTIA Throughput limit per epoch: 189,394 stTIA Gas price: 1 stutia / gas unit
PGF - Fee grant to support Namada IBC relayer operators
## Author Daniel from Mandragora validator is submitting this proposal. ## Context As Mandragora is leading IBC channels creation and maintenance for Namada’s mainnet (along with collaboration for supporters information collection with Cosmic Validator), I have detected a problem, but I found out a potential. ## Problem We have detected that indeed genesis accounts are needed to be used as relayer accounts, just like in Housefire testnet, but that could be problematic when it comes to mainnet. ## Solution It consists in funding supporters’ Namada relayer accounts via a PGF proposal - as a fee grant to support them and to avoid using genesis accounts as relayer accounts on mainnet. Retroactive Public Goods Funding (RPGF) mechanism lets to directly send them the fee grant from the PGF Treasury. ## Proposed amount We are proposing to distribute total of 50,050 NAM, i.e. 3,850 NAM to 13 IBC relayer operators. ##Comments These funds couldn’t be used for other purposes, and relayer accounts would be monitored from time to time. ## IBC Relayer Operators These are Mandragora, Cosmic Validator, Sproutstake, max-02, pro-nodes75, Architect Nodes, OriginStake, Stake&Relax, anodeofzen, ContributionDAO, ValidatorVN, Inter Blockchain Services and Citizen Web3.
PGF - accompanying fix for Donor Drop Prop5
This is a PGF (public goods funding) proposal to distribute a total of 5,000 NAM to these two Namada addresses: 1) tnam1qzkx2k6zxjcdxf5tz4ep55mj4ll2kq7wsyrd5k5u - 1,667 NAM 2) tnam1qr649fhvu3f3mdaxs80mm7gsm5uyegsv4g596flz - 3,333 NAM It won't be valid unless Prop5 is also approved. ## Context Gavin Birch has launched this proposal on behalf of Luminara 🔅 We also launched Namada Prop5: https://explorer75.org/namada/proposals/5 However, if Prop5 is approved, two addresses will not receive their intended totals because of an interesting phenomenon: if the PGF proposal contains more than one entry for the same address *and* the same number of NAM, only one of the entries is actually enacted. Prop5 intentionally had one duplicate entry, which the protocol is ignoring, and the other duplicate is the incorrect tnam address (corrected in this proposal). It's a unique set of circumstances (ie. transfers disabled) that we ask you to approve this relatively small PGF proposal as a solution to the problem that arose from this issue: https://github.com/anoma/namada/issues/4380 ## Future We recommend summing a total for each address in future, instead of multiple entries for the same address. Additionally, the duplication error could have been discovered with more thorough data analysis of the Housefire test proposal. Huge thanks to Zen 🦸 and Rigorous 🦸 for discovering and reporting this!
PGF - Coin Center Donor Drop allocations
This is a PGF (public goods funding) proposal to distribute a total of 1,225,986 NAM to the 188 Namada addresses listed here: https://docs.google.com/spreadsheets/d/1uMGqq1BtPlNP25DnCGmkw78DFFEW2le9BG0GgfueRAI/edit?gid=764951800&range=F2. This proposal has been tested and successfully executed on the Housefire testnet: https://namada-explorer.sproutstake.space/test/proposals/6 ## Context Gavin Birch has launched this proposal on behalf of Luminara 🔅 We previously launched Namada Prop2, and are grateful that voters signalled strong support for our proposed Donor Drop that targeted the amazing Coin Center team: https://forum.namada.net/t/draft-signalling-proposal-will-you-support-an-airdrop-campaign-using-namadas-pgf/1338 The Donor Drop is done, 🎉 many thanks to the many different kinds of participants 🙌 ## Details The aim was to award 1m NAM, the lower boundary of this draft proposal: https://forum.namada.net/t/draft-signalling-proposal-will-you-support-an-airdrop-campaign-using-namadas-pgf/1338, but we are instead asking you to approve this proposal to distribute ~1.226m NAM. This is to reward donors whose donations were not reported during the Donor Drop tally, due to issues such as invalid/missing tnam addresses. There are plausible reasons for why this happened, and we now have some learnings, and we'd still like to thank and welcome these participants to our community. Please see details here: https://docs.google.com/spreadsheets/d/1uMGqq1BtPlNP25DnCGmkw78DFFEW2le9BG0GgfueRAI/edit?gid=1986442751&range=A1 **Note:** 1. We've provided evidence for all corrected addresses with the exception of two, highlighted in red at the top of the spreadsheet. We'd like to give them the benefit of the doubt and reward them regardless. There were no competing claims on these two donations, totalling 6,666 NAM. 2. There were four donations that attempted to participate but arrived some time after the Donor Drop ended. We are not asking that they be included in this proposal, and instead, I personally would like to thank and reward them once transfers are enabled in Phase 5. ## History Shortly after Prop2 passed, at least seven Namada community members independently and collaboratively got involved at different times and in different ways on a few potential Donor Drop app solutions. It was an incredible grassroots initiative in support of our first Donor Drop, with dedication that far exceeded my expectations 🔥 When the Donor Drop window opened on Saturday, January 18, Coin Center’s ethereum address received nearly 200 donations in about 35 minutes, totalling 36.78 ETH, worth about $125k when the Donor Drop finished 👀 ## Mooaar Donor Drops This will be a testament to Namada's novel technology, and we hope that others will use and improve upon the Donor Drop distribution mechanism & strategy. Please check out this forum post for the full summary of this campaign: https://forum.namada.net/t/donor-drop-success-36-78-eth-donated-to-coin-center/1492
Coordinating mainnet software upgrade to namada v1.1.1 at height 894,000
Gathering social consensus to coordinate a software upgrade of namada nodes at block 894,000. This block is expected to occur in between 15:00 and 16:00 UTC on Thursday, Feb 13, 2025.
Parameter change: Increase target_staked_ratio to 0.55
Namada’s target_staked_ratio is set to “0.4”. This means that **if more than 40% of the Namada token supply is staked, Namada’s staking inflation will begin decreasing towards zero.** Such a dramatic change at such an early stage could dampen our momentum by prematurely causing validators to exit from Namada, while not necessarily decreasing stake. The ratio has risen sharply over the past week or so, and **we now have ~36.4% of the NAM supply staked.** We think that the time to increase the target is now, and Knowable is proposing that the new target be 55%. The only change from passing this proposal is that staking inflation (and thus, staking rewards) won’t begin decreasing if more than 40% of the NAM supply is staked. Instead, this will begin decreasing if more than 55% is staked. We’re proposing that the target be 55% because engaged members of our community have signalled that: a) they favour increasing the rate and b) they favour a target between 50% and 60%. - **Compelling?** Please vote yay - **Disagree?** Please vote nay (and please post why in the forum topic!) - **Unsure?** Comment/question in the forum topic, or vote abstain Forum topic: https://forum.namada.net/t/proposal-increase-target-staked-ratio-from-40-to-55/1387 Engaged members of our community have also signalled that that this proposal would be a temporary fix, not a permanent solution, and we agree. We should identify a more permanent solution, but we think that **we’ll need some observations after the Phases of Mainnet** to better understand and to discuss introducing a more informed solution. Please review or ensure that someone capable has reviewed the wasm used for this proposal, and verify the hash: https://github.com/anoma/namada-governance-upgrades/blob/ce3a49eb93246aa81e6358e87d98f75bf69f5612/increase_target_staked_ratio/src/lib.rs This proposal and wasm were successfully executed on Housefire as Prop3: https://forum.namada.net/t/proposal-increase-target-staked-ratio-from-40-to-55/1387/6
Donor Drop: Coin Center campaign signalling
**PGF Donor Drop - Coin Center** Namada stakers and validators, I'm Gavin Birch 👋 (https://twitter.com/Ether_Gavin) Submitted on behalf of Luminara, we are proposing that Namada support a Donor Drop for Coin Center. **tl;dr** Instead of directly donating $NAM tokens, we can use PGF to drive ETH donations to Coin Center by rewarding donors with NAM. Coin Center gets funding in ETH (instead of selling NAM), and donors get pre-market access to NAM. So far our community likes this idea. Stakers, this is a **signalling** proposal to gauge your interest. We want Namada to use PGF to broaden the distribution of NAM, while driving donations to Coin Center's ethereum address: 0x15322B546e31F5Bfe144C4ae133A9Db6F0059fe3 - **Compelling?** Please vote yay - **Disagree?** Please vote nay (and please post why in the forum topic!) - **Unsure?** Comment/question in the forum topic, or vote abstain Read on.. Forum topic: https://forum.namada.net/t/draft-signalling-proposal-will-you-support-an-airdrop-campaign-using-namadas-pgf/1338 I'm pretty excited that this could be an elegant new token distribution mechanism/strategy, and I hope that other communities will copy it. Please see my amateurish diagram: https://forum.namada.net/t/draft-signalling-proposal-will-you-support-an-airdrop-campaign-using-namadas-pgf/1338/8 **Key details** - ~3 weeks for the campaign and/or donation window - a follow-up PGF proposal to allocate 1,000,000 NAM to the donors The mechanism isn't finalized yet, but it may involve a donation cap and time weighting like this (ignore the $ values!): https://www.online-python.com/4hLxJ2VQ7r Again, this is only a signalling proposal; we will need to follow up with a PGF proposal with the list of donor tnam addresses so that Namada's PGF can distribute NAM to them. (What's neat is that this can be done before Phase 5.) If you would like to be involved, any of these could help: 1. respond on the forum topic with feedback (or advice) about the campaign and/or mechanism (https://forum.namada.net/t/draft-signalling-proposal-will-you-support-an-airdrop-campaign-using-namadas-pgf/1338) 2. tweet about or tell a friend 3. help make a front-end page to see donations in real-time 4. something else that we haven't thought about PGF shouldn't be boring--let's usher in the new wave 🌊 Thank you to all of the folks who have helped 🙌
Phase 2: activate inflation for staking rewards and PGF
Namada mainnet has been running smoothly since Dec 3. As of Dec 11, 16.7% NAM has been staked. We (Luminara) think that Namada is ready for Phase 2: activate inflation for staking rewards and PGF. PoS max annual inflation rate = 5%; PoS target staked ratio = 40%; Kp gain parameter = 0.5; Kd gain parameter = 0.5; PGF annual inflation rate = 5%. PGF Steward inflation will be off for now. Our understanding is that this proposal was successfully tested on the Housefire fork (which is now in Phase 2) using this code: https://github.com/anoma/namada-governance-upgrades/blob/f1d19a5d4d28595ee73fe8fd15a9b4319bb171ff/phase2/src/lib.rs
Bengt for Steward
In addition to the obvious candidates like the good people at Penumbra, Zcash, Ethereum Foundation, InformalSystems, Keplr, to name a few, we have a large number of external libraries and crates that Namada depends on. Take for example rustwasm, which is essential for even making this proposal.