There is an esoio.token contract. This contract be used for issuing and storing many tokens starting with EOS.

However, is it possible to issue tokens without using the eosio.token contract?

What is the best way to issue tokens - to use the eosio.token contract, or to copy the eosio.token contract under new name and issue there?

2 Answers 2


The first line of token::create is require_auth( _self );. So I think only the contract account eosio.token can create the tokens. What you can always do is to reutilize this contract in an account that belongs to you:

cleos set contract your.account $EOSPATH/build/contracts/eosio.token

So you have control of all the features and can create all the tokens you need. Now I'm just curious if we have a way to have permission to create tokens using the eosio.token account...


You can view the eosdactoken contract here - https://github.com/eosdac/eosdactoken

We've implemented some extra functions for membership which will tie into our forthcoming DAC voting and worker proposal contracts.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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