This account has unlimited access to CPU, NET, and RAM resources representing the highest authority of the network which can execute priviledged functions.
Usually this authority is invoked by a multi-signature (or "multisig") contract that will require the consent of a super-majorit of the block producers. This privileged account will be called the
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.
Establish a new list of active producers (validators). Once the proposed block becomes irreversible, the new producers become active.
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.
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.
These actions do not need to be executed by a privileged account.
Create a new account.
Set code publish or update a smart contract in an account.
It allows to establish or update the abi for the smart contract, it is identified by account_name.
Update an account's permissions.
Removes permission authorization from an account.
Assign a specific action of a contract to a specific permission, five actions cannot be linked updateauth, deleteauth, linkauth, unlikauth, canceldelay.
It is the reverse of linkauth.
Native Token Contract
These actions can be executed by any account in order to issue their own token.
Allows an issuer account to create a token.
This action distributes a certain number of tokens to an account.
The opposite of creating a token.
Transfer an "n" amount of tokens from a source account to a destination account.