Skip to main content
Types of Policies
Updated over a week ago

Through the smart contracts, access permissions are programmatically managed and enforced, ensuring that only authorised operators can engage in specific transactions or operations. Brahma Console enables various Access Control parameters through Policies to ensure optimal transparency and delegation outlets.

Our Policies employ a quantitative approach to assess user’s eligibility, taking into consideration factors such as assigned actions within Console, transaction history, and adherence to protocol governance rules.

A. Global Policy

The Console Global Policy is a series of policies restricting contract interactions, creating a controlled "Walled Garden" where transactions can only have a specific set of recipients.

Console admins can activate Global Policy to allow precise protocol interactions, and set overarching asset policies and granular transfer policies, ensuring compliance. This approach mitigates numerous risks and fosters a secure environment for authorised transactions, reinforcing transparency within all overlapping policy frameworks.

  1. Asset Policy

  2. Transfer Recipients

Asset policies within Sub-Accounts create a resilient framework that not only protects assets from contract vulnerabilities but also ensures a strategic and controlled approach to fund management, thereby enhancing the overall operational integrity of the Sub-Account.

Admin can assign transaction limits on selected assets with a maximal outgoing limit in a given time frame. This ensures that assigned operators are in a controlled transaction environment.

To limit transactions on specific assets, the admin can also place restrictions by barring the asset from the whitelist.

B. Protocol Policy

The Interaction Policy regulates system interactions by whitelisting approved protocols and custom contracts. External protocol interactions are restricted by default to enhance security and prevent unauthorised third-party access. The policy acts as a contract gatekeeper, ensuring adherence to predefined parameters and safeguarding overall system integrity.

Admins can pre-verify and whitelist certain protocols and define contract functions for operation within the Sub-Account.

C. Granular Transfer Policies

Granular Transfer policies upkeep transfer limits within the Sub-Account

As an admin, transfer funds, monitor ownership transactions, and employ kill-switches with a streamlined emergency protocol.

Did this answer your question?