Yes, you can. Names are not unique. They are a way for you to identify your identity.
Unfortunately, you can’t link identities. If you created one before you were able to upgrade your old, now you need to decide either keep using the new one you created in 2.0 or start using the upgraded one.
Your question was answered in another thread.
I may not have been clear with my question. Let me try again. If I created an II2.0 named “John” to test id.ai when it first came out, how do I migrate my II1.0 to II2.0 and call it “John”? I don’t care about the test version of “John”, but I can’t figure out how to delete it. I simply want my real II that I’ve been using forever to be called “John”. Is there a way to make that happen?
Even if I decide to call the migrated II1.0 “John2”, which would be kind of irritating to look at forever since it can’t be changed, I still wouldn’t want to also have to look at the test “John” in my list of identities because I would never use it.
Hopefully the answer is not that I have to clear cache and remove all identities. That’s not a very user friendly option.
2 Likes
You can clear the page data for the id.ai domain in your browser to empty the list with recently used identities. Then when you’ve authenticated with either the new or old identity, it will show up in the list again.
We’re aware that this is not the ideal way to clear the list, it’s on our future improvements list to look into this e.g. show a “forget” option.
On a related note, you will have two passkeys with the same name on your credential manager unless you rename/delete one.
2 Likes
What?? …what ”ii 1.0 information to put in” … Clicking on the upgrade from legacy button results in information that the process has completed… and that’s it. Where and when did you enter anything?
( Am I misunderstanding something? )
Thanks for the suggestion. I wouldn’t have realized this step is needed.
It is strongly recommended to adopt the current mnemonic phrase mode of ii 1.0, that is, the mode of number + phrase. There are the following benefits:
- It is convenient for current 1.0 users to still use the current storage mode. Even if they do not upgrade to 2.0, they can still restore their accounts through the number plus phrase mode they have stored many years later, achieving seamless connection.
- It is a secure storage method. For example, if I have a five-digit ii now, when I store the mnemonic words, I will delete the number. No one will know which account’s mnemonic words these are, and I just need to remember this number.
- I remember someone said before that any registered ii will have an anchor, but the 2.0 mode will hide it (it actually still exists). Therefore, any account that can use this number plus phrase mode is the most compatible with the ii 1.0 mode.
2 Likes
I tried three times, but the upgrade still failed, so I have given up.
Could you share any more details like error messages that you’ve ran into?
As mentioned earlier in the thread, existing 1.0 seed phrases will remain usable, even in II 2.0. Any future new generated seed phrases will likely be without the identity number component (design pending).
Do not do this, that is not a secure storage method
Given knowing only a 5 digit II. It would be trivial to iterate over ALL of them given a known seed phrase.
Thanks for reminding, of course i will keep the phrase safely, thx
Thanks for reply, i will always use the 5 digit number + phrase to keep my account.
My passkey is stored on my phone and on the ledger. I can log in to the id.ai via my phone, but I can't via the ledger.
And you don’t get any error back?
What device, and browser are you using?
Yes, that’s correct. id.ai uses discoverable passkeys, which is a new standard not supported by ledger devices.
The picture contains my device model.It’s just stuck at this step all the time, with no error messages.
The browser being used is Edge.