Cleos asks for authority in transaction, but authority is in transaction

Question

Edit:

Bounty will be opened in 10hrs from writing (can't do it earlier). This question has been edited to meet the depth necessary to trouble-shoot an issue. The bounty will be issued as soon as the push/issue action is completed on my end. It may be necessary to re-deploy the contract, which also gave me additional errors.

Trying to re-deploy the contract gives Assert Exception (10)

Here is a list of actions that were done (I apologize if I skipped a step, doing it from a memory). Account names and keys are altered on purpose. I have managed to create a token, the last thing I need to do is to publish it. BP that I randomly chose is eosnewyork.io.

cleos version client

Build version: c9b7a247

Lets assume that these are my registered EOS keys:

Private key: 5KX2Bsns7hKNQ6YhA85xB1NQ5YzAbZMyGQM9M829TvDDBPAWHKC

Public key: EOS7bshTD31XdsY9ju7K9kdtHGQNjziPff8ANp5DGagA8CoFtbPoG

Mnemonic address: gywaofjugage

cleos wallet import 5KX2Bsns7hKNQ6YhA85xB1NQ5YzAbZMyGQM9M829TvDDBPAWHKC -n gywaofjugage

-imported private key for: EOS7bshTD31XdsY9ju7K9kdtHGQNjziPff8ANp5DGagA8CoFtbPoG

cleos wallet list

Wallets: [ "gywaofjugage *" ]

cleos wallet keys

[ "EOS7bshTD31XdsY9ju7K9kdtHGQNjziPff8ANp5DGagA8CoFtbPoG" ]

-Went to https://github.com/EOSIO/eos and downloaded the whole project as a ZIP file. Extracted, and continued with these commands:

eosiocpp -o /home/user/Downloads/eos-master/contracts/eosio.token/eosio.token.wast /home/user/Downloads/eos-master/contracts/eosio.token/eosio.token.cpp

Then, I have deployed the contract. I believe I might have make a mistake with "issuer" (wrote someting else, this is just for example) and that I was supposed to write my wallet name instead.

cleos -u http://api.eosnewyork.io push action gywaofjugage create '[ "issuer", "1000000000.0000 TOKEN", 0, 0, 0]' -p gywaofjugage

executed transaction: aabaf2b00e95ec571001dd27d898788358c4a3c9b41234671591f382115ff0b1 120 bytes 581 us # gywaofjugage <= gywaofjugage::create {"issuer":"issuer","maximum_supply":"1000000000.0000 TOKEN"}

Now, I am trying to issue the token to myself first by using this command:

cleos -u http://api.eosnewyork.io push action gywaofjugage issue '["gywaofjugage", "1.0000 TOKEN", "memo"]' -p gywaofjugage@active

Error 3090004: missing required authority Ensure that you have the related authority inside your transaction!; If you are currently using 'cleos push action' command, try to add the relevant authority using -p option.

Answer 1

In command

cleos -u http://api.eosnewyork.io push action gywaofjugage create '[ "issuer", "1000000000.0000 TOKEN", 0, 0, 0]' -p gywaofjugage

Can you confirm that "issuer" was actually "gywaofjugage" then?

Only the account name specified in place of issuer has authority to mint tokens.

Answer 2

You seem to be using -p gywaofjugage as the -p option. Try using -p gywaofjugage@active instead?

The -p option is described as "An account and permission level to authorize, as in 'account@permission'" in https://developers.eos.io/eosio-cleos/reference#cleos-push-action

Answer 3

Change it as follows.

cleos -u http://api.eosnewyork.io push action gywaofjugage issue '["issuer", "1.0000 TOKEN", "memo"]' -p issuer

I will arrange what you have done step by step.

In the first step above, the create action from the eosio.token contract, authorized by the gywaofjugage account, creates 1000000000.0000 TOKEN tokens in the issuer.

In the second step, the eosio.token contract's issue action takes 1000000000.0000 TOKEN tokens out of reserve and puts them into circulation. At the time of issue, the tokens are held within the issuer account. Since the issuer account owns the reserve of uncirculated tokens, its authority is required to do the action.

The following links provide more information.

https://developers.eos.io/eosio-nodeos/docs/bios-boot-sequence