Market-listing governance threshold
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-072 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
SushiSwap v2 and v3 both use fully permissionless pool creation. Any ERC-20 token can be paired with any other ERC-20 token by any user by calling the factory's createPair() (v2) or createPool() (v3) — no governance approval, no KYC, no curator whitelist required. Third-party guide confirms: 'no gatekeepers,' permissionless listing. This is standard AMM design (inherited from Uniswap v2/v3) but creates a manipulation surface: low-liquidity or malicious tokens can be listed, enabling price manipulation of thin pools, rug pulls via LP drain, or exploitation of automated routing. Yellow (permissionless is standard for this AMM type but represents a real listing/manipulation risk surface, especially on long-tail chains).
Sources #
- GitHubsushiswap/v2-core — permissionless factorysushiswap/v2-core: SushiV2Factory.createPair() — permissionless; anyone can callretrieved 2026-05-17
- Comprehensive Guide to Listing Tokens on SushiSwapMedium guide: SushiSwap token listing is permissionless; no gatekeepers; no governance approval required; ERC-20 standard only requirementretrieved 2026-05-17
Methodology #
Classify the governance threshold required to list a new market as: permissionless / low-threshold (team multisig) / high-threshold (DAO vote) / no new listings.
See the full factor methodology and distribution across all protocols →