Glossary¶

• Governor: CenturionUpgradeGovernor, timelocked upgrade and approval authority.
• roleAdmin: address controlling role grants/revocations and role-admin transfer.
• proposer: role that creates upgrade operations.
• executor: role that executes queued upgrade operations.
• queuer: role that queues operations and starts timelock.
• canceller: role that cancels queued operations.
• registrar: role that registers upgrade targets and genesis approvals.
• timelock: mandatory waiting period between queue and execute.
• multisig: threshold-signature account used for role custody.
• EOA: externally owned account controlled by private key.
• proxy: delegating shell contract preserving state while implementation changes.
• transparent proxy: proxy pattern with admin-separated call behavior.
• beacon: contract storing shared implementation address for many proxies.
• beacon proxy: proxy that resolves implementation through beacon.
• implementation: logic contract used via delegatecall by proxy.
• codehash: runtime bytecode hash of a contract address.
• expected codehash: stored or recomputed runtime bytecode hash used by policy and custody checks.
• live approval registry: governor mapping of approved implementations and metadata.
• approved implementation: implementation matching kind/version/policy/codehash expectations.
• fail closed: default to revert/disable instead of allowing uncertain behavior.
• permissioned: access requires explicit allowlist admission.
• permissionless: access path does not require admission allowlist.
• allowlist: intent-based admission set managed by allowlistAdmin.
• deposit intent: hashed tuple authorizing one deposit attempt.
• withdrawal credentials: deposit credential bytes that route execution withdrawals.
• vault: validator-specific custody account proxy.
• controller: CenturionEconomicController, accounting and policy engine.
• gatekeeper: CenturionClaimGatekeeper, claim policy and cap engine.
• principal: protected base stake target per seat.
• reward: surplus value potentially claimable under policy.
• receipt: recorded physical inflow event.
• consensus reward: observation-derived reward delta from finalized consensus data.
• physical receipt: execution-layer inflow physically received by vault.
• actual balance: observed real balance value in risk updates.
• effective balance: consensus effective balance metric used for risk state logic.
• dust: small principal gap classification state.
• recovery: state where deficit repair takes precedence.
• stop loss: severe risk state that disables normal claims.
• slashing: penalty or severe risk event reducing validator safety state.
• exit: validator exit lifecycle transition.
• stale oracle: observation freshness violation.
• safe epoch: cleared epoch threshold used for receipt safety checks.
• claimable: amount eligible for payout under current state and caps.
• reserve coverage: configured reserve support limits/proofs for smoothing/deficit handling.
• storage layout: ordering/slot map of proxy-held state across implementations.