AEX-2: In which case may be needed to update network from aepp? about aexs HOT 7 CLOSED

Will be added to the rationale section and then let's discuss it in the forums.

from aexs.

@shekhar-shubhendu how #57 resolves this issue?

from aexs.

as you can see this method has been removed from the aex-2 and we've added a notification for the wallet and app to inform the other party about change in network so that they can handle the requests appropriately.

wallet/app can inform other party about the network change but they can not enforce or trigger a network change.

from aexs.

Have you updated the rationale section as you promised in the message above? Is there any practical use cases when aepp need to inform wallet about network id? Isn't enough that network id is a part of the transaction that aepp sends to a wallet for signing?

from aexs.

Let's assume the wallet wants to maintain a list of aepps it is/has connected to then it would be a nice feature for the wallet to show this detail there. this was the user can just open the wallet and see which aepp is on which network without going to check this on the aepp side.
if this info is part of the sign request then wallet can only say what was the network id of the last signed tx.

from aexs.

What if aepps resets network id to mainnet by default? Then the user will assume that aepp uses testnet but after opening it will appear to be connected to mainnet. It makes "without going to check this on the aepp side" a bad strategy.

#56 proposes to store supported networks in app metadata, it is better because wallet shouldn't open aepp to know it's network id.

from aexs.

@davidyuk as suggested, this functionality will be removed

from aexs.