beacon-proxy

Coordinate synchronized upgrades for identical proxies via a shared UpgradeableBeacon.

120|12|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ccashwell/evm-cortex --skill beacon-proxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beacon-proxy
Source: https://github.com/ccashwell/evm-cortex/tree/main/skills/beacon-proxy
Command: npx skills add https://github.com/ccashwell/evm-cortex --skill beacon-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes upgrade logic for many identical proxy instances by using a single beacon to coordinate upgrades.

Core Features & Use Cases

  • Beacon-centric upgrades: all proxies reference one UpgradeableBeacon, upgrading all of them in sync.
  • Bulk upgrades: upgrading the beacon propagates to all proxies in a single transaction.
  • Factory and deterministic patterns: supports factory deployments and deterministic proxies.
  • Comparative guidance: useful when comparing Beacon to UUPS or Transparent patterns.
  • Typical scenarios: vaults, accounts, pools with uniform logic.

Quick Start

Deploy an initial Vault implementation, create a Beacon, and instantiate BeaconProxy proxies to start using the beacon pattern.

Frequently Asked Questions about beacon-proxy

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

FAQPage Schema
How do I upgrade many identical smart contracts at once using a beacon proxy?

To upgrade many identical smart contracts at once, a beacon proxy pattern centralizes upgrade logic in a single UpgradeableBeacon. Updating the beacon implementation automatically synchronizes the upgrade across all BeaconProxy instances in one transaction.

What is the difference between beacon proxy and UUPS upgradeable patterns?

A beacon proxy centralizes upgrade logic in a shared beacon to synchronize many proxies, whereas UUPS manages upgrades within the implementation contract itself. Beacon proxies are optimal for bulk updates to replicated contracts like vaults or pools.

Can I deploy deterministic beacon proxies using OpenZeppelin factories?

Yes, you can deploy deterministic beacon proxies using OpenZeppelin factories. The beacon proxy pattern supports deterministic deployments, allowing you to create predictable addresses for replicated contracts that reference a shared UpgradeableBeacon.

When should I use a beacon proxy instead of a transparent upgradeable proxy?

Use a beacon proxy when you need to coordinate synchronized upgrades across many identical contracts like accounts or pools. Transparent upgradeable proxies are better suited for individual contract instances where upgrade logic is managed independently.

Does the beacon proxy pattern enforce storage layout restrictions?

Yes, the beacon proxy pattern enforces an append-only storage layout. Using OpenZeppelin's UpgradeableBeacon and BeaconProxy implementations ensures storage compatibility is maintained across all synchronized proxies during upgrades.