Hi @kimamila thanks indeed for your comments as usual. I’ll try to take all into account.
About the last one, G1nkgo does not stores the protected accounts private key (only in memory). In this case, the user has to enter the passwords on each session on demand.
I maintain in memory the cesium wallets info here (that are requested when paying, for instance):
The way I detect if is a protected card or not is looking if I had persisted the seed (not in the case of Cesium accounts):
I trying not to compromise the current security of the cesium accounts (and this was one of the reason to not adding this before).
Again, merci! Anyway the new cesium version works great!