0. Proposer Info
- Email:
[insert proposer email] - Proposer’s Project Name:
[insert project name] - Proposer’s X (Twitter) Account:
[insert X profile URL] - Affiliation:
[State whether proposer is affiliated with the protocol or a token in the pool]
1. TL;DR
Proposing to [Whitelist / Delist / Update Parameters for] the token pair [X-INIT] for Enshrined Liquidity.
Summary of the motivation and expected impact:
[1–2 sentences]
2. Background
2-1. Token Pair Info & Context:
- Token Name / Symbol:
[X] - LP Pair:
[X-INIT] - Pool Type:
- Pool Parameters:
2-2. Token Details
-
Name:
[Insert name] -
Symbol:
[Insert symbol] -
Origin Chain:
[Insert origin chain]- state where the token minting happens
-
Contract Address:
[Insert address] -
Total Supply Cap:
[Insert or N/A] -
Circulating Supply:
[Insert current supply] -
Token Type:
[LST / Stablecoin / Governance / Other] -
Upgradability:
[Yes/No] + Details -
Control:
[Multisig / DAO / Permissionless] -
Contract Verified?
[Yes/No] -
Special Mechanics:
[e.g., Custom mint/burn, Peg stability, etc.] -
Bridge Used:
[Insert name]- only include this field if the token to-be-whitelisted is a bridged token
3. Proposed Parameters
| Field | Proposed Value | Example | Description |
|---|---|---|---|
| Reward Weight | 1000000000000000000 | RewardWeight is registered to distribution’s Params | |
| Token Metadata | 0x… | Dex coin LP metadata address |
4. Rationale & Impact
Explain why this token should be added/removed or why parameters should be adjusted:
- Economic Rationale:
[e.g., incentivize liquidity, adjust for market activity, rebalance emissions] - Ecosystem Impact:
[e.g., benefits for LPs, protocol alignment, risk mitigation] - Community Consideration:
[e.g., requested by dApp teams, community sentiment]
Governance Votes
- YES – You support the proposed change to Enshrined Liquidity.
- NO – You do not support the change.
- NO WITH VETO – You believe the proposal is harmful, spam, or violates governance principles.
- ABSTAIN – You are neutral but want to contribute to quorum.
References / Appendix (Optional)
- [Link to code or registry entry]
- [Forum thread or previous discussions]
- [Relevant data, analysis, or dashboards]
- [Additional context or visualizations, if any]