ThreeIdProvider creates a new DID when the same seed is provided

[carlfairclough]

I am currently trying to allow users to usedid:3 without using the 3id-connect modals, however while integrating I found that every time the same seed was provided, a new DID was created.

To investigate, I set up a demo project which only generates a DID from seed, and confirmed the behaviour.

Code providing seed to ThreeIdProvider: https://github.com/carlfairclough/ceramic-3id-demo/blob/758b67eb0ce121c1534e9bb9def11d0626493f21/src/utils/connect.ts#L20C1-L24C6

Demo: https://ceramic-demo-eosin.vercel.app/

[oed]

Use of 3ID is no longer recommend. Instead use DID PKH using did-session: https://did.js.org/docs/authorization

[carlfairclough]

Kindly requesting

• a recommendation on how to reliably allow users to access and manage their existing data without the 3id-connect modal
• to clearly deprecate abandoned functionality
• To update your own documentation to avoid others pursuing this.

[oed]

Hey @carlfairclough, excuse the delayed response.

1. If the question is how to migrate data from did:3 to did:pkh, the best way is probably to:
   a. Find the did:3 and read the data
   b. Write the data to a new stream that the did:pkh controlls
2. (and 3), yes we are planning to do this.

[mzkrasner]

Hello @carlfairclough - happy to help if you still need it. Feel free to contact me directly - mzk@3box.io