-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable did:peer:4 in deployments #1048
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Examples of calling OOB/create-invitation with
|
Note Tenant UI create invitation screen specifies nothing for the use_did_method. Could add option boxes for the did:peer ones to test different usages easily. I'm not sure what all consuming Traction tenants are using for their invitations? Likely just not specifying? |
@jamshale FYI since we have been chatting about this elsewhere. @swcurran do you have any thoughts/input? Based on what we are currently using and how it is unclear why/how the resulting payloads are different when creating didexchange transactions, I am leaning towards closing this as |
I believe all you'd need to do is change the handshake protocol from |
Enable usage of did:peer:4 in Traction deployments
dev
test
prod
The text was updated successfully, but these errors were encountered: