Skip to content
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

Implement Web3 OAuth/Sign-In Functionality #11560

Closed
0xmulch opened this issue Mar 23, 2024 · 4 comments
Closed

Implement Web3 OAuth/Sign-In Functionality #11560

0xmulch opened this issue Mar 23, 2024 · 4 comments
Assignees

Comments

@0xmulch
Copy link

0xmulch commented Mar 23, 2024

Overview

I would like to suggest Jetty should integrate Web3 OAuth/Sign-In to let users log in with their blockchain wallets, like MetaMask or WalletConnect.

This move taps into the secure and user-friendly aspects of blockchain, offering a modern twist to logging in without traditional usernames and passwords. Impact to legacy code is minimal, so this would be a means of radically modernizing Jetty in the eyes of the public, without a lot of technical overhead for maintainers.

Following implementation, users would be able to authenticate by simply connecting their wallet! It’s like “Sign in with Google" but on-chain and permission-less. Moreover, numerous libraries already provide this functionality.

Long-term, Jetty could have significant potential within the Web3 space, particularly for enhancing cross-chain communications and supporting decentralized physical infrastructure. Jetty could play a crucial role in the evolving Web3 ecosystem. If explored, this direction could greatly amplify Jetty's impact on blockchain interoperability and the broader adoption of decentralized and open source systems.

Enhancement-Specific Description

  • User Perks: Instant account setup with a wallet address and one-click logins. No forms or PII, just a quick signature.
  • Compatibility: Works natively with major EVM wallets, keeping an eye on a smooth integration with our current system.
  • Benefits: This boosts security, protects user privacy by obfuscating PII, and puts Jetty ahead in the Web3 space.

Looking forward to making Jetty a pioneer in Web3. Open to feedback/questions.

CC: @jmcc0nn3ll

@gregw
Copy link
Contributor

gregw commented Mar 25, 2024

@lachlan-roberts is this something you'd like to look into?

@lachlan-roberts lachlan-roberts self-assigned this Mar 25, 2024
@0xmulch
Copy link
Author

0xmulch commented Mar 29, 2024

@lachlan-roberts If you run into any snags, don't hesitate to reach out and I can try to help you out.

lachlan-roberts added a commit that referenced this issue Jun 6, 2024
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts added a commit that referenced this issue Jun 6, 2024
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@lachlan-roberts
Copy link
Contributor

@0xmulch I have opened PR #11883 if you wish to review.

It is still a draft PR as there is still work to do including the documentation, but it is working and would be good to receive some early reviews.

lachlan-roberts added a commit that referenced this issue Jul 5, 2024
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts added a commit that referenced this issue Aug 26, 2024
 Issue #11560 - Implement EIP-4361 Sign-In With Ethereum
@lachlan-roberts lachlan-roberts moved this to ✅ Done in Jetty 12.1.0 Sep 27, 2024
@lachlan-roberts
Copy link
Contributor

Completed in the 12.1.x branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Status: Done
Development

No branches or pull requests

3 participants