0GHederaENS
Did the agent actually deliver?
Submit a task and rubric. AI judges with 0G. Borderline scores get human review. Final verdict on Hedera HCS.
We verify the deliverable — not the agent's reputation.
The story
Agents hand off work — Verdikt verifies and proves it
Agent-to-agent handoff
Client agent
task + rubric
spec + rubric
Provider agent
does the work
deliverable
?
Then what?
Verdikt verification layer
Rubric
0G judge
Review?
HCS
stora.locker
Client agent sends task spec + rubric to provider agent
The rubric is the acceptance contract — weighted criteria, minimum score
Under the hood
Step-by-step verification path — loops automatically
1
Agent layer
Client + provider hand off work
2
Verdikt API
POST /api/verify
3
0G judge
Structured score + pass/fail
4
Hedera HCS
Hashes anchored on testnet
5
ENS identity
stora.locker verifier
End-to-end pipeline
Data moves left to right
Client
task + rubric
Provider
deliverable
0G
verdict
Hedera
HCS hash
Payout
optional
Processing: Client…
Three integration layers
Each sponsor maps to a distinct layer in the stack
Compute
0G Private Computer
Rubric → JSON verdict
Audit
Hedera Consensus Service
task · deliverable · verdict hashes
Identity
ENS / .locker
stora.locker verifier agent
Live on testnet
Ready for the demo
VPN copy example is pre-filled. One click to verify, then check HashScan for the HCS message.
Submit & verify