1

I am trying to make a transaction on eos. I have a node running on docker and created an account with cleos.

I tried following this: https://github.com/EOSBlock/EOS-Tutorials/blob/master/EN/transfer-tokens-using-RPC.md

But it gives me this when creating the contract:

no wasm file found /opt/eosio/bin/data-dir/contracts/eosio.token/eosio.token.wasm

I also tried some python libraries, but the problem there was that the contract eosio.token is missing, so I guess it's in the end the same problem as above.

Generally I am also confused why the eosio.token is not already existing in the testnet. In my understanding it is not a private testnet then why isn't the eosio account and contract already there?

Improve this question
8
  • 1
    why do you think you're not a private testnet? did you provide your nodeos with the genesis.json for the public testnet you wanted to connect to?
    – confused00
    Oct 24, 2018 at 9:54
  • I followed more or less this developers.eos.io/eosio-nodeos/docs/docker-quickstart. It doesn't explicitly say it but I assumed its not private as there are already a lot of blocks present
    – solaire
    Oct 24, 2018 at 10:12
  • 1
    ah, that article guides you to start your own chain from scratch; it's not connecting to a public chain. you'd need to push the eosio.* contracts to enable the various functionalities
    – confused00
    Oct 24, 2018 at 10:17
  • ok, makes sense. so if the node is running it just produces empty blocks even though there are no transactions or anything going on?
    – solaire
    Oct 24, 2018 at 10:24
  • yeah that's right
    – confused00
    Oct 24, 2018 at 11:46

0

Reset to default

Your Answer

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

Browse other questions tagged or ask your own question.