ERC-3643 : the T-REX token standard

ERCs
,
15

@Joachim-Lebrun, what are your thoughts on narrowing the token interface in a different ERC, to allow for simpler implementations?

In very rough terms, identity registry and onchainID could be embedded in the compliance module, and TIR, and CTR could be implemented on top of forced transfers.

On the other hand, I find token permissioning functions very strong and accurate, leading me to believe it would make sense to propose a backwards compatible ERC with a narrower scope that enables minimal T-REX-like deployments:

  • Token interface:
    • Pausable (pause, unpause, isPaused).
    • Address freezing (setAddressFrozen, isFrozen).
    • Partial token freezing (freezePartialTokens, unfreezePartialTokens, getFrozenTokens).
    • Forced transfers (forcedTransfer).
    • Minting and burning (mint, burn).
    • Agnostic to ownership, versioning, token holder identity, and claims.
    • Additional transfer rules through compliance (compliance).
  • Compliance interface:
    • Exposes unique check (canTransfer).
    • Modular.
    • No token binding.
    • Optional stateful hooks (transferred, created, destroyed).

Congrats on your job so far!

1 Like