Skip to main content
A vault on the current implementation separates control from daily operation. The admin owns the vault and can appoint other wallets to help run it. Each role acts only through its own wallet, and no role can take anything out of the vault. Trusset holds no role on any vault.
Role management is handled in the Issuer Portal, under Vault Details, Roles. It is not available through the API at the moment. API endpoints for it are planned. Until then, the API reads the roles of your own vault, as described below.

​
Roles

​
Handing the vault over

The admin nominates a new admin, and nothing changes until the nominee accepts. At acceptance every allocator and pauser is removed and the fee recipient returns to the new admin. The handover takes effect at once, with no notice period. A nominee that is a wallet of the same Trusset instance accepts in the Issuer Portal. Any other wallet accepts by calling acceptOwnership() on the vault contract from its own wallet. The vault stays listed under the instance that created it.

​
Reading roles through the API

  • Get Vault returns roles on your own vault: the admin, a pending admin, the fee recipient, the allocators and pausers, and the role epoch. staleAllocations and staleConsents list positions and draw consents the vault still holds in markets its current admin does not run.
  • List Vault Transactions records each role change with roleChange, naming who was appointed, removed, nominated or named.