Patrick St-Louis

@dbluhm thanks for doing this work. @aritroCoder does this cover your use case?

Something I'd like to clarify - `3FfZB8jq8kch5qddakysA2` is not a DID - `did:sov:3FfZB8jq8kch5qddakysA2` is a DID The same way that: - `www.linkedin.com` is not a DID - `did:web:www.linkedin.com` is a...

This makes sense yes, so theres 2 things I could see happening: - Define a new did registration method for indy: - We are currently in the process of restructuring...

Here's the git blame history: https://github.com/openwallet-foundation/acapy/blame/6173d9c9ea0b36e686504547c587080894186b42/acapy_agent/multitenant/base.py#L309 It seems to be related to managed / unmanaged wallets. I would propose to review this feature and perhaps consider removing it.

There is mention of this in the multitenancy documentation: http://github.com/openwallet-foundation/acapy/blob/main/docs/features/Multitenancy.md#method-2-get-tenant-token It also says that this was temporary, 4 years ago. It might be time to review the authentication for multitenancy...

Thanks for having another pair of eyes on this. It seems like it boils down to the unmanaged wallet mode, which is partially implemented and not useable according to the...

For a present-proof attachment, you need to first create a present-proof exchange using the `/present-proof-2.0/create-request` endpoint, then capture the exchange id of the response and include this as the `id`...

I did some digging around, here what is happening: When the OOB invitation is created with a handshake, it creates a connection and metadata records: https://github.com/openwallet-foundation/acapy/blob/ce8dac422b5ffbf6c5925afc2068e0eeb8c3753a/acapy_agent/protocols/out_of_band/v1_0/manager.py#L322 When the holder receives...

For the connectionless, you can try creating the OOB invitation **without** the `handshake` parameter. If I remember correctly this is how I did it in the past. Is your holder...

The reason I was asking how your agents are setup is that if its all in the same agent, it can be difficult to know who is raising the error...