What problem does it solve? Ethereum dApps can compile, pass tests, and demo cleanly while still handing users to censorable frontends, closed indexers, custodial wallets, or admin keys with total control. This Skill turns the Ethereum Foundation's CROPS values (Censorship Resistance, Open Source and Free, Privacy, Security) into concrete architecture checks so trust assumptions are caught before users are harmed. ## Core Features & Use Cases - Four-pillar architecture review: Systematically checks who can block users, whether the whole stack is open and freely licensed, what data leaks to observers, and who controls funds, upgrades, and exit paths. - Structured review output: Produces a standardized CROPS Review naming risks, mitigations, user escape routes, and accepted compromises per pillar, plus a short-form comparison for weighing architecture options. - Failure-mode detection: Flags common patterns like censorable frontends, invisible RPC dependencies, prompt-only agent spending limits, hidden custody in embedded wallets, and unexamined L2 sequencer trust. - Use Case: Before finalizing a new prediction-market dApp, run the review to discover that the frontend is hosted by a single provider, the admin key can pause all payouts, and the indexer has no self-host path, then get concrete mitigations for each. ## Quick Start Review my Ethereum dApp architecture with the CROPS framework and list the trust assumptions, admin powers, and user exit risks.