Block Hacker
Hack Blocks, Hide Nothing, Prove Everything
Created on 25th September 2025
•
Block Hacker
Hack Blocks, Hide Nothing, Prove Everything
The problem Block Hacker solves
Block Hacker Transforms "trust the game developer" into "trust the math" - players can prove they earned rewards through skill, not cheating, while maintaining smooth gameplay experience.
It solves these key problems:
Gaming Industry Issues:
Score manipulation & cheating - Players can fake high scores since game state is client-side
Pay-to-win skepticism - Players can't verify if rewards are actually earned through skill
Centralized game economies - Players don't truly own their achievements or items
Blockchain Gaming Problems:
Transaction spam - Every game action requiring wallet signatures kills UX
Proof of skill - No way to cryptographically prove you earned rewards legitimately
Trust in game mechanics - Players must trust developers about drop rates, difficulty, etc.
Technical Solution:
Zero-knowledge proofs verify you played legitimately without revealing strategy
Token delegation eliminates constant wallet popups during gameplay
Challenges I ran into
Technical Integration Challenges
- Multi-system complexity: Coordinating between RISC0 proof generation, zkVerify aggregation, smart contracts, and frontend
- Data flow mismatches: Getting proof data to flow correctly from Rust backend through NextJS API to smart contracts
- Framework compatibility: NextJS App Router vs Pages Router confusion,
OpenZeppelin version issues
- Development Workflow Issues
- Debugging across languages: Troubleshooting issues spanning Rust, Solidity, and TypeScript
- Type system conflicts: Rust serialization traits, TypeScript interfaces, and Solidity ABI compatibility
- State management: Wallet connection gating, proof result handling, and UI state coordination
Architecture Evolution
- Approach pivoting: Started with simple backend minting, evolved to full zkVerify contract integration
- Security vs complexity tradeoffs: Balancing gasless UX with decentralized verification
- Documentation gaps: Limited examples for zkVerify integration patterns
Hackathon-Specific Pressures
- Time constraints: Building complex cryptographic integrations under deadline pressure
- Learning curve: Implementing zkVerify aggregation without extensive prior experience
- Testing limitations: Difficulty validating full proof-to-token flow on testnet
Tracks Applied (2)
Combined Bounty (zkVerify + Horizen)
Horizen
Technologies used
Cheer Project
Cheering for a project means supporting a project you like with as little as 0.0025 ETH. Right now, you can Cheer using ETH on Arbitrum, Optimism and Base.