ship-contracts

Coordinates multi-stage deployment and activation of ZKP2P smart contracts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill manages the complex, high-stakes process of deploying smart contracts by enforcing strict, boundary-based authorization and validation, preventing accidental production deployments or unauthorized state changes.

Core Features & Use Cases

  • Boundary-Based Deployment: Separates source preparation, staging activation, and production activation into distinct, independently approved phases.
  • Safety Guardrails: Prevents automated production releases and ensures that deployment scripts are verified against current network state and governance policies.
  • Use Case: When preparing a new version of the ZKP2P Orchestrator, use this Skill to systematically move from source preparation to staging activation, ensuring all deployment artifacts and governance requirements are met before any production-level action is considered.

Quick Start

Use the ship-contracts skill to prepare the deployment plan for the latest source commit on the staging network.

Frequently Asked Questions about ship-contracts

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

FAQPage Schema
How do I manage multi-stage smart contract deployment across staging and production?

Multi-stage smart contract deployment is managed by separating source preparation, staging activation, and production activation into distinct phases. Each phase requires explicit validation of deployment artifacts, transaction hashes, and on-chain state before advancing.

How can I prevent accidental production releases when deploying smart contracts?

To prevent accidental production releases during smart contract deployment, strict safety guardrails enforce boundary-based authorization. Automated production releases are blocked unless deployment scripts are verified against current network state and governance policies.

What is boundary-based deployment for blockchain governance?

Boundary-based deployment for blockchain governance is a process that isolates source preparation, staging activation, and production activation into independently approved phases. This separation ensures all deployment artifacts meet governance requirements before any network-scoped action proceeds.

Do I need explicit transaction hash validation for smart contract lifecycle management?

Yes, explicit transaction hash validation is required for smart contract lifecycle management. Verifying transaction hashes and on-chain state ensures secure, authorized contract activation and prevents unauthorized state changes across environments.

How do I verify deployment artifacts before production activation?

Deployment artifacts are verified by enforcing strict validation against current network state and governance policies before production activation. This systematic validation ensures all safety boundaries are met prior to any production-level contract deployment.

Can I use automated release management for ZKP2P smart contracts?

Automated release management for ZKP2P smart contracts is restricted by safety guardrails. The system prevents automated production releases and requires manual, explicit validation of on-chain state and deployment artifacts to coordinate secure contract lifecycle management.