1

What is the difference between defining actions inside a eosio contract such as eosio.token and other contracts.

Can I costomize the eosio contract : for example can I customize the eosio.token contract according to my use case?

| improve this question | | | | |
3

In many cases, the contract of custom tokens are based on eosio.token contract. You can add custom actions, or change the logic of existing actions such as create, issue, transfer and so on.

The main difference of eosio.system contract and others is that eosio.system is for privileged account, so it contains privileged APIs like setpriv etc. (Privileged APIs are not callable by normal account and you can find them from eosiolib/privileged.h)

| improve this answer | | | | |
  • Can we customize the eosio.token contract according to our requirement? – Nirdesh Kumar Choudhary Jan 18 '19 at 4:31
  • 1
    Why not? Customize as you want, and deploy it on your account. If you mean the contract deployed oneosio.tokenaccount, it’s not possible. Only the majority of block producers can have a permission to modify it. – conr2d Jan 22 '19 at 16:57
  • Yes it seems fine. – Nirdesh Kumar Choudhary Jan 23 '19 at 8:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.