Solana Squads Upgrade

Construct Solana Squads v4 vault transactions for multisig program upgrades.

4|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/widnyana/eyay-toolkits --skill solana-squads-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Solana Squads Upgrade
Source: https://github.com/widnyana/eyay-toolkits/tree/main/plugins/solana-onchain/skills/solana-squads-upgrade
Command: npx skills add https://github.com/widnyana/eyay-toolkits --skill solana-squads-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Squads-v4 multisig governance makes Solana program upgrades safer, but building the correct upgrade proposal, wiring IDL/metadata updates, and turning it into a CI-ready workflow is operationally tedious and error-prone.

Core Features & Use Cases

  • CI-driven upgrade proposal creation: Builds a Squads vault transaction via squads-program-action instead of attempting a direct on-chain upgrade.
  • Supports Anchor IDL and program-metadata flows: Updates Anchor IDL buffers or writes/initializes program-metadata buffers (including chunked realloc/extend behavior for larger payloads).
  • End-to-end upgrade lifecycle coverage: Includes PDA verification hooks (via pda-tx), instruction ordering, compute-budget tuning, and failure-oriented troubleshooting for failed proposals.
  • Use cases: Setting up GitHub Actions CI/CD for Squads upgrades, creating and debugging upgrade proposals, and coordinating optional IDL/metadata updates alongside the BPF upgrade.

Quick Start

Use the Solana Squads Upgrade skill to generate the Squads v4 upgrade proposal transaction for your program using your CI inputs (rpc, program, buffer, multisig, and voter keypair).

Frequently Asked Questions about Solana Squads Upgrade

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

FAQPage Schema
How do I automate Solana program upgrades through a Squads multisig in GitHub Actions?

Automating Solana program upgrades through a Squads multisig in GitHub Actions involves using a CI/CD workflow to construct a vault transaction proposal via squads-program-action, rather than executing a direct on-chain upgrade.

How does Squads multisig governance handle Anchor IDL and program-metadata updates during an upgrade?

Squads multisig governance handles Anchor IDL and program-metadata updates by building instruction ordering that updates IDL buffers or initializes and chunks program-metadata buffers before executing the BPF program upgrade.

Can I use GitHub Actions CI to create Squads v4 upgrade proposals for Solana programs?

Yes, you can use GitHub Actions CI to create Squads v4 upgrade proposals by configuring inputs like rpc, program, buffer, multisig, and voter keypair to generate the proposal transaction securely.

What is the correct instruction ordering for a Squads multisig Solana program upgrade proposal?

The correct instruction ordering for a Squads multisig Solana program upgrade proposal starts with PDA verification, followed by Anchor IDL or program-metadata updates, and concludes with the BPF upgrade execution.

Why does my Squads v4 upgrade proposal fail during CI simulation and how do I add compute budgeting?

Squads v4 upgrade proposal failures during CI simulation often stem from compute budget limits; you can resolve this by applying compute-budget tuning and utilizing the workflow's built-in simulation and retry behavior.

Do I need a direct on-chain upgrade execution if I use a Squads multisig vault transaction workflow?

No, you do not need a direct on-chain upgrade execution if you use a Squads multisig vault transaction workflow, because the process builds a proposal-based vault transaction for governance approval instead.