crops

Reviews Ethereum dApp architectures for censorship resistance, openness, privacy, and security risks.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/m-faran/genie-markets --skill crops-m-faran
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crops
Source: https://github.com/m-faran/genie-markets/tree/main/.agent/skills/ethskills/crops
Command: npx skills add https://github.com/m-faran/genie-markets --skill crops-m-faran

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about crops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an Ethereum dApp for centralization risks?▼

Run a CROPS review covering four pillars: who can block users, whether the whole stack is open and freely licensed, what user data leaks, and who controls funds and upgrades. The output names each risk, its mitigation, and the user's escape route.

What does CROPS mean in Ethereum development?▼

CROPS is the Ethereum Foundation's shorthand for Censorship Resistance, Open Source and Free, Privacy, and Security. It defines the properties Ethereum applications must preserve, and this Skill turns those values into concrete architecture checks.

Does contract verification on Etherscan make a dApp open source?▼

No. Etherscan verification ties bytecode to source for that contract only. Open requires the whole stack to be public, and Free requires an OSI-approved license, not merely source-available terms like BUSL or SSPL.

How do I check if my dApp passes the walkaway test?▼

Ask whether users can still access funds and exit if the team, vendor, host, or oracle disappears. Check custody arrangements, admin keys, recovery paths, and whether critical flows depend on a single vendor's liveness.

What are the limits of a CROPS architecture review?▼

CROPS covers trust assumptions, admin powers, censorship paths, privacy leakage, and user exit, but not deep code-level vulnerabilities. For Solidity vulnerability patterns and pre-deploy checks, use a dedicated smart contract security or audit review.