Skip to content
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.

make eosio.token inheritable #12

Open
cc32d9 opened this issue Aug 9, 2018 · 4 comments
Open

make eosio.token inheritable #12

cc32d9 opened this issue Aug 9, 2018 · 4 comments

Comments

@cc32d9
Copy link

cc32d9 commented Aug 9, 2018

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
Copy link

prcolaco commented Feb 6, 2020

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
Copy link

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 deckb transferred this issue from EOSIO/eosio.contracts Apr 21, 2021
@deckb
Copy link
Contributor

deckb commented Apr 21, 2021

Transferring this issue to the new reference token contract repo.

@mschoenebeck
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants