The upgrade authority of a Solana program is the key that can replace its code, so it controls everything the program does. Do not leave it in the deployer wallet. Move it to a multisig with several independent signers, rehearse an upgrade on devnet, and consider a timelock or making the program immutable once the code is stable and audited.
| Holder | Risk | Verdict |
|---|---|---|
| Deployer hot wallet | One leaked key replaces the program | Avoid |
| Development agency | You depend on a third party for your own code | Avoid |
| Multisig (for example 3 of 5) | Needs several signers to be compromised | Good default |
| Multisig plus timelock | Users get notice before any change | Best while upgradeable |
| None (immutable) | No upgrade risk, and no bug fixes | When the code is final |
- Whoever holds the upgrade authority can replace your program with any code, including code that drains funds.
- Move it from the deployer wallet to a multisig before launch, with signers who are different people on different devices.
- Rehearse one full upgrade through the multisig on devnet, so the first real one is not also the first attempt.
- Add a timelock if users hold funds in your program, so changes are visible before they run.
- Making the program immutable is irreversible: do it only when the code is final and audited.
Most teams spend weeks on the code and minutes on the key that can rewrite it. On Solana, a program deployed with the upgradeable loader can be replaced by whoever holds its upgrade authority. An audit covers the code at one commit. The upgrade authority decides what the code will be tomorrow, which makes it one of the first things auditors, partners and informed users look at.
What the upgrade authority is
A deployed program has a program account and a separate program data account that holds the code and the address of its upgrade authority. Anyone can read that address. You can see it with solana program show and the program ID, or in a block explorer. If the authority is a single wallet, the safety of your whole protocol is the safety of that one wallet.
Why a single key is a problem
- A leaked or phished key: a malicious upgrade can change every instruction in one transaction. The audited code no longer matters.
- A departing team member or agency: whoever deployed the program often still holds the key long after the project moved on.
- A lost key: with no one able to sign, you cannot ship a fix even for a critical bug.
Move it to a multisig
A multisig is a wallet that needs approval from several signers before it executes a transaction. On Solana, teams commonly use Squads for this. The steps are the same whichever tool you pick:
- 1. Choose signers and a threshold. for example 3 of 5. Pick people, not roles that one person fills, and put each key on its own hardware wallet.
- 2. Create the multisig and note its vault address. this vault address, not a member wallet, becomes the authority.
- 3. Transfer the authority. run
solana program set-upgrade-authoritywith the program ID and--new-upgrade-authorityset to the vault address. Check the result withsolana program show. - 4. Rehearse an upgrade. write a new build to a buffer, give the multisig control of the buffer, propose the upgrade, approve it and execute it, all on devnet first.
- 5. Document the procedure. who proposes, who reviews the diff against the audited commit, who signs, and how a signer is replaced if a key is lost.
Timelocks and immutability
A timelock adds a delay between the approval of an upgrade and its execution. It gives users and monitors time to see a change and react, and it limits the damage if signers are compromised. It matters most when users deposit funds into the program.
Making the program immutable removes the authority for good (--final in the CLI). It is the strongest guarantee for users and it cannot be undone, so you lose the ability to fix bugs. Many teams keep a multisig with a timelock through the first months, then revoke the authority once the code has run under real usage and a bug bounty.
Mistakes we see
- All signers in one place: five keys held by three people who sit in one office, share a password manager, or all use the same phone are not five independent signers.
- Signers who never signed: a multisig whose members have never executed a transaction is untested. Run a rehearsal.
- Ignoring other admin keys: a locked upgrade authority does not help if an admin instruction lets one key drain the vault. Review every privileged role, not just the upgrade key.
- No plan for lost keys: decide how a signer is rotated out before you need to.
If you hired a developer
State in the contract that you own the code, the repository and the upgrade authority, and confirm the transfer on-chain at delivery. The questions in how to hire a Solana development company cover this, and milestone payments let you tie the final payment to the handover. Related terms: upgrade authority and multisig.
Frequently asked questions
What is the upgrade authority of a Solana program?
It is the key that is allowed to replace the code of a deployed program. Programs deployed with the upgradeable loader store it in a program data account. Whoever controls it can change what the program does, including its handling of user funds.
How do I check who holds the upgrade authority?
Run solana program show with the program ID, or look the program up in a block explorer. The output lists the upgrade authority address. If it is a normal wallet instead of a multisig, or it is not a key your team controls, fix that before launch.
How do I move the upgrade authority to a multisig?
Create the multisig, copy its vault address and run solana program set-upgrade-authority with the program ID and --new-upgrade-authority set to that address. Then check the result with solana program show and rehearse one upgrade through the multisig on devnet.
Should a Solana program be immutable?
Once the code is stable and audited, making it immutable removes the upgrade risk entirely, but it also removes your ability to fix bugs. Many teams keep a multisig with a timelock first and revoke the authority later. Revoking is irreversible.
Can the development agency keep the upgrade authority?
It should not. Put the handover of the upgrade authority and the repository into the contract and confirm it on-chain at delivery.
Get your launch security reviewed
Describe your program and launch date. Smart Match suggests verified Solana auditors and developers with a reason for each match. Free for teams.
Get matched →Looking for help with this? Browse Solana smart contract audit providers, or describe your project and get matched for free.
Related reading
- Solana audit readiness checklist: 12 things to prepare before the audit startsWhat to prepare before a Solana audit: a frozen commit, a short spec, invariants, tests that run in one command, agreed scope and a developer on call.
- Breakpoint 2026 launch-week checklist: what Solana teams should sort outLaunching around Solana Breakpoint 2026 (15-17 November, Olympia London)? A checklist for security, authorities, token launch, legal and growth, and what to book before the event.
- How long does a Solana audit take? Timeline from first call to final reportHow long a Solana smart contract audit takes: booking, waiting for a slot, the review, fixes and the fix review. Typical timelines and how to get audited sooner.