Protocol Actors
Every role in a Qiro vault, what it can and cannot do, and which powers sit behind a delay.
A Qiro vault separates authority across several roles rather than concentrating it in one administrator. This page lists each role, what it controls, and what it cannot reach.
One distinction runs through the whole table and is worth reading first.
Instant authority and delayed authority
Every governed contract carries two authorities, not one. The split is by direction of risk, not by seniority:
Anything that reduces exposure can be done immediately; anything that increases it waits. The timelock is seeded to the owner at construction and handed to an external timelock contract afterwards — see Smart Contract Architecture for why that handoff cannot be reversed.
Roles
Owner
Rotate role holders — fee manager, whitelist manager, pausers, curator Remove a position manager Lower a sanctioned limit Service the redemption queue Cancel a request administratively
Change fee rates Whitelist a position manager Raise a cap Add a subaccount Move investor capital to itself
Instant. Non-renounceable; transfer is two-step and blocked until the timelock is wired
Timelock
Change fee rates and collectors Whitelist a position manager Raise a sanctioned limit Add a subaccount Rotate the timelock itself
Anything reserved to the owner or the curator
Every call sits behind the external timelock's delay
Fee Manager
Collect accrued performance and management fees to their configured collectors
Set fee rates Set collector addresses Touch investor capital
Collections must be at least 15 days apart after the first
Curator
Deploy capital to a whitelisted subaccount via invest()
Pull it back via redeem()
Post the NAV mark via setNAV()
Move capital to an address that is not a whitelisted subaccount Add a subaccount Set its own limits Withdraw to itself
setNAV() is bounded by a time-weighted deviation guard
Fees settle against the old mark first
Investor Whitelist Manager
Add and remove investor addresses from the whitelist
Anything else
Exists only in permissioned vaults; reverts if the vault is permissionless
Pauser
Pause and unpause the vault
Any configuration or capital movement
Several pausers may hold the role at once; added by the owner
Investor
Deposit and mint Request redemption Claim and cancel Delegate to an operator
Transfer shares to a non-whitelisted address
Must be whitelisted in a permissioned vault Deposits and requests require the vault unpaused
Operator
Request, claim and cancel on behalf of a controller who approved them
Anything the controller could not do
Approved per address by the controller via setOperator
Contracts hold authority over one another too. The Vault accepts capital instructions only from its Vault Strategy Manager, and share movements tied to redemption only from its Redemption Manager; the VSM accepts capital calls only from a position manager it has already whitelisted.
What the timelock gates
Five calls sit behind the delay. Every one of them either opens a new route for capital or increases what can flow down an existing route.
StakedVault
setFeeConfig
Changes fee rates and collector addresses
VaultStrategyManager
setWhitelistStatus(pm, true, …)
Admits a new position manager
VaultStrategyManager
raiseSanctionedLimit
Increases a position manager's cap
SubaccountPositionManager
addSubaccount
Admits a new destination wallet for capital
StakedVault
VaultStrategyManager
SubaccountPositionManager
setTimelock
Rotates the timelock authority itself
Their de-risking counterparts are deliberately not delayed: removing a position manager is setWhitelistStatus(pm, false, …) and lowering a cap is lowerSanctionedLimit, both instant on the owner, so a position manager behaving badly can be dropped without waiting.
Two properties keep the delay from being sidestepped. setTimelock is itself timelocked, so the authority can only be rotated through its own delay and the owner can never re-point it. And raiseSanctionedLimit rejects a value that is not strictly greater than the current cap, so it cannot be used as a back door to lower one instantly.
See Smart Contract Architecture for the contracts these roles act on.
Last updated