Daniel Bluhm

I recently adjusted the behavior of the credential subject ID override in #2341. If the issuer knows the appropriate ID to use for the holder, it can set the ID...

This PR has been overcome by events. In the future, we expect proof negotiation to move to a companion protocol. If you're interested in proof negotiation, please feel free to...

Good points; I actually deliberately swapped things over from running in a container at least partially for faster run times but that would be far less important for nightly testing...

To further clarify my thoughts, I would recommend moving the plugin code out of the ACA-Py repo. This would mean that there would be a little more than just a...

Yes, indeed, I agree that the right place for this would probably be a plugin**s** (plural) repo. This would serve as a destination for other future deprecated protocols, too, in...

@jamshale @ianco merged in main and resolved conflicts in the poetry lock. This will need a fresh review but then should be ready to merge. Thanks!

Good question. I think there is value in the concept of an "agent in a box," to borrow a term @TelegramSam has used in the past. Having something that is...

I haven't glanced at the specifics just yet but I assume it would be accurate to say that replacing this library with an actively maintained alternative is infeasible?

ACA-Py is following the `did-communication` convention right now. This convention is defined here: https://github.com/hyperledger/aries-rfcs/blob/main/features/0067-didcomm-diddoc-conventions/README.md#service-conventions ACA-Py is correctly adhering to this convention and has not yet adopted the DIDCommMessaging service type....

@ff137 I think this should be ready for review now; would you be able to regenerate the lock file?