Determine if its possible to remove the chain_id from the Session options
aaroncox opened this issue · comments
Removing the chain_id would simplify the configuration for a Session. It would only be an API endpoint. The chain_id could be retrieved during the get_info call at the same time the tapos parameters are generated.
The chain_id will likely still be required for the SessionKit, since the chain_id itself is used to dictate which accounts are valid for a wallet to use in order to login to an application.
I think we've simplified it even more by using the common library and the Chains definitions.