EOS Account Permissions

What makes EOS different from other blockchains is the accounting system it possesses. EOS holds A 12 character name account. Whenever an end user needs to transact funds, he is required to sign a transaction for the account.

The user is equipped with one or more keys within the chain, which are adaptable to changes. One can alter the keys, setting varied permission management system to the account.

EOS Account

An EOS account acts as a human-readable identifier on blockchain with fixed 12 characters encompassing format (a-z) and (1–5). Unlike other blockchains, EOS account names are unique and others identify them via this name. The most fascinating feature that EOS offer to its clientele is the creation of different accounts from a single pair of keys. And these accounts can be owned by an individual or group of individuals depending on the configured permission settings. Every EOS account has two native named permissions (owner and active).

EOS Permissions

EOS permissions are mainly Owner and Active and these are the standard permissions that every account possesses. While creating an account both permissions will be setup default with a set of key pairs (private and public).

It is even possible for an account to set different keys for its owner and active.

For an EOS account, the owner permission acts as the “root access” to enter it…If someone has the private key for owner permission, they are prone to do anything with your EOS account. Whereas the active permission acts much more safeguarding you EOS account.

In an EOS account permission, the owner permission set the permission for adding new owner and changing the existing authorities within the account. Also adding the new keys to the authorities are within the pursuit of ownerpermission. Active permission is mainly into pushing the transactions.

Apart from this anyone can make custom permissions in EOS making it more flexible to use. The owner and active permissions are standard permissions that every account has.

In addition to the native permissions, an account can even have custom permissions. It is normally done for further extension of account management. Usually, these are done with contract accounts that are deployed with some dapp contracts. Permission for any given authority can be assigned to one or multiple public keys or a valid account name. That is an authority can have multiple keys or accounts as its permission level.

Continue Reading… EOS Account Permissions

| Follow us on Twitter : @Blockchain_E

| Related Topics:

| Blockchain in Supply Chain Management | Crypto Pump and Dump |