PROTOCOL ADMINISTRATION
Colony Registry
Manage registered colonies, per-colony fee rates, and protocol settings.
One wallet controls everything — it owns the registry and receives all fee settlements.
Owner actions locked. Click any action button below — MetaMask will prompt you to connect the Protocol Wallet shown in the stat box above.
OWNER ACTIONS
ETH accrued per colony per S-token send(). Applies to all colonies unless overridden in the colony detail drawer.
Fee updated ✓
% of the fee sent to the colony founder wallet. Max 50%. Per-colony overrides set in the colony detail drawer.
Founder share updated ✓
Transfers registry ownership and fee destination to a new wallet. The current wallet loses all admin access. Cannot be undone without the new wallet's cooperation.
Protocol wallet changed ✓
MANUALLY REGISTER A COLONY
New colonies register themselves automatically when deployed via zpc.finance/create.
Use this only for colonies that were deployed before the registry existed, or deployed without going through the create flow.
You will need the colony's contract address (from the deployer's MetaMask activity or Basescan).
The slug is the URL identifier (e.g. daves-colony) — must be unique and lowercase with hyphens only.
Colony registered ✓
COLONY IMPLEMENTATION UPGRADE
All colony contracts are BeaconProxy instances pointing at a single UpgradeableBeacon.
Upgrading the beacon's implementation upgrades every colony simultaneously — no re-registration needed.
Deploy a new Colony implementation, verify it on Basescan, then enter its address below.
This is a protocol-level action and cannot be undone.
Calls beacon.upgradeTo(newImpl). All existing colony proxies instantly use the new logic.
New colonies deployed via the wizard will also use the new implementation.
All colonies upgraded ✓
Updates the beacon address stored in the registry. New colonies read this address from the registry.
Use after deploying a fresh beacon (e.g. a new colony suite for a separate upgrade track).
Beacon updated ✓