-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add Initial SIWE support to taco-auth
for Demo
#526
Add Initial SIWE support to taco-auth
for Demo
#526
Conversation
✅ Deploy Preview for taco-nft-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for taco-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
taco-auth
taco-auth
e2d658f
to
527f9d6
Compare
Co-authored-by: Piotr Roslaniec <p.roslaniec@gmail.com>
Modify some default values used for creating SIWE message, including use a random nonce.
…used tests to fail. Co-authored-by: Manuel Montenegro <manuel@nucypher.com>
Fix the URI used for EIP4361 message to be properly formed - it caused an invalid SIWE message to be created.
…are invalid for SIWE.
Run linter.
…61 to be more accurate and in line with EIP712 auth signature call. This can perhaps be an interface/base class method in the future. Run linter.
taco-auth
taco-auth
for Demo
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.
🎸 - Good to merge this checkpoint of the code which was used for the Ceramic demo. It will be merged into the broader EPIC #527 where additional changes will be made based on feedback/discussions.
Type of PR:
Required reviews:
What this does:
This was an initial implementation of SIWE support used for the Ceramic demo. Post-demo, the implementation will be modified based on updated discussions/realizations, but these can be done in a separate PR. This is a good checkpoint to merge since we are simply merging into an EPIC branch and not directly into
main
.Issues fixed/closed:
Why it's needed:
Notes for reviewers: