-
Notifications
You must be signed in to change notification settings - Fork 32
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
Upgrade Authentication with Passkey Integration System #45
Comments
Hi I'm Jan, I'm from dojo coding |
Could I be assigned to this? |
Proposal to Work on the IssueI am eager to contribute to this issue and believe I am well-suited for the task, given my extensive experience in Cairo programming and building decentralized applications on StarkNet. My expertise spans across multiple domains crucial for this implementation:
Why Assign This to Me?I have a track record of delivering high-quality solutions efficiently, with a deep understanding of smart contract security, decentralized architectures, and full-stack development. My ability to bridge frontend, backend, and blockchain components ensures a well-rounded, optimized solution. Estimated TimelineI anticipate delivering a fully functional solution within 2 days. Please let me know if I can proceed. I am excited about the opportunity to contribute and look forward to collaborating! Best regards, |
Hi, I am Ruben and I am a full-stack developer. This is complex task that require backend end fronted integration to be secure implementation (the challenge must never be generate in the client). I will create the backend route that handle the complex logic about the challenge with smart contract and two hooks usePasskeyRegistration and usePasskeyAuthentication. A. Registration Routes: I suggest to use @simplewebauthn and https://github.com/kalepail/soroban-passkey/blob/main/src/lib/webauthn.ts, https://github.com/kalepail/soroban-passkey/blob/99144b309f7159fc7a9b543d3b81e169104e5ecc/ext/capacitor-native-webauthn/src/web.ts#L2 as references. ETA: three days. |
Application for ContributionI am excited about the opportunity to contribute to this issue and am confident that my expertise aligns well with the requirements. With a strong background in Cairo programming and decentralized application development on StarkNet, I bring a well-rounded skill set to deliver an effective solution. Relevant Expertise
Why Consider My Application?My proven track record of delivering high-quality, optimized solutions in blockchain and full-stack development sets me apart. I have a deep understanding of smart contract security, decentralized architectures, and the synergy between frontend, backend, and blockchain layers—ensuring a seamless and efficient implementation. ETAI expect to have a working solution ready within 48 hours. Please let me know if I can proceed with the implementation. |
@espaciofuturoio what is your status with this issue? |
@AndlerRL it is still in progress. I will have updates soon. |
* feat(wip): upgrade authentication with passkey integration system * feat(wip): add signup flow * feat(wip): add sign-in flow * feat(wip): add sign-in flow * chore(docs): add some dev notes close #45 * fix: build issue * fix: build issue --------- Co-authored-by: Brandon Fernández <[email protected]> Co-authored-by: Bran18 <[email protected]>
Context
We are transitioning from Supabase Auth with email + OTP to a custom NextAuth implementation that uses passkeys as the primary authentication method. The existing OTP system will be repurposed as part of our account recovery process.
Current System
Our platform currently uses Supabase Auth with:
Acceptance Criteria:
Development Notes:
Blocker
Related
The text was updated successfully, but these errors were encountered: