Replies: 1 comment
-
If delegation is not allowed for a QVI AID within the vLEI ecosystem, is the following approach allowed for a QVI?
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Recording:
https://us06web.zoom.us/rec/share/9RtKAuTNe1417D-4tgdLzmdsrRz63EuaBOysMQU4EZ0ysw4aaZXsIXo1tIRNdzyC.FJhPr84fMxOsGoQN
Passcode: Z0JP84J+
keria
PR #67 - some test in credentialing failing
PR #78 - needs review
Delegated Multisig with Tholder impl
For codecov:
signifypy
Delegated Multisig with Tholder impl
Minor fixes from PR
PR #45 - Draft
signify-ts
Typescript clean up
Revocation PR
Delegated Multisig with Tholder impl
keripy
Delegated Multisig with Tholder impl
cesride
no major update
parside
PR coming from Jason with new examples
Questions
vLEI Ecosystem - QVI Delegation, Multiple QVI credentials.
Sending the path in sig headers(?)
Path used to solve credentials within credentials for partial signing, path (SAD path language) is to the portion they signed.
Also, used for forwarding in KERI embedded messages - see video discussion.
We don't sign our credentials, you shouldn't either!
How are we going to migrate KELs moving forward?
We'll work on a migration tool, it is TBD right now, but we acknowledge the need.
Demo
Delegated Multisig - Starts around 28 minutes.
Beta Was this translation helpful? Give feedback.
All reactions