deployment

Coordinate cargo-make tasks and Abstract scripts for AXONE contract deployments.

124|19|Updated Jul 11, 2022
One-click install
npx skills add https://github.com/axone-protocol/contracts --skill deployment-axone-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/axone-protocol/contracts/tree/main/.agents/skills/deployment
Command: npx skills add https://github.com/axone-protocol/contracts --skill deployment-axone-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates AXONE deployment workflows, coordinating cargo-make tasks, Abstract deployment steps, and on-chain lifecycle operations to simplify publishing, installing, and inspecting contracts.

Core Features & Use Cases

  • Publish contracts with cargo-make, including artifact handling and publish scripts.
  • Install modules on Abstract accounts.
  • Run local chain tasks (initialize, start, logs, stop) and verify deployments.
  • Inspect and debug deployments across local, testnet, and mainnet environments.
  • Use wrapper tasks to streamline the deployment process and avoid ad-hoc commands.

Quick Start

Follow the standard AXONE deployment workflow by publishing contracts, installing them on accounts, and inspecting deployments with cargo-make targets.

Frequently Asked Questions about deployment

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

FAQPage Schema
How do I automate contract publishing and module installation for AXONE?

Run local chain lifecycle tasks for AXONE deployments using dedicated cargo-make targets that initialize, start, stop, and fetch logs. These wrapper tasks coordinate the local-chain environment, allowing you to manage the network state and verify deployment operations without ad-hoc commands.

Does the AXONE deployment workflow support testnet and mainnet environments?

The AXONE deployment workflow supports inspecting and debugging deployments across local, testnet, and mainnet environments. It handles network alias configuration and post-deploy verification through specific cargo-make targets and Abstract scripts tailored for each network environment.

How do I manage credentials and network aliases when deploying AXONE contracts?

Manage credentials and network aliases for AXONE contract deployments through configured cargo-make tasks that satisfy credential setup and alias handling. The workflow integrates these configurations into its publish and install scripts, ensuring proper authentication across different deployment environments.

What is the best way to verify an AXONE deployment after publishing contracts?

The best way to verify an AXONE deployment is by using cargo-make wrapper tasks designed for post-deploy inspection. These tasks coordinate with Abstract deployment scripts to check the installed modules and contract states across local, testnet, or mainnet environments, ensuring successful on-chain lifecycle operations.