Access control methods

The vault has one owner that can be changed. The owner can grant the role to the executor or turn off CrossChainStatus to block calls from vault copies on other networks. Vault has built in mechanics to validate the call.

• Events:

  • RoleGranted(bytes32 role, address account, address sender): Emitted when a role is granted to an account.

  • RoleRevoked(bytes32 role, address account, address sender): Emitted when a role is revoked from an account.

  • VaultOwnershipTransferred(address indexed oldOwner, address indexed newOwner, address vault): Emitted when the ownership of a vault is transferred.

• Functions:

  • owner() -> address: View function that returns the address of the owner of the vault.

  • hasRole(bytes32 role, address account) -> bool: View function that returns whether a given account has a specific role.

  • grantRole(bytes32 role, address account): Grants a specific role to an account. Emits a RoleGranted event if the role had not been previously granted. Only the owner of the vault can call this function.

  • revokeRole(bytes32 role, address account): Revokes a specific role from an account. Emits a RoleRevoked event if the account had the role. Only the owner of the vault can call this function.

  • renounceRole(bytes32 role): Allows an account to revoke a specific role from itself, intended as a mechanism for accounts to lose privileges if compromised. Emits a RoleRevoked event if the calling account had the role.

  • creatorAndId() —> address s.creator, uint16 s.vaultId

  • getVaultProxyAdminAddress() —> address proxyAdmin