Important Functions in EOSIO

EOSIO Privileged Account

This account has unlimited access to CPU, NET, and RAM resources. An account consisting of the permitting committee representing the highest authority of the network will be set.

You can create specific permissions for each privileged action and you can also use a multi-signature (or "multisig") contract with variable parameters that will require the consent of most of the actors in the table. This privileged account will be called the eosio account.

EOSIO Privileged Features

EOSIO smart contracts are simple WebAssembly files. The WebAssembly format allows you to define imports, functions that are not declared in WASM itself but in the environment in which the WebAssembly code is run. EOSIO uses these built-in (intrinsic) functions to exchange data between the WebAssembly contract code and the EOSIO node nodeos. Every time the EOS virtual machine (EOSVM), which runs the WebAssembly code, reaches an intrinsic level, control of the program is transferred to the node controller code to resolve it. A complete list of intrinsic functions for EOSIO 2.0.X can be found here.


Update the resource limits associated with an account


account: The destination account
ram_bytes: The RAM limit in bytes
net_weight: Weight to determine your NET capacity
cpu_weight: Weight to determine your CPU capacity


Establish a new list of active producers (validators). Once the proposed block becomes irreversible, the new producers become active.


schedule: JSON with list of producers and their signing keys


Modify one or more parameters of the blockchain.


  • max_block_net_usage The maximum amount of net usage in a block

  • target_block_net_usage_pct The maximum percentage of net use, after this limit the network enters congestion mode.

  • max_transaction_net_usage The maximum use of net that the chain will allow, beyond the limits of the account.

  • base_per_transaction_net_usage The base amount of net usage billed for a transaction to cover incidentals

  • net_usage_leeway

  • context_free_discount_net_usage_num The numerator for the discount on net usage of context-free data

  • context_free_discount_net_usage_den The denominator for the discount on net usage of context-free data

  • max_block_cpu_usage The maxiumum billable cpu usage (in microseconds) for a block

  • target_block_cpu_usage_pct The target percent (1% == 100, 100%= 10,000) of maximum cpu usage; exceeding this triggers congestion handling

  • max_transaction_cpu_usage The maximum billable cpu usage (in microseconds) that the chain will allow regardless of account limits

  • min_transaction_cpu_usage The minimum billable cpu usage (in microseconds) that the chain requires

  • max_transaction_lifetime The maximum number of seconds that an input transaction's expiration can be ahead of the time of the block in which it is first included

  • deferred_trx_expiration_window The number of seconds after the time a deferred transaction can first execute until it expires

  • max_transaction_delay The maximum number of seconds that can be imposed as a delay requirement by authorization checks

  • max_inline_action_size Maximum allowed size (in bytes) of an inline action

  • max_inline_action_depth Recursion depth limit on sending inline actions

  • max_authority_depth Recursion depth limit for checking if an authority is satisfied


Allows you to establish an account as privileged.


account: La cuenta que se quiere setear como privilegiada
is_priv: 0 para falso, mayor a 0 para verdadero

System Actions

These actions do not need to be executed by a privileged account.


Create a new account.


creator: Name of the account that creates the new account
name: New account name
owner: Owner public key
active: Active public key

set code

Set code publish or update a smart contract in an account


account: The account to which you want to post a contract
code: The code in the form of a binary BLOB

set abi

It allows to establish or update the abi for the smart contract, it is identified by account_name.


account: The name of the destination account
abi: The ABI


Update an account's permissions.


account: The account to be modified.
pemission: The name of the new permission
parent: The parent permission of the new permission
auth: The JSON defining permission authorization


Removes permission authorization from an account.


account: The destination account
permission: The name of the permission to be removed


Assign a specific action of a contract to a specific permission, five actions cannot be linked updateauth,deleteauth,linkauth,unlikauth,canceldelay


account: The destination account
code: Account owner of the action to link
type: The action to be linked
requirement: Permission to link.


It is the reverse of linkauth


account: The destination account
code: Account owner of the action to be unlinked
type: The action to be unlinked

Native Token Contract eosio.token

These actions can be executed by any account in order to issue their own token.


Allows an issuer account to create a token.


issuer: The account that creates the token
maximum_supply: The maximum amount next to the token symbol.


This action distributes a certain number of tokens to an account.


to: Account to which the tokens are distributed
quantity: The amount of tokens to distribute
memo: Memo accompanying the transaction


The opposite of creating a token.


quantity: The amount of tokens to withdraw
memo: Memo accompanying the transaction


Transfer an "n" amount of tokens from a source account to a destination account


from: Source account from where tokens are debited
to: Target account to which to credit the tokens
quantity: The amount of tokens
memo: Memo accompanying the transaction
Last updated on