Skip to content

Conversation

@Artemkaaas
Copy link
Contributor

Started work on splitting the Alice/Faber demo into smaller cases. Using this we can add demos for various optional modules.

  • Main - general demo of issuing credentials and presenting the proof
  • DidComm V2 - demo reflecting supported didcomm v2 protocols

@Artemkaaas Artemkaaas requested a review from a team May 26, 2023 08:42
@TimoGlastra
Copy link
Contributor

I think overall LGTM. I'm not sure though on splitting it up. What if we add an option to create a v1 or v2 invitation? And on the other side we just do receive invitation and it will accept both?

I think an agent should be able to run both at the same time, so I don't see a specific reason to split it up

@Artemkaaas
Copy link
Contributor Author

I think overall LGTM. I'm not sure though on splitting it up. What if we add an option to create a v1 or v2 invitation? And on the other side we just do receive invitation and it will accept both?

I think an agent should be able to run both at the same time, so I don't see a specific reason to split it up

What if we add an option to create a v1 or v2 invitation? And on the other side we just do receive invitation and it will accept both?

This is how it's currently done in hyperledger:feat/didcomm-v2.
I thought of splitting the main demo into independent cases so that we can create demos for conflicting cases such as: indy/askar wallets, indy/cheqd ledgers, cl/w3c credentials etc...

@TimoGlastra
Copy link
Contributor

Discussed on AFJ WG call. It's okay to split up the demo.

@TimoGlastra TimoGlastra added this to the 0.6 milestone Feb 14, 2024
@TimoGlastra TimoGlastra modified the milestones: 0.6, 0.7 Jun 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants