-
Notifications
You must be signed in to change notification settings - Fork 83
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
Implementation of did:peer:2 DID method #883
Conversation
0cb1eae
to
2de180f
Compare
FYI @Jsyro . |
91dd534
to
71f3055
Compare
bc73803
to
bc5fa24
Compare
ac1d7dc
to
636d362
Compare
FYI — We just did a quick clarification to the DID Peer Spec. to clarify that the padding characters of the Base64URL encoding of the service item MUST have the padding characters removed. The padding characters (“=“) are not permitted in a DID, per the peer DID spec. |
4936275
to
3c9d5a8
Compare
Codecov Report
@@ Coverage Diff @@
## main #883 +/- ##
==========================================
- Coverage 49.90% 8.43% -41.47%
==========================================
Files 432 410 -22
Lines 35058 33546 -1512
Branches 7613 7218 -395
==========================================
- Hits 17496 2830 -14666
- Misses 12285 29915 +17630
+ Partials 5277 801 -4476
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
||
impl Key { | ||
pub fn new(key: Vec<u8>, key_type: SupportedKeyType) -> Result<Self, DidPeerError> { | ||
// If the key is a multibase key coming from a verification method, for some reason it is also |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo for myself: review this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a point of confusion for me as well, so it will be good to have another pair of eyes (with a brain attached) taking a look at it. 👍
Signed-off-by: Miroslav Kovar <miroslav.kovar@absa.africa>
Signed-off-by: Miroslav Kovar <miroslav.kovar@absa.africa>
Implementation of did:peer method 2:
The main non-functional requirement is maximal interoperability with the already existing implementations in other Aries frameworks.