Skip to main content

Operator Registration

VaultRegistrar uses OPERATOR_ROLE to restrict who can onboard vaults into the DS registry. In practice, the operator is your vault factory or protocol contract — the address that will call registerVault() on behalf of investors.

Operator responsibilities​

An operator typically does four things:

  1. Deploy or deterministically derive the investor vault address.
  2. Collect an investor EIP-712 signature.
  3. Call registerVault() on VaultRegistrar.
  4. Move tokens into the vault and execute protocol logic.

Self-service registration (this sandbox)​

On this testnet deployment, addOperator() is permissionless — any address can register itself as an operator directly from the frontend. No admin approval required.

Go to the Register as Operator page, enter your protocol contract address, and submit. The transaction calls addOperator(yourAddress) on-chain and completes in seconds.

Production deployments​

In production, addOperator() is gated by DEFAULT_ADMIN_ROLE. Only the registrar admin (Securitize) can grant operator status. Contact Securitize to get your protocol contract whitelisted on a production VaultRegistrar.

Frontend coverage​

FeatureAvailable
Register as operator (permissionless)Yes — Register as Operator page
Investor permission signing (EIP-712)Yes — Mock Protocol Example page
Check vault registration statusYes — Mock Protocol Example → Check tab
Revoke investor permissionYes — Mock Protocol Example → Revoke tab
Test your own protocol contractYes — Protocol Tester page

Next step​

Operator Onboarding Guide