proxmox/token-lists/docs/TOKEN_LIST_POLICY.md

Token List Inclusion Policy

Version: 1.0
Last Updated: 2025-12-22
Network: ChainID 138 (DBIS Chain)

---

Overview

This document defines the inclusion and delisting policy for the DBIS Chain 138 Token List. All tokens must meet these requirements to be included in the list.

---

Inclusion Requirements

Required Criteria

1. Contract Verification

   • Contract source code must be verified on the block explorer (if available)
   • Contract address must have deployed bytecode

2. Chain ID

   • Token must be deployed on ChainID 138
   • Chain ID must be correctly specified in the token list entry

3. Contract Standards

   • ERC-20 tokens must implement standard ERC-20 interface
   • Oracle feeds must implement Chainlink-compatible interface
   • All functions (decimals, symbol, name, etc.) must be callable

4. Metadata Accuracy

   • decimals, symbol, and name must match on-chain values
   • Address must be EIP-55 checksummed
   • Logo URL must be accessible and return valid image

5. Security

   • No known security vulnerabilities or exploits
   • No fake branding or impersonation
   • Contract must be audited (preferred) or have disclosed upgradeability

Preferred Criteria

1. Audit Status

   • Public security audit reports preferred
   • Links to audit reports should be provided

2. Upgradeability

   • Immutable contracts preferred
   • If upgradeable, admin keys and upgrade process must be disclosed

3. Governance

   • Decentralized governance preferred
   • Centralized admin keys should be disclosed

4. Liquidity

   • Sufficient liquidity for trading (if applicable)
   • Active trading volume (if applicable)

---

Token Categories

Tokens are categorized using tags:

• core: Native-wrapped tokens (e.g., WETH), stablecoins
• defi: DeFi protocol tokens (DEX LP tokens, lending tokens)
• oracle: Oracle price feed contracts
• experimental: New or unproven tokens (use with caution)

---

Delisting Criteria

Tokens will be removed from the list if:

1. Security Issues

   • Exploit or security vulnerability discovered
   • Rug pull or exit scam
   • Malicious contract behavior

2. Compliance

   • Legal or regulatory issues
   • DMCA takedown requests
   • Court orders or legal injunctions

3. Misrepresentation

   • Fake branding or impersonation
   • Incorrect metadata that cannot be corrected
   • Violation of trademark or copyright

4. Technical Issues

   • Contract no longer functional (e.g., permanently paused)
   • Migration to new contract address (old address removed)
   • Chain migration (token no longer on ChainID 138)

5. Inactivity

   • Token no longer in use
   • No trading activity for extended period
   • Project abandoned

---

Governance Process

Adding Tokens

1. Request Submission

   • Create issue or pull request with token details
   • Include contract address, metadata, and verification evidence
   • Provide links to audits, documentation, or verification

2. Review Process

   • Code owners review submission
   • On-chain verification performed
   • Security assessment (if applicable)

3. Approval

   • Requires approval from at least one code owner
   • All validations must pass
   • Version bump (minor for additions)

Removing Tokens

1. Delisting Request

   • Create issue explaining reason for delisting
   • Provide evidence (exploit reports, legal notices, etc.)

2. Review Process

   • Code owners review delisting request
   • Verify claims and evidence
   • Consider impact on users

3. Execution

   • Requires approval from at least one code owner
   • Version bump (major for removals)
   • Update CHANGELOG.md with reason

---

Versioning Policy

Token list versions follow semantic versioning:

• Major (x.0.0): Token removals, breaking changes
• Minor (x.y.0): Token additions
• Patch (x.y.z): Metadata fixes (name, symbol, logo), no address changes

---

Contact

For questions or concerns about the token list policy:

• Create an issue in the repository
• Contact DBIS team maintainers

---

Last Updated: 2025-12-22