A successful deployment requires that smart contracts or code for the protocol have been deployed to the specified blockchain mainnet (not testnet), the deployment has been officially announced or confirmed by the protocol team, core functionality of the protocol is operational on the blockchain, users can interact with the protocol through at least one interface (web app, CLI, or direct contract interaction), and the deployment is publicly accessible (not restricted to whitelisted addresses only). Full protocol launch with all features operational counts as deployment, as does partial deployment with core features operational (e.g., beta or v1 launch), migration of existing protocol from another blockchain, deployment of a new version or fork of the protocol, multi-chain expansion where the specified blockchain is added as a supported network, or deployment through official bridges or cross-chain infrastructure. Testnet deployments regardless of functionality do not count as deployment, nor do announcements of future deployment without actual smart contract deployment, deployment of placeholder or proxy contracts without functionality, private or permissioned deployments accessible only to team or investors, deployment of auxiliary contracts (e.g., governance tokens) without core protocol functionality, third-party forks or clones not endorsed by the protocol team, wrapped or synthetic versions created by other parties without protocol endorsement, deployment on a different blockchain than specified, or deployment on Layer 2s when the specification is for Layer 1. Resolution will be based on verifiable on-chain records, official protocol communications, blockchain explorers, and reputable crypto news sources.