skills.rest
devrelaicom
devrelaicomOFFICIAL
Explore all skills by this author →
GitHub

midnight-verify:verify-by-zkir-checker

Verify Compact contracts and ZKIR claims with the PLONK checker.

37|9|Updated Feb 25, 2026
Search Tags:#verification#blockchain#compact#plonk#zkp#zkir
One-click install
npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-verify-verify-by-zkir-checker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: midnight-verify:verify-by-zkir-checker
Source: https://github.com/devrelaicom/midnight-expert/tree/main/plugins/midnight-verify/skills/verify-by-zkir-checker
Command: npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-verify-verify-by-zkir-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying Compact contracts and ZKIR claims requires running the entire zero-knowledge proof pipeline with real PLONK verification keys to ensure the authenticity of proofs.

Core Features & Use Cases

  • End-to-end verification: compile contracts without --skip-zk, run the JS runtime, serialize proof data, and verify with the PLONK checker.
  • Supports both contract mode and claim mode to test actual contracts or minimal contracts asserting a claim.
  • Provides a reproducible workflow for testing, debugging, and auditing ZK circuits in the Midnight network.

Quick Start

Run the verification workflow against a prepared workspace and the target .compact or claim scenario.

Frequently Asked Questions about midnight-verify:verify-by-zkir-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Compact contracts using real PLONK proofs?▼

To verify Compact contracts using real PLONK proofs, compile without the --skip-zk flag, run the JS runtime to serialize proof data, and invoke the zkir-v2 PLONK checker against your compiled artifacts.

What is the difference between contract mode and claim mode in ZKIR verification?▼

Contract mode verifies actual compiled Compact contracts, while claim mode tests minimal contracts asserting a specific claim, both requiring a workspace and the zkir-v2 verifier to execute end-to-end PLONK verification.

Do I need compiled artifacts to run ZKIR verification?▼

Yes, you need compiled artifacts and a prepared workspace to run ZKIR verification, as the PLONK checker requires serialized proof data generated from compiling contracts without the --skip-zk flag.

Why does compiling with --skip-zk break ZKIR PLONK verification?▼

Compiling with --skip-zk bypasses the generation of zero-knowledge proof data, meaning the PLONK checker lacks the serialized verification keys required to validate the authenticity of ZK circuits.

What's the best way to debug ZK circuits in the Midnight network?▼

The best way to debug Midnight ZK circuits is using a reproducible verification workflow that compiles contracts, executes the JS runtime, runs negative testing, and generates reports via the zkir-v2 PLONK checker.

Related Skills

Explore More Software Engineering Skills→
devrelaicomdevrelaicom
37

midnight-verify:zkir-regression

Run regression verification across curated ZKIR claims for Midnight Compact toolchains.

Official
Advanced
kunallimayekunallimaye

crypto-zkp

Guide ZKP proof system selection and circuit design with security auditing.

Community
Advanced
devrelaicomdevrelaicom
37

midnight-verify:verify-by-execution

Compile and execute Compact test contracts to verify runtime behavior.

Official
Advanced
devrelaicomdevrelaicom
37

core-concepts:zero-knowledge

Explain zero-knowledge proofs and Midnight's PLONK-based transaction validation.

Official
Intermediate