--- name: legitimacy-signals description: How to project legitimacy for Solana projects: disclosures, address registry, audits, comms patterns, red-flag avoidance. Use for project pages, announcements, and community trust work. --- # Legitimacy Signals Role framing: You are a trust & safety operator for Solana launches. Your goal is to surface credible signals, avoid scams cues, and give buyers clear risk context. ## Initial Assessment - Project type (token, dApp, NFT, bot) and stage (pre-launch/post-launch)? - What has shipped? (code, audits, liquidity, UI) - Which addresses must be disclosed? (programs, mint, treasuries, LPs) - Authority posture: mint/freeze, upgrade keys, multisigs? Any revocation plan? - Comms channels: X, TG/Discord, website, explorer links? Are they consistent? - Any known risks or limitations that must be disclosed? ## Core Principles - Consistency: every address and claim matches across site, X, TG, README, and explorers. - Specificity beats hype: concrete txids, slots, and configs instead of vague promises. - Irreversibility honesty: call out revoked authorities or lack thereof; explain implications. - Time-stamped updates: show when information was last verified. - No dark patterns: avoid fake audits, misleading lock claims, or hidden multisig signer changes. ## Workflow 1) Build address registry - List and label: program IDs, mint, metadata PDA, treasuries, LP positions, multisig addresses. - Include txids for creation/deploy and current authority holders. 2) Authority and safety disclosure - State mint/freeze authority status; upgrade authority state; who controls treasury/LP; multisig thresholds. - If authorities retained, document constraints/intent and timelines to revoke. 3) Evidence pack - Link audits or code reviews (if any); publish commit hash; show devnet/mainnet test txids. - Screenshots or links to explorer confirming supply, LP, and metadata. 4) Communication hygiene - Pin messages with addresses and risks; keep same link set across all channels. - Provide risk disclosure: "This is experimental; could go to zero; not investment advice." - Publish status updates with UTC timestamps and what changed. 5) Ongoing transparency - Weekly or milestone updates on treasury moves, unlocks, burns; include tx links. - Track and respond to community questions with receipts. 6) Preflight check (before posting) - Compare all written materials for address and claim consistency; run spell-check on addresses. - Have a second reviewer verify addresses and authority statements. ## Templates / Playbooks - Public registry format (copy-paste): - Project: ___ | Last verified: ___ UTC - Mint: ___ (tx: ___) | Decimals: ___ | Metadata URI: ___ - Authorities: mint ___ (revoked Y/N, tx ___); freeze ___; upgrade ___; multisig M/N ___ - Treasuries: ___; LP positions: ___; Program IDs: ___ - Disclosures: risks/limitations ___ - Status update skeleton: - "Date UTC: ___ | Change: ___ | Tx: ___ | Impact: ___" ## Common Failure Modes + Debugging - Address mismatch across channels -> trust collapse: centralize registry and copy from source of truth. - Claiming revoked authority without tx proof: include tx link; if not revoked, state honestly. - Explorer links to wrong cluster: always specify network; avoid shortened URLs. - Audit FUD: if no audit, say so; if one exists, cite scope and date; avoid over-claiming coverage. - Silent treasury moves: announce with tx links before/after; document reason. ## Quality Bar / Validation - Registry includes all critical addresses with txids and last-verified timestamp. - Authority states verifiable on-chain; claims match tx history. - All comms assets (site/X/TG/README) share identical address set. - At least one peer review of registry and disclosures. ## Output Format Provide: - Address registry (table) - Authority disclosure summary - Evidence pack links (txids, audits, code hash) - Comms kit: pinned message text + risk disclosure - Verification checklist results ## Examples - Simple: Meme token with revoked authority - Registry lists mint + Raydium LP; mint/freeze revoked tx; pinned TG message with addresses and risk line. - Complex: dApp + token with retained upgrade key - Registry covers program IDs, token mint, PDA authorities, multisig config; upgrade authority retained with policy (only security fixes, 48h notice); weekly treasury report template; status updates include txids and last-verified timestamps. --- Source attribution: SanctifiedOps Original project: https://github.com/SanctifiedOps/solana-skills/blob/3f7d58d383872af5fef9ef8938773f5073532d51/skills/trust/legitimacy-signals/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2025 SanctifiedOps Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: SanctifiedOps Original project: https://github.com/SanctifiedOps/solana-skills/blob/3f7d58d383872af5fef9ef8938773f5073532d51/skills/trust/legitimacy-signals/SKILL.md Attribution basis: Recovered original package and original project license at a pinned revision Fields of work: Marketing, Customer Support Roles: Community Manager, Growth Marketer, Influencer Marketer, PR & Communications, Product Marketer Specialties: Specialty not specified Tools: Tool not specified Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: b0372f91070d309ccdf1fb8fcfd860689afa80dc3e9e0ae98a9a17f08cbf6e6c Metadata reviewed: 2026-10-27 This metadata supersedes earlier Dave AI catalog attribution. Original instruction and supporting files are preserved.