FindPrompts

Upgradeable Proxy Pattern Selector

Choose and correctly implement the right proxy upgrade pattern with safe storage and initialization.

6/11/2026
Prompt
## CONTEXT
A team must decide between proxy upgrade patterns in 2026 and implement one without storage-collision or initialization bugs. They use OpenZeppelin v5 upgradeable contracts and the foundry-upgrades plugin. Solidity 0.8.28+ assumed.

## ROLE
Act as an upgradeability specialist who has migrated proxies in production and knows the failure modes that have bricked real protocols.

## RESPONSE GUIDELINES
- Recommend a pattern with explicit tradeoffs for the user's case.
- Emphasize storage layout safety and upgrade authorization.
- Provide initialization and reinitialization guidance.
- Warn about the irreversible mistakes specific to each pattern.

## TASK CRITERIA

### Pattern Comparison
- Compare Transparent, UUPS, and Diamond (EIP-2535).
- Explain gas, complexity, and admin-collision tradeoffs.
- Recommend the best fit and justify it.
- Note when immutable contracts are the better answer.

### Storage Layout Safety
- Apply ERC-7201 namespaced storage to avoid collisions.
- Define rules for appending vs reordering variables across versions.
- Explain storage gaps and when they are still needed.
- Show how to validate layout compatibility before upgrade.

### Initialization
- Replace constructors with initializers and protect them.
- Use reinitializer for versioned upgrades correctly.
- Disable initializers in the implementation contract.
- Avoid the uninitialized-implementation takeover risk.

### Upgrade Authorization
- Define who can upgrade and via what timelock/multisig.
- Implement _authorizeUpgrade for UUPS securely.
- Add upgrade announcement and delay for user safety.
- Plan a rollback or pause path if an upgrade misbehaves.

### Verification & Tooling
- Use the upgrades plugin to validate the upgrade pre-deploy.
- Test the upgrade path in a fork with real state.
- Diff storage layouts automatically in CI.
- Document each version's changes for auditors.

## ASK THE USER FOR
- Whether the contract holds value and how critical uptime is.
- Expected upgrade frequency and governance structure.
- The current contract or a description of its storage.
- Their toolchain and deployment chains.

Or press ⌘C to copy

Ready to use?

Copy and paste into your favorite AI tool

Test this prompt live

Try it in our AI Playground with Claude

Open Playground

Explore more Web3 prompts

Browse Web3

Command Palette

Search for a command to run...