New answers tagged eosio-code
0
If a contract has an inline action, the permission for running that action must be eosio.code from that contract account.
Thats it.
Example:
accounta is a smart contract with an inline action to accountb. Therefore accounta will need the permission accounta@eosio.code, as the contract will need to execute the inline action.
0
The problem is your inline action, you are trying to transfer the funds onto the to account, but you are trying to do this with the permission of the from account, but it should be with the permission of self.
So change your inline action to say:
action
{
permission_level{get_self(), "active"_n},
"eosio.token"_n,
"transfer"_n,
std::...
0
this tutorial written by EOS developer. https://medium.com/@kaloliya/step-by-step-guide-to-set-up-your-private-eos-network-eosio-6d80c30dd520
1
Contract console out in nodeos log is debug level, but default logging level of nodeos is changed from debug to info. If you want to print console out, put next logging.json in your config directory.
{
"includes": [],
"appenders": [{
"name": "stderr",
"type": "console",
"args": {
"stream": "std_error",
"level_colors": [{...
0
eosio.code permission on your account will give access to target account from contract-code, which eosio.code permission you use.
For example, if account Bob will set contractA@eosio.code on their active permission slot, contractA will get active permissions from the code to Bob's account.
0
Not sure why this happens, but I've also been struggling with it.
I get around it by doing
eosio::print("hello!");
eosio::check(false, "uh oh");
So when I do cleos push action ... it then errors out the transaction, but prints "hello!" in the console.
Would also love to know a better way to print, but for now maybe this could help!
Top 50 recent answers are included
