Overview of EOS Account Permissions
The EOSIO blockchain platform employs a flexible and robust account permission management system designed to provide users with granular control over their assets and operational authorizations. In this system, every EOS account is configured with two core permissions by default: Owner Key and Active Key. Understanding the functions, hierarchical relationships, and best practices of these two permissions is crucial for EOS users to effectively manage their digital assets.
Owner Key
The Owner Key is the highest-level permission for an EOS account, representing complete ownership of the account. It holds supreme control and can perform any operation within the account, including but not limited to:
- Modifying, adding, or deleting any other permissions in the account, including the Active Key.
- Recovering the account.
- Performing all types of transactions and operations.
Given the powerful capabilities of the Owner Key, it is generally recommended to be kept as a cold storage key pair. This means storing it on an offline device and only using it when account recovery, major permission changes, or extreme circumstances are necessary, to minimize the risk of compromise.
Active Key
The Active Key is a sub-permission of the Owner Key, primarily used for performing daily account operations. The design philosophy behind the Active Key is to facilitate frequent user interactions without exposing the highest-level Owner Key. Its main uses include:
- Initiating token transfers.
- Staking and unstaking resources.
- Participating in network voting.
- Executing smart contracts, such as interacting with decentralized applications (DApps).
An EOS account can have multiple Owner and Active permissions, which provides flexibility for multi-signature accounts and team collaboration. However, users must exercise extreme caution when using DApps and authorizing smart contract execution. Some DApp contracts may include operations that modify account permissions, which could lead to unauthorized Active Keys appearing in the account, thereby posing a risk of asset loss. Users should carefully review the scope of permissions requested by any contract before authorizing its operations. Users can check real-time EOS market data and related news on market platforms like Svmuu to better understand market dynamics.
Features of the EOSIO Permission System
The EOSIO permission system has several notable features:
- Parent-Child Hierarchical Structure: EOSIO adopts a parent-child hierarchical permission structure, where lower-level permissions (child permissions) are derived from higher-level permissions (parent permissions). A parent permission inherently possesses the capabilities of all its child permissions, meaning the Owner Key can control the Active Key, and the Active Key can also derive lower-level custom permissions.
- Custom Permissions: In addition to the default Owner and Active permissions, EOS accounts also support the creation of custom permissions. These custom permissions can be used to extend future account management, for example, by setting independent permissions for specific operations (such as voting only or managing only a specific DApp). Custom permissions can be child permissions of the Active Key or other custom permissions, forming a flexible permission tree.
- Permission Composition: Each permission in EOS consists of a permission name, a permission parent, and required authorization. The required authorization is further detailed into Threshold, Keys, Accounts, and Wait Time. These parameters collectively determine the signature combinations and conditions required to perform specific operations, providing a highly configurable security policy.
