Summary:
Accounts in Jade signer are keyed currently from the chainID. This is fine when you aren't switching chains. However, as we move forward towards L2 scaling solutions, we hit problems supporting cross chain requests.
Motivation:
ChainID is the prefix for all account actions, when account addresses should be chain agnostic.
Acceptance Criteria:
Jade Signer stores account address information not keyed by chainID
Summary: Accounts in Jade signer are keyed currently from the chainID. This is fine when you aren't switching chains. However, as we move forward towards L2 scaling solutions, we hit problems supporting cross chain requests.
Motivation: ChainID is the prefix for all account actions, when account addresses should be chain agnostic.
Acceptance Criteria: Jade Signer stores account address information not keyed by chainID