upgrade-vs-immutable-decision

Decide upgrade or immutable posture for Solana programs with governance and risk mapping.

3|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/SanctifiedOps/solana-skills --skill upgrade-vs-immutable-decision
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrade-vs-immutable-decision
Source: https://github.com/SanctifiedOps/solana-skills/tree/main/skills/core-dev/upgrade-vs-immutable-decision
Command: npx skills add https://github.com/SanctifiedOps/solana-skills --skill upgrade-vs-immutable-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps governance teams and engineers decide whether a Solana program should be upgradeable or immutable, balancing trust, transparency, and operational needs.

Core Features & Use Cases

  • Decision framework: Clear criteria to map risks, assets, deployment contexts, and governance constraints to an upgrade posture.
  • Governance playbooks: Templates for upgrade/release processes, multisig/DAO workflows, notice periods, and changelogs.
  • Use Case: Before a major deployment or a key rotation, determine the appropriate upgrade posture and publish a policy and authority plan.

Quick Start

Provide the program id, governance structure, and risk appetite to determine recommended posture; outline steps to implement it, including rotating upgrade authority if needed, communicating changes, and documenting evidence.

Frequently Asked Questions about upgrade-vs-immutable-decision

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

FAQPage Schema
How do I decide if a Solana program should be upgradeable or immutable?▼

To decide on a Solana program's upgrade posture, map your deployment risks, governance setup, and operational flexibility needs against trust and transparency requirements to produce a documented upgrade authority policy.

What is a Solana upgrade authority and how does it affect program immutability?▼

A Solana upgrade authority controls program updates, where holding an upgrade authority key allows modifications while relinquishing it makes the program immutable, directly impacting governance and trust.

How do I configure a multisig for Solana program upgrade authority?▼

Configuring a multisig for Solana upgrade authority involves mapping your risk appetite and governance constraints to a multisig workflow, then documenting the authority ownership, notice periods, and release steps.

Can I rotate the upgrade authority on an existing Solana program?▼

Yes, you can rotate the upgrade authority on an existing Solana program during key rotation scenarios by applying a governance playbook that documents the new authority, communication policy, and verification steps.

When should I make a Solana program immutable instead of upgradeable?▼

You should make a Solana program immutable when your risk mapping determines that transparency and user trust outweigh operational flexibility, requiring a documented policy that removes upgrade authority.

What governance structure works best for managing Solana program upgrades?▼

The best governance structure for Solana program upgrades depends on your risk appetite, ranging from a single key for rapid updates to a multisig or DAO for distributed control, resulting in a documented authority plan.