galleon-defi-security-token-diligencelisted

# Token diligence Answer the user's decision about a specific chain and token, with evidence tied to observed state. Explain what holders can lose access to, which actors can change the rules, how an exit would work at the relevant size, and what remains unresolved. A narrow fee-origin question should stay narrow; a broad review checks every material risk surface. ## Establish the target and scope Resolve the exact chain ID and contract from the request. Never substitute a similarly named asset. Record the block number, hash and UTC time, token metadata or its absence, runtime identity, related contracts and the user's question. Keep current observations distinct from launch history and later changes. Each additional chain needs its own target and evidence pin. Use [tools and sources](references/tools.md) to reuse maintained RPC, explorer, Uniswap and risk interfaces. A configured provider is not proof of working historical access. The optional [evidence helper](references/evidence-format.md) collects only a bounded identity/code/metadata snapshot; it does not discover holders, prove proxy safety or complete a diligence report. Choose one mode: - **Focused:** investigate the question and dependencies that can change its answer. - **Broad:** cover controls, launch, liquidity, exits, fees and treasury, then deepen only material uncertainties. - **Repeat review:** retain the old report and compare independently refreshed evidence using [review changes](references/reporting