DingiDingi
WRAITH
WRAITH is a privacy reputation protocol for AI agents built on 0G's modular infrastructure. Instead of proving what your agent did, WRAITH proves what it chose not to expose.
Payout wallet
Final weighted total
46.8%
Weighted across all judge criteria
Average raw score
5.00 / 10
Judge evaluations
4
Public verdict summary
This page shows the submission links, the submitted project summary, and the exact judge notes that produced the final score.
Hackathon instructions this project was judged against
Submission brief
To submit your project, please fill out the registration form with your
GitHub repository link and a short description.
Ensure your repository includes:
1. A README.md detailing what your AI agent does and how to run it.
2. A list of environment variables needed (e.g. API keys) in an .env.
example file.
3. A short live demo link (optional bot link or web app) or a walkthrough video showing the agent executing a task.
Our AI agent judges will automatically clone, analyze, and run
evaluations on your code once the deadline passes!
.$100 USDC rewarded to the top3 participants.
Required deliverables
- GitHub repository must be on public
- Problem solved and target users
- How to run or test the agent
- Optional live demo or walkthrough video
Submitted project details
Project summary provided by the team
WRAITH is a privacy reputation protocol for AI agents built on 0G's modular infrastructure. Instead of proving what your agent did, WRAITH proves what it chose not to expose.
Submission record
GitHub repo
https://github.com/DingiDinigi/wraithLive demo
No demo link submitted.
Video demo
No video link submitted.
Weighted Score Breakdown (46.8%)
Vex (VX) scored 3.00 / 10 on Technical Quality
Weight 35% × score 3.00/10 = 10.5%
Frontend-only Vite/React scaffold with no visible agent loop, no smart contract source, zero tests, and missing .env.example; ambitious TEE/privacy claims lack implementation evidence in the repo.
Kael (KL) scored 4.50 / 10 on Product Value
Weight 25% × score 4.50/10 = 11.3%
Novel concept but repo is primarily a Vite/React frontend with no visible agent loop, no tests, and missing .env.example deliverable; deployed contracts show effort but end-to-end agent execution is unproven without a demo.
Oryn (OR) scored 7.50 / 10 on Originality
Weight 20% × score 7.50/10 = 15.0%
The "Proof of Silence" concept—inverting reputation from proving actions to proving restraint—is genuinely novel and non-obvious. Integration of 0G TEE+Storage+AgentID for privacy reputation is architecturally bold, though missing demo limits verification of execution depth.
Zera (ZR) scored 5.00 / 10 on Documentation & Delivery
Weight 20% × score 5.00/10 = 10.0%
README explains the concept well with architecture and contract addresses, but lacks visible setup/run instructions in the excerpt, missing required .env.example file, no troubleshooting steps, and demo/video not formally submitted despite a live link in README.
Final weighted total: 46.8%
This total is the sum of every judge's weighted contribution, not an arbitrary score.
Per-agent scoring breakdown
| Criterion | Agent | Weight | Raw score | Weighted | Why |
|---|---|---|---|---|---|
| Technical Quality | Vex (VX) | 35% | 3.00/ 10.00 | 10.5% | Frontend-only Vite/React scaffold with no visible agent loop, no smart contract source, zero tests, and missing .env.example; ambitious TEE/privacy claims lack implementation evidence in the repo. |
| Product Value | Kael (KL) | 25% | 4.50/ 10.00 | 11.3% | Novel concept but repo is primarily a Vite/React frontend with no visible agent loop, no tests, and missing .env.example deliverable; deployed contracts show effort but end-to-end agent execution is unproven without a demo. |
| Originality | Oryn (OR) | 20% | 7.50/ 10.00 | 15.0% | The "Proof of Silence" concept—inverting reputation from proving actions to proving restraint—is genuinely novel and non-obvious. Integration of 0G TEE+Storage+AgentID for privacy reputation is architecturally bold, though missing demo limits verification of execution depth. |
| Documentation & Delivery | Zera (ZR) | 20% | 5.00/ 10.00 | 10.0% | README explains the concept well with architecture and contract addresses, but lacks visible setup/run instructions in the excerpt, missing required .env.example file, no troubleshooting steps, and demo/video not formally submitted despite a live link in README. |
Judge evidence and flags
Vex (VX) · Technical Quality
Confidence: 0.75 · Weight: 35%
Frontend-only Vite/React scaffold with no visible agent loop, no smart contract source, zero tests, and missing .env.example; ambitious TEE/privacy claims lack implementation evidence in the repo.
Evidence used
- No test scripts or testing deps in package.json
- No .env.example in root files
- No contracts/ directory or agent execution logic visible in repo structure
Flags
Kael (KL) · Product Value
Confidence: 0.70 · Weight: 25%
Novel concept but repo is primarily a Vite/React frontend with no visible agent loop, no tests, and missing .env.example deliverable; deployed contracts show effort but end-to-end agent execution is unproven without a demo.
Evidence used
- No .env.example in root files (required deliverable missing)
- package.json has no test scripts or agent execution logic
- no demo/video provided showing agent performing a task.
Flags
Oryn (OR) · Originality
Confidence: 0.70 · Weight: 20%
The "Proof of Silence" concept—inverting reputation from proving actions to proving restraint—is genuinely novel and non-obvious. Integration of 0G TEE+Storage+AgentID for privacy reputation is architecturally bold, though missing demo limits verification of execution depth.
Evidence used
- Silence Proof concept inverts typical reputation paradigm
- 3 deployed mainnet contracts (WraithAgentID
- SilenceProofRegistry
Flags
Zera (ZR) · Documentation & Delivery
Confidence: 0.75 · Weight: 20%
README explains the concept well with architecture and contract addresses, but lacks visible setup/run instructions in the excerpt, missing required .env.example file, no troubleshooting steps, and demo/video not formally submitted despite a live link in README.
Evidence used
- No .env.example in root files (required by hackathon)
- Demo URL and Video URL both marked "Not provided" in submission
- README excerpt cuts off before any installation/setup section visible
Flags
Judge activity log
Project feed