Skip to content

Interfaces

External Interface Files

  • interfaces/ICenturionWithdrawalVault.sol

In-File Interfaces (Selected)

Multiple contracts define local interfaces for external checks, for example:

  • proxy admin/beacon admin views in CenturionUpgradeGovernor.sol
  • baseline factory/controller/registry views in DepositContractCTN.sol
  • vault factory and upgrade-policy views in CenturionEconomicController.sol

Operational Implication

Many safety checks rely on interface views over external contracts. Deployments must ensure interface compatibility with live contracts at those addresses, or critical flows will revert fail-closed.

Source-Grounded Examples

DepositContractCTN reads factory metadata, controller readiness, vault metadata, upgrade registry assertions, and beacon authority. CenturionUpgradeGovernor reads proxy admin/implementation and beacon implementation. CenturionEconomicController uses the withdrawal-vault interface for exit and transfer operations.

Review Rule

When an interface function is used during deposit or upgrade validation, verify the implementation behind that interface is the expected component. Runtime code hash, target registration, and authority checks are part of the trust boundary.