sails-program-evolution

Plan safe V1 to V2 cutover for deployed Gear/Vara Sails contracts.

17|23|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/gear-foundation/vara-skills --skill sails-program-evolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sails-program-evolution
Source: https://github.com/gear-foundation/vara-skills/tree/main/skills/sails-program-evolution
Command: npx skills add https://github.com/gear-foundation/vara-skills --skill sails-program-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the high risk of breaking deployed Gear/Vara Sails contracts during upgrades, solving the complex challenge of evolving live smart contracts without disrupting existing frontends, indexers, or user workflows.

Core Features & Use Cases

  • Change Classification: Categorizes contract changes as additive, breaking, migration-readiness only, or immediate migration to guide safe upgrade paths.
  • Safe Cutover Planning: Designs V1 to V2 cutover procedures including ReadOnly or write-disable behavior for old contract versions and explicit rollback targets.
  • Compatibility Preservation: Ensures frontend, generated client, and indexer compatibility during contract upgrades, with clear steps for switching to the new contract version.
  • Use Case: For example, if you need to add a new feature to a live Sails token contract, this Skill guides you to deploy a V2 version, set the V1 contract to ReadOnly during cutover, and update the frontend to point to the new version with zero user impact.

Quick Start

Request a safe evolution plan for your deployed Sails contract that covers versioning, cutover steps, and frontend compatibility checks.

Frequently Asked Questions about sails-program-evolution

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

FAQPage Schema
How do I upgrade a deployed Sails smart contract on the Gear network without downtime?

Upgrading a live Sails smart contract safely involves deploying a V2 version while setting the V1 contract to ReadOnly or write-disable behavior. This prevents disruption to existing frontends and indexers during the cutover period.

What is a safe cutover plan for Gear Vara contract evolution?

A safe cutover plan for Gear Vara contract evolution includes explicit rollback targets, ReadOnly behavior for old versions, and off-chain component impact assessment. This preserves public route and event compatibility during the migration.

How do I migrate smart contract state from V1 to V2 in Sails?

State migration from V1 to V2 in Sails requires classifying changes as migration-readiness only or immediate migration. You design explicit cutover procedures and assess off-chain component impacts before implementing changes to the live program.

Can I add new features to a live Sails token contract without breaking existing frontend integrations?

You can add new features to a live Sails token contract without breaking frontend integrations by deploying a V2 version and setting V1 to ReadOnly during cutover. The Skill guides compatibility preservation for generated clients and indexers to ensure zero user impact.

What are the limitations when upgrading deployed Gear network contracts?

Upgrading deployed Gear network contracts requires assessing off-chain component impacts and establishing rollback targets before modifying live Sails programs. Breaking changes demand immediate migration, while additive changes allow simpler compatibility preservation for public routes and events.