> For the complete documentation index, see [llms.txt](https://service.block-pro.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://service.block-pro.net/hub/namada-hub/governance.md).

# Governance

Explore past and active governance proposals with summaries, links, and voting instructions. Learn how to participate in the Namada governance process.

***

<details>

<summary>Proposals #19. Whitelisting USDC, UM, NYM, and NTRN for Namada</summary>

**Voting Period:** May 2, 2025, 09:05:52 – May 8, 2025, 03:05:28 (UTC)

**Details:** 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. The proposal sets IBC rate limits and allows these assets to be used for gas payments.

Technical parameters:

USDC

* Global mint limit: 5,000,000
* Per-epoch limit: 1,000,000
* Gas price: 3 uusdc / gas unit

UM

* Global mint limit: 5,000,000
* Per-epoch limit: 1,000,000
* Gas price: 10 upenumbra / gas unit

NYM

* Global mint limit: 5,000,000
* Per-epoch limit: 2,000,000
* Gas price: 50 unym / gas unit

NTRN

* Global mint limit: 10,000,000
* Per-epoch limit: 2,000,000
* Gas price: 20 untrn / gas unit

**Discussion:** [**https://forum.namada.net/t/proposal-add-support-for-usdc-usdy-um-nym-ntrn/1648**](https://forum.namada.net/t/proposal-add-support-for-usdc-usdy-um-nym-ntrn/1648)

**How the BlockPro validator votes and why:**\
✅ **Vote:** Yes

**Rationale:**

BlockPro supports the inclusion of USDC, UM, NYM, and NTRN as it enhances Namada’s interoperability, aligns with the broader ecosystem, and provides users with more options for gas payments and liquidity. The proposal includes reasonable rate limits and gas fees, minimizing systemic risks while encouraging adoption. We also appreciate the community-driven asset selection process and transparency of the implementation.

</details>

<details>

<summary>Proposals #20. Signalling - Support for Wormhole as Namada’s First New Bridge Integration</summary>

**Voting Period:** May 4, 2025, 14:05:27 – May 14, 2025, 03:05:19 (UTC)

**Details:**\
This proposal asks voters to signal support for integrating **Wormhole** as Namada’s first new bridge integration. The goal is to expand Namada’s interoperability with other ecosystems, aligning with its vision of being a composable privacy layer across chains. If approved, Heliax will prioritize engineering resources to implement Wormhole integration.

The proposal notes Wormhole’s broad adoption and reliability despite its early 2022 exploit, highlighting its recovery, continued growth, and position as the leading bridging solution for many new chains. This integration is intended as a first step and does not exclude future bridge integrations like IBC Eureka.

**Discussion:** <https://forum.namada.net/t/prioritize-building-out-a-wormhole-integration/1652>

**How the BlockPro validator votes and why:**\
✅ **Vote:** Yes

**Rationale:**\
BlockPro supports this proposal as it aligns with Namada’s mission to enable privacy across multiple ecosystems by broadening the range of supported assets and chains. Integrating Wormhole will unlock new opportunities for shielded asset transfers and composability. We recognize the concerns raised about Wormhole’s past security incident but believe its resilience, adoption, and improvements since then demonstrate maturity and readiness for integration. Supporting Wormhole now accelerates Namada’s growth without limiting future bridge options.

</details>

<details>

<summary>Proposals #21. Coordinating mainnet software upgrade to namada v101.0.0 at height 2,176,000</summary>

**Voting Period:** May 19, 2025, 15:05:09 – May 22, 2025, 21:05:45

**Details:** This proposal seeks social consensus to coordinate a software upgrade of Namada nodes at block height 2,176,000, expected around 15:00 UTC on Tuesday, May 27, 2025. The upgrade involves a hard fork to transition Namada mainnet to version v101.0.0, alongside updates to off-chain infrastructure such as indexers. The goal is to prepare the network for the upcoming Phase 4, with discussions for Phase 4 to occur separately. The upgrade has been successfully tested on Campfire and Housefire testnets, and detailed instructions for operators are available in a hackMD document. The proposal encourages community discussion to finalize the upgrade plan.

**Discussion**: <https://forum.namada.net/t/coordinating-the-pre-phase-4-hard-fork-upgrade-to-namada-v101/1670>

**How the BlockPro validator votes and why:**\
✅ **Vote:** Yes

**Rationale:**\
BlockPro supports this proposal as it ensures Namada’s mainnet remains robust and ready for future phases, particularly Phase 4.&#x20;

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://service.block-pro.net/hub/namada-hub/governance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
