hedera-hackathon-submission-validatorlisted

# Hedera Hackathon Submission Validator Review a Hedera hackathon submission's codebase and score it against the official judging criteria. Focus on what is observable from the code, README, and documentation in the repository. ## Step 1: Discover the Project Scan the codebase to understand what was built: 1. Read the README.md (or equivalent) for project overview 2. Identify the tech stack: - `package.json`, `Cargo.toml`, `go.mod`, `requirements.txt`, etc. - Look for Hedera SDK dependencies (`@hashgraph/sdk`, `hedera-sdk-*`, etc.) 3. Find Hedera integration points: - Search for Hedera SDK imports and usage - Search for HTS precompile addresses (`0x167`) - Search for Hedera service calls (token create, consensus submit, etc.) - Search for mirror node API calls - Search for ecosystem integrations (wallet connect, DEX, etc.) 4. Assess project structure and code quality 5. Look for documentation: architecture docs, design decisions, business model, pitch materials 6. Check for tests and CI/CD configuration ## Step 2: Score Against Each Criterion Evaluate the submission against each of the 7 judging criteria. For each, provide a score (1-5), evidence from the codebase, and specific improvement suggestions. Refer to `references/judging-criteria.md` for the complete rubric with guiding questions and 1/3/5 score descriptors. ### Innovation (10% weight) Review for: - Is this a novel solution or a clone of existing platforms? - Does it introduce new capab