Daniel Bluhm

@swcurran the connection protocol doesn't make any specific recommendations on DIDDoc format, deliberately omitting those details, so there's nothing to align with 67.

My recommendation would be to make the more forward thinking `did-communication` be the expected service type and service identifier suffix and note that agents seeking to be backwards compatible can...

Maybe... I have issues with something that was never explicitly Aries RFC Standard being suddenly introduced as standard, especially when other relevant RFCs at least indicate a different convention, if...

@swcurran Yes, that helps. Thanks for taking the time to do that. I do hope we can quickly change to a more appropriate service type in the near future.

I also noticed that today. RFC 67 shows `#did-communication` whereas RFC 94 shows `;did-communication`. I also agree that the ID could be anything and shouldn't be forced to have an...

> There are conflicts between this PR and PR #1955 It does indeed; we have a patch handy to cleanly merge the two after one or the other is merged...

This PR doesn't yet address multi-tenancy with a mediator connected to the base wallet. I'll mark this as a draft as I work on that.

See #1864 for some prior discussion on a similar change.

If you haven't pulled changes from your remote branch and just have your original commit locally still, you can run: ```sh git commit --amend -s git push -f ``` If...

So I think some of the same concerns raised in #1864 apply here. Namely, by permitting `credentialStatus`, there might be some implication that ACA-Py will verify the `credentialStatus` when in...