Proposer: MAP Protocol Foundation
Date: 21/10/2026
Timeline
The voting period for this proposal will end on 28/10/2026.
Background
As MAP Protocol’s cross-chain ecosystem continues to grow, connected blockchains differ in security, actual cross-chain demand, ecosystem activity, and maintenance costs.
Adding or maintaining support for a chain requires technical integration, security assessment, infrastructure, and ongoing maintenance. MAP Protocol therefore needs consistent, transparent criteria for determining which chains to support and when support should be suspended.
This proposal establishes two types of community governance proposals: Chain Listing Proposals and Chain Support Suspension Proposals. The community will review the supporting information and vote on whether to add or suspend support for a specific chain.
Proposal Details
1. Currently Supported and Suspended Chains
MAP Protocol currently supports the following chains:
Support for the following chains is currently suspended:
These lists record the current chain support status as of the date of this proposal. Future additions or suspensions will be submitted to a community vote under the framework below, and the lists will be updated after the approved changes are implemented.
A suspended chain seeking reinstatement must submit a new Chain Listing Proposal for community approval.
Support for a chain does not automatically include every asset, application, or cross-chain route on that network.
2. Community Decision-Making Framework
Changes to chain support will be managed through two types of proposals:
Each proposal must identify the chain and the scope of support affected, including the relevant functions, assets, and cross-chain directions where applicable.
3. Evaluation Criteria for Chain Listing
A Chain Listing Proposal should provide evidence addressing the following criteria:
Security and technical feasibility are prerequisites for listing. Subsidies, promised transaction volume, or integration payments cannot replace these requirements.
For early-stage chains with limited historical data, the community may consider specific use cases, ecosystem development, and potential cross-chain demand when assessing the value of integration.
4. Required Information for a Chain Listing Proposal
Each Chain Listing Proposal should include:
-
Chain Overview: Network name, technical architecture, ecosystem, and operating status.
-
Rationale for Listing: Why MAP Protocol should support the chain and which specific needs the integration would address.
-
Evaluation Findings: Evidence covering security, technical feasibility, demand, liquidity, and costs.
-
Scope of Support: The proposed functions, assets, and cross-chain directions to be enabled.
Following community approval, the relevant technical teams will complete the necessary testing and security validation before activating support and publishing an official announcement.
5. Suspension Criteria and Proposals
Support may be proposed for suspension due to persistently low usage, unsustainable maintenance costs, significant security risks, recurring service failures, technical incompatibility, or discontinued chain maintenance.
Each proposal must state its reasons, supporting evidence, affected services, and effective dates. Usage and cost assessments should normally cover 90 days, or the available operating period, excluding artificial activity where identifiable. Short-term volume or price fluctuations alone are insufficient grounds.
Suspension requires a community vote, except for emergency measures below.
6. Notice and Emergency Measures
Approved non-emergency suspensions should be announced through official channels at least 15 days in advance, stating the affected services, effective dates, and required user actions. Safe asset withdrawals or redemptions should remain possible where feasible, and pending transactions should be addressed.
For urgent security risks, a governance-authorized operator may immediately pause affected services without advance notice, promptly disclose the impact and next steps, and submit any continued suspension to a community vote.
7. Reinstatement and Transparency
Reinstatement requires a new Chain Listing Proposal, evaluation against the listing criteria, and community approval. Evaluation findings, voting results, implementation outcomes, and updated support lists should be public.
Adopting this framework does not itself list or suspend any chain; individual changes require separate proposals.
Expected Outcomes
1. Clear Community Decision-Making
The two proposal types give the community a direct role in deciding how MAP Protocol’s cross-chain network expands and changes.
2. Improved Security and Service Quality
Consistent security, technical, and maintenance requirements help reduce the impact of unreliable connections on the protocol and its users.
3. More Effective Resource Allocation
Development and maintenance resources can be directed toward chains with actual demand, ecosystem value, and sustainable operating conditions.
4. Greater Predictability for Users and Developers
Public assessments, community voting, and advance notice reduce uncertainty around changes to chain support.
Conclusion
This proposal establishes consistent criteria for MAP Protocol’s chain support decisions through two community voting mechanisms: Chain Listing Proposals and Chain Support Suspension Proposals.
With transparent evidence, community decisions, and clear implementation, MAP Protocol can continue expanding its cross-chain ecosystem while prioritizing user asset safety, service quality, and long-term sustainability.
Vote
The community is invited to vote on adopting the chain listing and suspension criteria and governance framework set out in this proposal.
Voting Options:
For: Adopt this proposal.
Against: Reject this proposal.
Abstain: Express neither support nor opposition.
Cast your vote on the proposal 
MAPO Governance.