conanoc

The comment on line 1 is no longer necessary. You can remove it.

The DCO check can be handled in this PR. There's a guide on how to do it on the "Details" page.

```swift func findConnectionByMessageThreadId(message: AgentMessage) async throws -> ConnectionRecord? { let threadId = message.threadId guard let oobRecord = try await agent.outOfBandService.findByAttachmentThreadId(threadId) else { return nil } guard let invitationKey = try...

We are assigning the pthid to all outbound messages in MessageSender: https://github.com/hyperledger/aries-framework-swift/blob/main/Sources/AriesFramework/agent/MessageSender.swift#L48 I guess the pthid of the messages(credential-request or presentation message) should be already the same as the oob...

Good job. The strange lint errors are gone now. I don't know what happened to swiftlint. It seems like the only thing left to do is implement the `testConnectionlessProofExchange()` function.

Looks good. Thanks.

@andrewwhitehead Do you have any idea about this issue? I have no idea why the proof created by anoncreds-rs ommits `m2`.

Because m2 is not optional in `NonRevocProofXList` of ursa, the proof json could not be parsed in indy-sdk. https://github.com/hyperledger-archives/ursa/blob/main/libursa/src/cl/mod.rs#L1173

I see. `revocation status list` is a new thing introduced by Anoncreds. Indy-sdk creates `revocation state` from `revocation registry delta` which can be retrieved from the indy ledger, while Anoncreds...

I found this spec by searching this repo. https://github.com/hyperledger/anoncreds-spec/issues/108 I think there should be some guide on how to create `revocation status list` from `revocation registry delta` because indy-vdr does...