Makes your EOS contracts action data understandable, by human.

It's hard for the average user to understand what is going on the chain due to the complexity.

Dapp developers are also often questioned by users about the meaning of the data on the chain.

The emergence of EOS Semantics can make common users understand contract data and lower the threshold for common users to participate, thus improving the activity of Dapp.

EOSPark was the first EOS explorer to come up with and implement contract semantics.

At first, it was only applied to system contract and won wide praise from users. We are now opening up its semantic capabilities to further serve the vast majority of contract developers.

The basic principle of EOS Semantics is similar to the Ricardian Contract, which renders the data of a contract action into a human-readable natural language through a template.

In addition, EOS Semantics provides more powerful functions, such as account/contract link, code highlighting, multi-language and so on.

Take EOS system contract eosio.token as example, it's contract action data is below:

{
  "data": {
    "quantity": "1.0000 EOS",
    "to": "supereospark",
    "memo": "Good job EOS Semantics"
  }
}

The correspond needed semantic info is below:

{
    "issue": {
        "actionName": "Issue Token",
        "template": "System issued <Token :quantity="quantity" contract="eosio.token"/> to <Account :to="to" /> <Memo>{{memo}}</Memo>"
    }
}

It will be finally rendered as below:

1. Clone

git clone https://github.com/BlockABC/eos-semantics
cd eos-semantics

2. Add semantics info

   2.1 Test your template info in Playground

   2.2 Create new .js file under /semantics directory named by contract's account name, and add semantic info.

   For detailed semantic info see DOC below，or refer to existing contract semantic info eosio

   2.3 Compile

   npm run build
   

3. Submit PR

Readable action name

template is a html template, taking a form like Vue template syntax. It would be easy for you if you are familiar with Web Development.

One thing to be aware of, the syntax of template is a subset of Vue's template syntax for security.

EOS Semantics also has some builtin components to make it easier for you and we can then unify UI style.

If component will render different component based on condition.

<If :condition="true">Component on true</If>

Link will render an a tag.

<Link :to="url">Some Web Page</Link>

Accounts will receive accounts array as prop, and render a accounts list.

<Accounts :accounts="accounts" />

Account will render an 'a' tag, click which will redirect to correspond account page.

<Account :to="account" />

Contract will ren Contract will render an 'a' tag, click which will redirect to correspond contract page.

<Contract :to="account" />

Transfer will render transfer UI

<Transfer :from="from" :to="to" :quantity="quantity" :contract="action.account" :memo="memo"/>

Memo will render memo ( Commonly used in transfer. ).

<Memo>{{memo}}</Memo>

Token will render a Token, support multiple token format.

<!-- Only Token name (and contract) will be rendered -->
<Token :symbol="symbol" contract="eosio.token"/>

<!-- Token with amount -->
<Token :symbol="symbol" contract="eosio.token" :amount="123.456"/>

<!-- Sometimes you need to specify token's decimals -->
<Token :symbol="symbol" contract="eosio.token" :amount="amount" :decimals="4"/>

<!-- It can also receive what format is in EOS -->
<Token symbolValue="47575848338" quantity="123.4567 EOS"/>

Highlight will render a highlighted json

<Highlight :json="auth"/>

Quantity will render a comma-separated number.

<Quantity :num="num"/>

ActionInterface will render an action name.

<ActionInterface :account="code" :name="type"/>

For more information, please join us on telegram: EOSPark Telegram