AEX-2: How wallet can determine that it was talking to some aepp before? about aexs HOT 5 CLOSED

currently out of scope for this AEX. best would be to create a separate aex for this functionality

from aexs.

I think we should mention in AEX-2 that developers shouldn't rely on them as persistent and additional identification is needed for that.

from aexs.

noted. but it is up to the developers how they want to use it. if they want it to be persistent and use them throughout they can very well choose too. the AEX proposal uses id to uniquely identify the sender and receiver of messages. The AEX2,5 do not deal with best practices and it is up to the community to decide.

from aexs.

if they want it to be persistent and use them throughout they can very well choose too

wallet.request.connect: connection request sent by the wallet containing an identifier that it wants to assign to the aepp/sdk

Don't it means that wallet should send a random identifier every time? Or you mean that wallet can somehow identify aepp by itself and then send the existing identifier? Do we need identifiers in AEX-2 if wallet can identify aepp by itself?

The AEX2,5 do not deal with best practices and it is up to the community to decide.

Are you sure about the necessity of identifiers in AEX-2? If not why don't introduce them later?

from aexs.

So, this determination is not a part of AEX-2, I suppose that for this purpose should be used the domain of URL / postMessage origin or some other transport depending identifier.

from aexs.