audit

Audit ZKP2P smart contracts with differential invariant analysis against canonical main baselines.

24|14|Updated Dec 2, 2024
One-click install
npx skills add https://github.com/zkp2p/zkp2p-contracts --skill audit-zkp2p
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/zkp2p/zkp2p-contracts/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/zkp2p/zkp2p-contracts --skill audit-zkp2p

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of auditing evolving smart contract systems by providing a structured, invariant-based framework for security reviews, differential analysis, and V2-to-V3 parity verification.

Core Features & Use Cases

  • Differential Auditing: Compare current branch changes against the canonical main baseline to identify regressions or new vulnerabilities.
  • Invariant Verification: Systematically check critical security boundaries like authorization, settlement, and replay protection.
  • V3 Parity Checks: Ensure that new V3 lifecycle implementations maintain the required security guarantees and behavioral consistency with V2.

Quick Start

Use the audit skill to perform a full security review of the current branch against the canonical main repository.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I perform a differential security audit on Solidity smart contracts?

To perform a differential smart contract audit, compare your current branch changes against a canonical main baseline to identify regressions or new vulnerabilities. This process ensures evolving contract updates do not compromise existing security boundaries.

What is invariant testing for smart contracts and when do I need it?

Invariant testing for smart contracts systematically verifies critical security boundaries like authorization, settlement, and replay protection. You need it when reviewing evolving contract systems to ensure core protocol guarantees remain intact during updates.

How do I verify V2 to V3 smart contract lifecycle parity?

To verify V2 to V3 smart contract lifecycle parity, execute V3 lifecycle parity checks against canonical baselines. This ensures new V3 implementations maintain required security guarantees and behavioral consistency with previous V2 versions.

Do I need Foundry and Git to run invariant analysis on Solidity contracts?

Yes, you need Git-based repository access and Foundry-compatible testing environments to run invariant analysis. These dependencies are required to validate authorization, settlement, and reentrancy boundaries during comprehensive security reviews.

Can I use this audit framework for pull request validation on ZKP2P smart contracts?

Yes, you can use the audit framework for pull request validation on ZKP2P smart contracts. It performs differential analysis against the canonical main repository to detect regressions and verify invariant boundaries before merging.