Skip to content
This repository was archived by the owner on Aug 30, 2022. It is now read-only.

fix the token desc table #395

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix the token desc table #395

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -181,6 +181,7 @@ These are the actions implemented and publicly exposed by the `eosio.msig` contr
The `eosio.token` contract defines the structures and actions that allow users to create, issue, and manage tokens for EOSIO based blockchains.

These are the public actions the `eosio.token` contract is implementing:

|Action name|Action description|
|---|---|
|create|Allows an account to create a token in a given supply amount.|
Expand Down Expand Up @@ -208,4 +209,4 @@ However, the current method is opaque and leaves undesirable side effects on spe
The only action implemented by the `eosio.wrap` system contract is the `exec` action. This action allows for execution of a transaction, which is passed to the `exec` method in the form of a packed transaction in json format via the 'trx' parameter and the `executer` account that executes the transaction. The same `executer` account will also be used to pay the RAM and CPU fees needed to execute the transaction.

Why is it easier for governance actions to be executed via this contract?
The answer to this question is explained in detailed [here](./03_guides/07_how-to-use-eosio.wrap.md)
The answer to this question is explained in detailed [here](./03_guides/07_how-to-use-eosio.wrap.md)