[Discussion] OxiZ: A Pure Rust SMT Solver infrastructure for Polkadot/Substrate

kitasan
7hrs 30mins ago
0 Comments

Introduction: Who am I?

I am the maintainer of 362 Rust crates on crates.io, effectively managing about 0.15% of the entire Rust ecosystem single-handedly.
I operate under the name COOLJAPAN OU (Team KitaSan).

I am not here to talk about "plans." I am here to offer existing infrastructure that I have already built.

The Problem: Rust Chains need Rust Tools

Polkadot and Substrate are built on Rust. However, the current standard for formal verification (SMT solvers like Z3 or CVC4) relies heavily on C++.

This creates a critical bottleneck for the Substrate ecosystem:

  1. No Wasm Support: C++ solvers cannot easily run in no_std environments or inside the browser/blockchain runtime.
  2. Complex FFI: Integrating Z3 into a pure Rust project requires messy Foreign Function Interfaces, breaking the safety guarantees of Rust.

We are building the future of Web3 on Rust, so why are we still relying on legacy C++ tools for verification?

The Solution: OxiZ (Pure Rust SMT Solver)

I have developed OxiZ, a high-performance SMT solver written entirely in Pure Rust.
It is already live (v0.1.3) and available on crates.io: https://crates.io/crates/oxiz

https://github.com/cool-japan/oxiz

OxiZ allows us to:

  • Verify logic directly in Wasm (Browser & On-chain).
  • Integrate verification tools into ink! smart contracts without external dependencies.
  • Ensure mathematical correctness of the Polkadot infrastructure using native Rust code.

The Proposal

I originally applied for a W3F Grant, but since the program is currently closed, I am bringing this proposal directly to the Treasury and the community.

I am requesting funding to take OxiZ from "General Rust" to "Substrate Native".

Goal: Make OxiZ fully compatible with Substrate & ink!

  • Milestone 1: Implement BitVector Theory (QF_BV) (Essential for EVM/Wasm contract verification).
  • Milestone 2: no_std & Wasm Optimization (Make it run inside the browser and runtime).
  • Milestone 3: Proof Generation (Trustless verification).

Estimated Cost: ~$30,000 (Small Spender Track)
Timeline: 3 Months

Why Vote "Aye"?

  • Sovereignty: Polkadot deserves its own verification stack, independent of Microsoft's Z3.
  • Security: Formal verification is the only way to prevent smart contract hacks mathematically.
  • Proven Track Record: I have already shipped 350+ crates. I deliver code, not just promises.

I welcome any feedback from the community before I move this to a formal Referendum.
Let's make verification accessible to every Substrate developer.

Edited
Up
Comments