Consumer chain fee token must be PHOTON

[tbruyelle]

As per the Constitution, the core shards fee token must be PHOTON. For now we do not distinct core vs consumer shards, so let's consider that the current implemention refers to the core shards.

This requires all users to transfer PHOTON from AtomOne be able to submit tx on a consumer chain. I don't know what to think about it but that looks very suboptimal. Let me know what you think, maybe there's other paths.

[giuliostramondo]

I went back and checked the constitution.
The requirement you mention only applies to Core Shards ( ICS-secured chains that function as an extension of functionality of the AtomOne Hub, these consumer chains are completely controlled by the AtomOne Hub. ). Not to Consumer Shards ( ICS-secured chains that retain full sovereignty due to their own governance and they are in a client relationship with AtomOne Hub ).

IMHO, the general case we target in VAAS are Consumer Shards not Core Shards, for consumer shards there is not such a requirement...

[tbruyelle]

Question of point of view, on my side I was more aligned with "Core Shards" being the general case of Vaas.

https://github.com/atomone-hub/genesis/blob/main/CONSTITUTION.md#section-5-the-photon-token

The PHOTON shall be the only fee token except for ATONE to PHOTON burn transactions. This applies for all transactions on the root and core shards, and all IBC and ICS payments.

We still need to enforce PHOTON for IBC transactions fees anyway.

[Pantani]

Requiring PHOTON as the only fee token on consumer shards creates significant UX friction, since every new user must first buy PHOTON before submitting even their first tx