Ian Costanzo

I'm going to put in a check - if the test requires an `askar-anoncreds` wallet and the agent isn't running an `askar-anoncreds` wallet then the test will fail. For now...

> Sorry — I junped the gun on this one. I also should have waited until the connections plugin was in place. I think there will be some falling out...

I think some tests use an in-memory wallet (where a wallet is needed) however if so they should be able to use sqlite, so I agree let's get rid of...

It could be related to a cange to using the `2.0` protocol, I didn't really dig into it too much ...

Credential verification is working in production OrgBook but not locally. Upon inspection the self-connection isn't getting created on startup (the OrgBook agent makes a connection to itself in order to...

Closing as we're not planning to fix this issue. If a new instance is setup the self-connection (required for credential verification) has to be setup manually.

Sounds like it's a change in behaviour of aca-py, so we should probably fix it, but we should verify that we're following best practices: https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0441-present-proof-best-practices/README.md

> There is an example implementation in my repo This comparison highlights the code changes required: https://github.com/ianco/owl-agent-test-harness/compare/owl-tutorial...ianco:owl-agent-test-harness:owl-tutorial-impl?expand=1

@swcurran yes that all makes sense. (Another improvement required to the document is to make sure the revocation scenario actually works :-P)

> @ianco — fodder for your plugins design? Yes all very good info