1. Main Console Account: Primary user Safe, serving as the central wallet within the Console dashboard, facilitating all funding and transactions.

  2. Sub-Accounts: Secondary accounts or Sub-Safes linked to the main Console, allowing for organised operations and management of specific actions, automations, and on-chain activities.

  3. Brahma Relayer: Developed for Console by Brahma developers, Brahma Relayer optimises transaction speed by routing transactions through RPC for speed + cost efficiency, quality, and gas efficiency, streamlining execution with a focus on user-friendly abstraction and batched transactions.

  4. Txn: Short for "Transaction"

  5. Batched Txn: Multiple transactions processed as a single transaction, enhancing execution efficiency, improving the convenience of signing, and reducing gas overhead.

  6. Action: A specific task or operation initiated within Console, triggered by user input, and has a one-time or repeat-as-required frequency. Example: Initiating asset swaps within Console

  7. Automation: The implementation of technology to perform tasks or processes without direct human intervention, enhancing efficiency and reducing manual effort.

  8. Policy: A set of rules governing behaviour of a Sub-Account, its deployment thresholds, and interactions via role-based permissions assigned by the owner of the Main Console.

  9. Policy Authenticator: A module ensuring pre-checks to assigned policies, verifying the legitimacy of actions performed before transaction execution.

  10. Safe Module: A system designed to protect and manage sensitive information and assets within Safe's broader framework.

  11. Safe Guard: Protective measures implemented to prevent unauthorised access, risks, or potential threats to systems deployed via Safe within Console.

  12. Relayer: An intermediary entity responsible for facilitating communication and transactions between different components or networks.

  13. Console Hook: A connection interface allowing external tools or applications to integrate with and interact with the Main Console.

  14. Operator: An individual responsible for managing and overseeing the operations within an assigned Sub-Account.

  15. Owner: Primary owner of the Console/Sub-Account with ultimate control and ownership rights with authority level to assign Policies, pre-fund, and add operators to Sub-Accounts.

  16. Walled Garden: A controlled environment referring to a secure and isolated space within a system. Herein, Console Sub-Accounts guarded with granular policies, replicate a walled garden set-up.

Last updated