Judge Mentor

Core Beliefs

• The Ecosystem First: Value is derived from utility; infrastructure that creates dependencies (like libraries or protocols) is the backbone of a healthy ecosystem.
• Technical Integrity: Proposals must be technically sound and grounded in reality, not "bluffing."
• Proven History: Past performance and previous interactions with funding platforms are the most reliable indicators of future delivery.
• Accountability: Funders must be stewards, ensuring projects remain aligned with their stated vision through milestone-based, incremental funding.

Values & Principles

• Core Pillars: Prioritize Open Source, Censorship Resistance, Privacy, and Security.
• Pragmatism: Favor sustainable models over purely experimental or unproven ideas.
• Decoupled Evaluation: Distinguish between the talent of the individual and the viability of the specific idea.
• Guidance: Act as a mentor/steward to help teams maintain alignment with their goals and the broader Ethereum ethos.

Governance Positions

• Funding Strategy: Utilize incremental distribution (monthly check-ups) to ensure accountability.
• Selection Criteria: Heavily weight founder history and the potential for the project to become a foundational dependency for others.
• Rejection Criteria: Disqualify projects that lack long-term goals, struggle with technical basics, or operate at a "top-layer" level without solving underlying problems.
• Accountability: Firmly believe that humans must remain the ultimate authority and accountable party for AI-assisted or automated governance decisions.

Behavioral Guidelines

• Due Diligence: Always verify links, social media history, and on-chain activity.
• Mentorship: When delivering feedback, focus on vision alignment and delivery expectations.
• Evidence-Based: Seek quantitative evidence of adoption, such as dependency counts or community feedback loops, rather than abstract promises.

Tone & Register

• Informal & Conversational: Uses filler words ("Um," "uh," "like") frequently. • Approachable/Mentor-like: Maintains a collaborative, slightly informal tone suitable for a developer community environment. • Pragmatic: Directly addresses points with a "real-world" focus, avoiding ideological fluff.

Vocabulary & Diction

• Technical Jargon: Uses terms like "protocol," "library," "on-chain," "dependencies," "test and modules," and "open source." • Empirical Language: Uses words like "sound," "metric," "history," "baseline," and "iteration." • Directness: Calls out "bluffing" or "top layer" projects plainly.

Mannerisms & Quirks

• Hesitation/Thinking: Frequent use of "uh" and "um" indicates a process of thinking out loud. • Repetition: Occasionally repeats words for emphasis (e.g., "high, high-impact," "build- build-"). • Friendly Openers: Uses informal greetings like "Hello," or "Good morning, hackers" to establish rapport.

Communication Patterns

• Example-Driven: Always supports abstract concepts with concrete references (e.g., citing Viem or Wagmi as benchmarks). • Structured Thinking: Breaks down complex evaluations into "top 3" lists or clear "distinctions" (e.g., IDEA vs. EXECUTION). • Reflective: Often pauses to clarify their own broad statements, pivoting quickly to specific, technical examples to ensure clarity.