Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By devrelaicom
Verify claims in Midnight projects by compiling and executing Compact test contracts, type-checking and E2E testing TypeScript SDK, checking ZKIR circuits via WASM inspector, validating witness implementations through cross-domain checks and source inspection, triggered by /verify command in multi-agent pipelines.
npx claudepluginhub devrelaicom/midnight-expert --plugin midnight-verifyFast source-first verification of Midnight claims. Uses source inspection as the primary method with optional background execution checks. Faster and cheaper than /midnight-verify:verify.
Verify claims about Midnight, Compact code, or SDK APIs. Accepts a claim, file path, code snippet, SDK question, or no arguments to be prompted.
Use this agent to verify Compact CLI tooling claims by running commands and observing output. Checks CLI availability, runs compact/compactc commands, captures stdout/stderr/exit codes, inspects filesystem changes, and interprets results. Dispatched by the /midnight-verify:verify command. Example 1: Claim "--skip-zk skips PLONK key generation" — compiles a minimal contract with and without --skip-zk, compares output directories (no keys/ directory when --skip-zk is used). Example 2: Claim "compact compile --language-version returns the current version" — runs the command, captures stdout, confirms it outputs a version string. Example 3: Claim "compactc rejects undeclared variables with exit code 1" — writes a contract with an undeclared variable, compiles with compactc, checks exit code is non-zero and stderr contains the expected error.
Use this agent to verify Compact claims by writing and executing test contracts. Translates a claim into a minimal Compact contract, compiles it with the Compact CLI, runs the compiled output with @midnight-ntwrk/compact-runtime, and reports what was observed. Dispatched by the /midnight-verify:verify command. Example 1: Claim "Tuples are 0-indexed" — writes a contract that returns tuple elements by index, compiles, runs, checks that t[0] is the first element. Example 2: Claim "persistentHash returns Bytes<32>" — writes a contract that calls persistentHash and returns the result, compiles, runs, checks the type and length of the return value. Example 3: Claim "disclose() is required for ledger writes" — writes a contract that does a ledger write without disclose(), confirms the compiler rejects it.
Use this agent to verify SDK behavioral claims by running E2E scripts against a local Midnight devnet. Checks devnet health first, then writes raw SDK scripts or testkit-js tests to exercise the full transaction pipeline. Dispatched by the /midnight-verify:verify command. Example 1: Claim "deployContract deploys and returns a contract address" — writes a raw SDK script that deploys a counter contract, checks the result has a contractAddress field with a valid hex string. Example 2: Claim "full deploy+call+observe lifecycle works" — uses testkit-js to set up environment, deploy, call increment, read state, verify counter changed. Example 3: Claim "findDeployedContract reconnects to an existing contract" — uses testkit-js for the multi-step flow: deploy, disconnect, reconnect via address, verify state is accessible. Example 4: Wallet SDK behavioral claim "WalletFacade.init syncs all three wallets" — only reached as a fallback when source investigation was Inconclusive. Checks Docker container health (midnight-node, midnight-indexer, proof-server), then writes a test script using the wallet SDK packages.
Use this agent to verify Compact or Midnight claims by inspecting the actual source code of the compiler, ledger, runtime, or related repositories. Uses octocode-mcp for quick lookups, falls back to local cloning for deep investigation. Dispatched by the /midnight-verify:verify command. Example 1: Claim "Compact exports 57 unique primitives" — searches LFDT-Minokawa/compact for midnight-natives.ss, counts the actual exports. Example 2: Claim "The Compact compiler is written in Scheme" — examines the LFDT-Minokawa/compact repository structure and source files. Example 3: Claim "MerkleTree is defined in the ledger crate" — searches midnightntwrk/midnight-ledger for the MerkleTree type definition. Example 4: Claim "ProtocolVersion is a branded bigint" — searches midnightntwrk/midnight-wallet for the ProtocolVersion type definition in packages/abstractions/src/. Uses verify-by-wallet-source for wallet-specific repo routing and evidence rules. Example 5: Claim "CoinCommitment = Hash<(CoinInfo, CoinPublicKey)>" — searches midnightntwrk/midnight-ledger coin-structure crate for the CoinCommitment type definition. Uses verify-by-ledger-source for Rust crate-level routing. Example 6: Claim "The Compact compiler is written in Scheme" — searches LFDT-Minokawa/compact for the compiler source code, examines file extensions and directory structure. Uses the general verify-by-source skill (tooling source claims route to existing repos).
Use this agent to verify SDK type claims or check user TypeScript files by running tsc --noEmit. Writes type assertion files for claims about the SDK API, or copies user .ts files into the SDK workspace. Dispatched by the /midnight-verify:verify command. Example 1: Claim "deployContract returns DeployedContract" — writes a .ts file with type-level assertions, runs tsc, confirms the return type matches. Example 2: Claim "CallTxFailedError extends TxFailedError" — writes an assignability check, runs tsc, confirms the inheritance hierarchy. Example 3: User file verification — copies src/deploy.ts to the workspace, runs tsc, reports any type errors with line numbers. Example 4: Claim "import { setNetworkId } from '@midnight-ntwrk/midnight-js-network-id'" works — writes a file with that import, runs tsc, confirms it resolves. Example 5: Wallet SDK claim "WalletFacade exports balanceFinalizedTransaction" — writes a .ts file importing from @midnight-ntwrk/wallet-sdk-facade, runs tsc, confirms the export exists. Uses the wallet-sdk-workspace (separate from the DApp SDK workspace).
Verification by running Compact CLI commands and observing output. Checks CLI availability, runs commands, captures stdout/stderr/exit code, inspects filesystem changes, and interprets results. Covers flag existence, flag behavior, output structure, error messages, exit codes, version info, and CLI-vs-compactc comparisons. Loaded by the cli-tester agent.
Verification by running E2E scripts against a local Midnight devnet. Writes SDK test scripts (raw or using testkit-js) that exercise the full transaction pipeline: deploy, call circuits, observe state. Checks devnet health before proceeding. Loaded by the sdk-tester agent. Loads the `midnight-tooling:devnet` skill for infrastructure management.
Verification by compilation and execution. Translates a Compact claim into a minimal test contract, compiles it with the Compact CLI, runs the compiled output with @midnight-ntwrk/compact-runtime, and interprets the result. Loaded by the contract-writer agent. Covers workspace setup (lazy init), contract writing, compilation, runner script creation, execution, and result interpretation. References midnight-tooling:compact-cli for compilation details.
Verification by source code inspection of the Midnight ledger Rust codebase. Searches and reads the actual Rust implementation to verify claims about transaction structure, token mechanics, cost model, on-chain VM, contract execution, and cryptographic primitives. Routes claims to specific crates within the 24-crate workspace. Uses octocode-mcp for quick lookups, falls back to local cloning for deep investigation. Loaded by the source-investigator agent when the claim domain is ledger/protocol.
Verification by source code inspection. Searches and reads the actual compiler, ledger, and runtime source code to verify structural or architectural claims about Compact and Midnight that cannot be tested via compilation. Uses octocode-mcp for quick lookups, falls back to local cloning for deep investigation. Loaded by the source-investigator agent.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Core knowledge for writing Midnight Compact smart contracts — contract structure, data types, ledger declarations, circuits, witnesses, and common patterns.
Formal verification for Sui Move smart contracts. Write specifications, run the prover, debug verification failures, and understand results.
Blue-team release-gate skill for smart contract systems. Classifies projects, reviews deployment and upgrade execution paths, inspects CI/CD and dependency trust boundaries, evaluates signer/admin operational security, and produces evidence-based release blockers, warnings, and release verdicts.
Specification-to-code compliance checker for blockchain audits with evidence-based alignment analysis
AI-powered smart contract security auditor with parallel hunt lanes, Devil's Advocate verification, static analysis (Slither, Aderyn), fuzz testing (Echidna, Medusa), symbolic execution (Halmos), Solodit intelligence, and interactive Map-Hunt-Attack methodology
Audits Solidity codebases for smart contract vulnerabilities using a four-phase workflow covering 36 vulnerability classes.
Compilable Compact smart contract examples — beginner contracts, reusable modules, token implementations, and full applications with witnesses and tests. All code at pragma language_version >= 0.22.
Audits and resolves Claude plugin dependencies — validates installed plugins against extends-plugin.json declarations, scans plugin files for undeclared dependencies, and resolves installation paths with fuzzy matching.
Conceptual foundations for understanding the Midnight Network: architecture, data models, privacy patterns, protocols, tokenomics, and zero-knowledge proofs
Fact-checking pipeline for Midnight content — extracts testable claims from any source (markdown, code, PDFs, URLs, GitHub repos), classifies them by domain (Compact, SDK, ZKIR, Witness), and verifies each claim using the midnight-verify framework. Produces structured JSON artifacts and human-readable reports.
Scaffold and develop Oclif CLIs for Midnight Compact smart contracts. Includes a complete CLI template with wallet management, contract deployment, devnet control, and an AI agent for ongoing development.
AI-powered development tools for the Midnight blockchain — a suite of Claude Code plugins that help you write, test, deploy, and review smart contracts in the Compact language.
midnightntwrk.expert — documentation, guides, and resources for Midnight developers.
curl -fsSL midnightntwrk.expert/me-install.sh | bash
Once installed, skills activate automatically based on what you're working on. Ask Claude to write a Compact contract, review existing code, set up a devnet, or explain a privacy pattern — the relevant skills engage on their own.
This repository contains 16 plugins organized by domain.
| Plugin | Description | |
|---|---|---|
![]() | compact-core | Compact language reference, patterns, privacy/disclosure, witnesses, tokens, circuit costs, debugging, and code review |
![]() | compact-examples | Compilable Compact examples from 8 repos — modules, tokens, applications, witnesses, and tests |
![]() | compact-cli-dev | Scaffold Oclif CLIs for Compact contracts with wallet management, deployment, and devnet control |
| Plugin | Description | |
|---|---|---|
![]() | midnight-dapp-dev | Vite + React 19 DApp scaffolding, SDK reference, DApp Connector API, provider assembly, state management |
| Plugin | Description | |
|---|---|---|
![]() | midnight-cq | Testing skills (contract simulator, DApp integration, DApp Connector, ledger, wallet) and code quality setup (Biome, Vitest, Playwright, CI) |
![]() | midnight-verify | Mechanical verification of Compact claims via compilation, execution, source inspection, type-checking, and ZKIR analysis |
![]() | midnight-fact-check | Fact-check documentation against the Midnight ecosystem — extract claims, classify by domain, verify, and report |
| Plugin | Description | |
|---|---|---|
![]() | midnight-tooling | Compact CLI management, local devnet lifecycle, proof server, release notes, troubleshooting |
![]() | midnight-wallet | Wallet CLI (MCP tools), test wallet setup, aliases, funding, dust registration |
![]() | midnight-mcp | MCP server skills for compilation, simulation, search, and health checks |
| Plugin | Description | |
|---|---|---|
![]() | core-concepts | Architecture, data models, privacy patterns, protocols, tokenomics, zero-knowledge proofs |
![]() | midnight-node | Node architecture, configuration, governance, operations, RPC API |
![]() | midnight-indexer | Indexer architecture, data model, GraphQL API |
![]() | proof-server | Proof server architecture, configuration, API, operations |
| Plugin | Description | |
|---|---|---|
![]() | midnight-expert | Ecosystem diagnostics — plugin health, MCP servers, external tools, cross-plugin references |
![]() | midnight-plugin-utils | Plugin infrastructure — dependency checking, scanning, root resolution |
Write a contract:
"Create a Compact contract for a simple voting system"
Review a contract:
/compact-core:review-compact contracts/MyToken.compact