Include "facade" interface for HTS fungible and non-fungible tokens

[acuarica]

Problem

Currently, we provide an interface for all supported methods behind 0x167, the IHederaTokenService interface.

The tokens (both fungible and non-fungible) also support methods to be called on themselves, that is, IERC20 and IERC721 respectively. In addition, both kind of tokens support association methods defined by IHRC719. However, there is no "facade" interface that contains "all" these methods combined.

Solution

Add two new interfaces IHtsFungibleToken and IHtsNonFungibleToken that would allow the user to call all methods behind a fungible and non-fungible token respectively.

interface IHtsFungibleToken is IERC20, IHRC719 {}
interface IHtsNonFungibleToken is IERC721, IHRC719 {}

Alternatives

No response

[david-bakin-sl]

Consider facade interface for HAS as well?

[acuarica]

We should, yes.

[Nana-EC]

Working on this, making progress on an E2E IHtsFungibleToken version.
However, in implementation I've found that implementing IHRC719 may not be a base case scenario.
For a contract to associate or dissociate it would require the contract to be listed on another accounts admin key.
IHRC719 is mostly intended for contracts to execute on themselves or for EOAs to call as a facade