As discussed with @pepyakin before my DappDev talk, some items were named misleadingly in our tutorial; TokenContract is actually TokenInterface, since it specifies the ERC20 interface (and nothing more); TokenContractInstance should be renamed into TokenContract, since it's where the actual contract code is (and it's not an instance, just a prototype for possible multiple instances on-chain).
I've also found some errors filepaths to the generated wasm artifacts, and optimized the rs files location (to closer follow the conventional layout expected by Cargo).
lexfrl
commented
6 years ago
As discussed with @pepyakin before my DappDev talk, some items were named misleadingly in our tutorial;
TokenContractis actuallyTokenInterface, since it specifies the ERC20 interface (and nothing more);TokenContractInstanceshould be renamed intoTokenContract, since it's where the actual contract code is (and it's not an instance, just a prototype for possible multiple instances on-chain).I've also found some errors filepaths to the generated wasm artifacts, and optimized the rs files location (to closer follow the conventional layout expected by Cargo).