You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 18, 2026. It is now read-only.
In plcSetupLabeler, com.atproto.identity.getRecommendedDidCredentials is called as part of creating an operation to submit to did:plc, however, that method doesn't actually return the current state of the did document, just the data that the PDS knows about, so if you had additional services or verificationMethods in your did document, then there's a chance that plcSetupLabeler would remove those verification methods & services from your did document.
I suspect we may actually want to fetch both the recommend did credentials, and the did document itself, and then merge in order of new labeler data, did document data, recommended credentials data.
This would prevent setting up a labeler from interfering with anything else that happens to already be on the did document.
In
plcSetupLabeler,com.atproto.identity.getRecommendedDidCredentialsis called as part of creating an operation to submit to did:plc, however, that method doesn't actually return the current state of the did document, just the data that the PDS knows about, so if you had additional services or verificationMethods in your did document, then there's a chance thatplcSetupLabelerwould remove those verification methods & services from your did document.I suspect we may actually want to fetch both the recommend did credentials, and the did document itself, and then merge in order of new labeler data, did document data, recommended credentials data.
This would prevent setting up a labeler from interfering with anything else that happens to already be on the did document.