Following #33, #34, and #35 we should consider the possibility of using the wallet:distro:sys module for provider registration as well, meaning that the provider sub-entries would be held in the user TBA rather than in an external wallet.
This would move the set of transactions established in #34 from interactions with an external wallet to an "under the hood" process enabled by the access list hot wallet paradigm. Ideally, this would use the same gas abstraction solution, enabling user USDC to serve as a kind of universal balance for both sending Hypergrid micropayments and minting providers.
This may not be implementable until work that is decidedly out of scope for #33 is completed, giving the wallet system process a more universal and adaptable interface.
Following #33, #34, and #35 we should consider the possibility of using the
wallet:distro:sysmodule for provider registration as well, meaning that the provider sub-entries would be held in the user TBA rather than in an external wallet.This would move the set of transactions established in #34 from interactions with an external wallet to an "under the hood" process enabled by the access list hot wallet paradigm. Ideally, this would use the same gas abstraction solution, enabling user USDC to serve as a kind of universal balance for both sending Hypergrid micropayments and minting providers.
This may not be implementable until work that is decidedly out of scope for #33 is completed, giving the wallet system process a more universal and adaptable interface.