consider pre-deployed approach

[harrysolovay]

Users could create new fungible tokens via a permissionless method of an already-deployed contract (instead of deploying their own).

Can draw inspiration from the Polkadot FRAME system's assets pallet.

[harrysolovay]

It seems this approach would also simplify wallet implementations, which wouldn't need to depend on / dynamically import contract code, which may or may not actually be published (and how would this lookup occur anyways? Archive node data?).

I don't believe this approach would utilize TokenContract nor native custom tokens. Is this a concern? Any critical functionality we'd be missing? We'll also want to provide an approach to persistence, which seems simpler without native custom tokens (?).

I'm not yet familiar with many of these constraints, so there's a lots to flesh out. @kantp, can you please add any detail that may be relevant / concerns?

Will follow up with a FungibleTokens interface soon.