A valid proof only means "this satisfied the circuit's constraints" — not "the wallet was genuinely verified." To trust the WHAT behind the proof, audit the circuit source and confirm the verification key hash matches.
Verification key hash (this is the circuit's identity):
21428822038759506179445837352223957273759843165645580082852926175852620820809
Server attestation public key (what signs every Minalia verification):
B62qmjxrag7YqmRmUQcT562iU1cB8zascC55eozo4Mjj5G9x7Mcwa9B
o1js version (pinned):
2.14.0
⬡ How to audit the circuit:
2. Check what circuit is running now at
/health ↗
— returns the commit SHA, VK hash, and server public key the live server reports
3. Clone the repo at that commit SHA and compile the circuit yourself:
git clone https://github.com/zkokio/minalia-proving-server
cd minalia-proving-server
npm install
node -e "import('o1js').then(async o => {
// paste the MinalianVerification ZkProgram block from server.js
const { verificationKey } = await MinalianVerification.compile();
console.log('VK hash:', verificationKey.hash.toString());
})"
4. Confirm your locally-compiled VK hash matches the one above. If all three match (source → live server → proof.json), the circuit identity is cryptographically locked — no way for Minalia to cheat without publishing a different circuit.