search

EOSIO / eosio.token

Reference contract for an EOSIO based token
MIT License
4 stars 7 forks source link

make eosio.token inheritable #12

Open cc32d9 opened 6 years ago

cc32d9 commented 6 years ago

It should be possible to inherit from eosio.token class, so that new tokens would not have to just copy the token source code.

So, all flesh should be moved to a token.hpp inside eosiolib, and eosio.token.cpp should only have EOSIO_ABI call.

prcolaco commented 4 years ago

Any news about this issue? I think that having base contracts like eosio.token inheritable is very important as the platform grows, making all the contracts code extendable without copy pasting stuff around. Also is there a way to make the abi generator to properly generate abi including base contract actions, tables, etc... from what I tried it generates only abi for the current contract, ignoring the base contracts it extends.

crazybits commented 4 years ago

any progress on this? i tried to extend from exiting contract, and add the base class actions into the abi file, seems not work, when call the base class action , following error prompted

assertion failure with error code: 8000000000000000000

deckb commented 3 years ago

Transferring this issue to the new reference token contract repo.

mschoenebeck commented 3 years ago

Agree. The token contract should be inheritable. Any progress on this? I would like to extend the base functionality for shielded transactions using zk-snarks and make it available for everyone. Inheritance of the base eosio.token contract would be the most elegant solution to this.