1

Notification is delivered by require_recipient. eosio.token::transfer calls require_recipient for from (sender of token) and to (recipient of token) account. As @towi_parallelism mentioned, only sender and recipient can get notification. https://github.com/EOSIO/eosio.contracts/blob/d7bc0a5c/contracts/eosio.token/src/eosio.token.cpp#L89-L90


1

It seems that the contract containing the on_notify attribute should be either the sender or reciever of the transfer. This is not clearly mentioned in the manual


1

It is hard to say for sure what the problem is without seeing the error message. It looks like you are trying to transfer money from the from account to the to account with the permission of eosuperadmin@eosio.code, which isn't possible because the transfer function of eosuperadmin requires the authorization of from. You can bypass this in two ways: Change ...


1

eosio::symbol consists of decimals,symbol_code like 4,EOS.


1

This error message means you do not have the correct permissions to run the command as the account eosio. You need to make sure that the private key for the eosio account is in your wallet. You can do that using the command: cleos wallet import After you have the private key in your wallet, you can check that it matches the public key that you have on record ...


1

You can use get_first_receiver() to get the name of the contract from where the notification comes.


1

Imagine the blockchain as a tamper resistant database. You interact with it per transactions that are signed and the log is signed as well. The method of hashing hashes (blocks) and chaining them is used for making it resistant to manipulation. In a traditional system an attacker would be able manipulate the database and the transaction log more or less ...


1

You can't create a token using the eosio.token-account because you would need the authentication of the contract to do so. void token::create( const name& issuer, const asset& maximum_supply ) { require_auth( get_self() ); ... } Therefore, you have you to deploy your own token-contract.


Only top voted, non community-wiki answers of a minimum length are eligible