ZK Miner

Introduction

The ZK Miner application is based off of the popular Mines Gambling Game. In this game, you are presented with a grid of tiles, each of which may or may not contain a mine. The goal is to uncover as much tiles as possible, without uncovering any tiles that do contain a mine. Each time you uncover a tile, you are presented with a reward.

The ZK Miner application is a decentralized version of the game, where the game logic is executed and proven in a trustless manner using a SP1. The outcome of the game is committed too and verified on Aligned, bringing the verification costs down to a fraction of the cost for verification on the L1. This proof can then be pulled from a L1 Escrow contract, and used to settle the game.

Architecture

• Contracts: Contains the Escrow contract and the deploy script for it.
• Mine: Contains the SP1 code for the Mines game along with the compiled ELF file for it.
• src: Contains the Rust code for the ZK Miner application backend and testing.

Requirements

• Rust
• SP1 toolchain: used to compile the SP1 code to an ELF file.

Execution

1. Clone the repository and navigate to the root directory.
2. Run cargo run --release to start the application.

Testing

1. Set the RPC_URL and PRIVATE_KEY environment variables in the .env file. The RPC_URL should point to a Holesky endpoint, and the PRIVATE_KEY should be the private key of the account that will be used to sign transactions during testing.
2. Run cargo test -r test_sp1_end_to_end to run the end to end test.

Team

• Dhruv Malik: CTO of extralabs.xyz / backend dev and web3 integration.
• Pol Montero: Full Stack Developer from Palma, Spain, transitioning into blockchain development. Co-founder and lead developer of Criptodigital.cat.
• Anukkrit: Founding team Karnot.
• Greg: Core developer at Kakarot ZK-EVM.

Challenges

• Stack overflow: When trying to proof using the SP1 SDK, we encountered a stack overflow error. This was due to the fact that we were compiling without the --release flag. This flag is necessary to optimize the code and prevent the stack overflow error.

• Ether-rs Encoding error: When trying to call the contract and pass the proof, we encountered an encoding error using Ethers-rs. This was fixed when switching to the alloy crate.