-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat: 🎸 Add verifier for w3c-did identityProof #80
base: master
Are you sure you want to change the base?
Conversation
AdamJLemmon
commented
Jan 9, 2020
- Support for universal resolver for broad did resolution.
- Initial did-auth support for ethr did-method utilizing comparison against tx.origin of document issuance tx.
Support for universal resolver for broad did resolution. Initial did-auth support for ethr did-method utilizing comparison against tx.origin of document issuance tx.
smartContract: string; | ||
} | ||
|
||
export interface DIDDocument { |
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.
I think you can use some of the types/methods from here https://github.com/decentralized-identity/did-common-typescript/blob/master/lib/IDidDocument.ts
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.
I actually pulled direct from the did-resolver here: https://github.com/decentralized-identity/did-resolver/blob/02bdaf1687151bb934b10093042e576ed54b229c/src/resolver.ts#L15
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.
would it make sense to then install it as a dependency and use the exported types?
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.
That feels like a good solution. Then also as types inevitably evolve we can just bump version of the package instead of having to replicate changes manually... I like it.
status: "SKIPPED", | ||
type, | ||
name, | ||
message: `Document issuer doesn't doesn't use ${v3.IdentityProofType.W3CDid} type` |
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.
doesn't doesnt :p
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.
👍
"@govtechsg/open-attestation": "3.1.0", | ||
"@types/request-promise-native": "^1.0.17", | ||
"ethers": "^4.0.40", | ||
"request-promise-native": "^1.0.8" |
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.
we usually use axios with async/await