Community Pool Spend #1: Access, Data and Security
MANTRA proposal #42: # Adopting the Community Pool Proposal Template and Approving Community Pool Spend #1 Dear Sherpas, With Proposal 39, Sherpas created th...
Yes
100%
No
0%
Abstain
0%
Veto
0%
If passed
AI Summary
gpt-6-luna - generated 11/20/2026, 1:11:00 AM
Community Pool Spend #1: Access, Data and Security
Proposal 42 establishes a standard template and standing rules for Community Pool spending, then uses them to request 17,500,000 $MANTRA (approximately $38,900) to renew MANTRA Chain’s Hyperlane cross-chain bridge integration. A YES vote approves both the template and this first spend.
- Requires future Community Pool spend proposals to use a common format covering purpose, amounts, recipients, community benefit, and deliverables.
- Sets standing rules for named recipients, pricing based on CoinGecko with a buffer of up to 15%, reporting within 90 days or earlier upon completion, and returning unspent funds.
- Makes recipients with overdue reports ineligible for further Community Pool funding until they report.
- Requests 17,500,000 $MANTRA for Hyperlane bridge renewal, paid to the listed address if the proposal passes.
Voter Impact
A YES vote adopts the required Community Pool proposal template and authorizes the first spend: 17,500,000 $MANTRA for bridge renewal. The proposal says funds transfer automatically if it passes.
Risk Signals
- The proposal describes bridge access benefits but gives no detailed renewal scope, milestones, or service terms.
- The approximate USD value may change; the template allows a price-movement buffer of up to 15%.
- A report and return of unspent funds are required, but the proposal does not specify enforcement procedures.
Original Proposal Text
# Adopting the Community Pool Proposal Template and Approving Community Pool Spend #1 Dear Sherpas, With Proposal 39, Sherpas created the **MANTRA Chain Community Pool** and established clear governance over its use: every drawdown requires its own onchain spend proposal, must identify the amount and its intended use, and is subject to transparent reporting. As part of that proposal, MANTRA committed to publishing a standard template for spend proposals. With this proposal, we present that template, the **Community Pool Proposal Template**, for your approval, and put it to its first use: **Community Pool Spend #1**, which renews funding the cross-chain bridge integration. The template and Spend #1 follow below. We would like to ask for your support and approval. ## Proposal Summary Voting **YES** approves and endorses the following: 1. Adopt the [**(1) Community Pool Proposal Template**](#1-community-pool-spend-template), set out below, as the required format for every proposal to release $MANTRA from the Community Pool, together with its standing rules. 2. Approve [**(2) Community Pool Spend #1**](#2-community-pool-spend-1-access-data-and-security), set out below using the aforementioned template format: 17,500,000 $MANTRA from the Community Pool to renew the cross-chain bridge integration. ## 1. Community Pool Spend Template The Community Pool funds initiatives that expand the MANTRA Chain community. A single template gives every Sherpa the same basis on which to evaluate a request to release funds, and holds every proposer, including MANTRA Chain Association (MCA), to the same standard. Every proposal under the template contains the following sections: | Section | What it covers | | :---- | :---- | | **Intro** | Explains what is being funded and why it is needed now. | | **Proposal Summary** | States the total amount and lists each item a YES vote approves. | | **Line Items** | Lists each item with its Proposal 39 mandate area and its amount in \$MANTRA and approximate USD. | | **Receiving Address** | Gives the address that receives each line item. | | **Community Benefit** | Explains how each item expands the MANTRA Chain community and names a deliverable Sherpas can check. | | **Closing** | Contains the endorsement, the Forum link and the voting period. | The following standing rules apply to every Community Pool spend: 1. **Named recipients.** Each line item pays one publicly disclosed address through its own onchain message. Multiple items may share one recipient address if needed. 2. **Fixed pricing.** Amounts are set in $MANTRA at the CoinGecko price on the day of submission, plus a buffer of up to 15% for price movement during the voting period. 3. **Report and return.** Recipients publish a report, including transaction hashes, within 90 days of receiving funds or on completion if earlier. Any unspent funds are returned to the Community Pool. 4. A recipient with an outstanding report from a previous spend is not eligible for further funding until that report is published. Following approval, the template and these rules will be published in the official MANTRA Chain documentation. We will keep an updated version of the Community Pool Proposal template under [https://docs.mantrachain.io/community-pool](https://docs.mantrachain.io/community-pool). Following below is the very first Proposal making use of the template: ## 2. Community Pool Spend #1: Access, Data and Security Dear Sherpas, Spend #1 funds the renewal of MANTRA Chain’s cross-chain bridge integration under the mandate set by Proposal 39. The bridge is how our users move assets onto and off MANTRA Chain, and renewing it keeps that route open. ### Summary Voting **YES** approves and endorses the following: 1. Release **17,500,000 `$MANTRA`** (approx. $38,900) from the Community Pool as Community Pool Spend #1 for cross-chain bridge renewal. 2. Commit the recipients to the standing rules set out in this proposal, including reporting and the return of any unspent funds to the Community Pool. ### Line Items | **#** | **Item** | **Mandate area (Proposal 39)** | **`$MANTRA`** | |-------|----------------------------|----------------------------------------------------|----------------| | 1 | Bridge Renewal (Hyperlane) | Bridge, interoperability and exchange integrations | 17,500,000 | | | **Total** | | **17,500,000** | ### Receiving Address | **#** | **Address** | |-------|-------------------------------------------------| | 1 | `mantra1wc3fykky6rjzmlreh8t7wcyn7r2ls6s4gk6p70` | Each line item is paid to its address through its own `MsgCommunityPoolSpend` message. Funds transfer automatically if this proposal passes. ### Community Benefit **Bridge Renewal:** Provides users and applications with a supported route to bring assets onto MANTRA EVM from other chains. ### Closing Thank you Sherpas for your continued support. We invite every Sherpa to consider the proposal and participate in the vote. --- ## Conclusion Approval of this proposal constitutes an endorsement of Item (1) to (2) of the main Proposal Summary section above. Point (1) being the community pool proposal template, and point (2) the actual first `$MANTRA` release using the named template. More details: ipfs://CID