rfc: Web3Auth social login integration for Hathor wallets#106
Open
andreabadesso wants to merge 3 commits into
Open
rfc: Web3Auth social login integration for Hathor wallets#106andreabadesso wants to merge 3 commits into
andreabadesso wants to merge 3 commits into
Conversation
Design document for integrating Web3Auth into Hathor wallets, enabling social login (Google, Apple, email) as an alternative to seed phrase management.
andreabadesso
changed the title
andreabadesso
moved this from In Progress (Done)
to In Progress (WIP)
in Hathor Network
The original draft was 570 lines of open-ended exploration. Rewrite to 277 lines focused on what we actually have to do. Major changes: - Fix architectural contradiction: replaced the "use raw Web3Auth key as BIP32 master entropy and derive a tree" approach with a pointer to the single-key wallet mode in internal-rfcs#46. Fabricating a chain code from the raw key breaks cross-app portability and is a non-standard crypto construction. - Add operational setup section — the missing actionable piece. Covers Web3Auth dashboard registration, pricing tier selection, OAuth provider setup per platform, verifier strategy (recommend custom verifiers), recovery-share enforcement, monitoring, and legal/DPA requirements. These are company-level actions that have to happen before any code runs. - Scope as cross-cutting foundation: link to internal-rfcs#46 (wallet- lib + mobile UI), internal-rfcs#47 (wallet-service support), and hathor-wallet-lib#1062 (library PoC) as the per-layer designs this foundation enables. - Cut content that was exploratory but not actionable: full DKG protocol walkthrough with bivariate polynomials, Lagrange interpolation math, per-node endpoint tables, Electron smart contract registry address, the "what happens if Web3Auth disappears" Mermaid diagram (kept a concise table instead). - Replace "Unresolved questions" with "Open decisions" — each item now names an owner (product / security / ops / finance) and is a choice, not a research question. - Remove outdated desktop-specific file-level changes (/src/screens/ WalletType.js, etc.) — the desktop wallet is now a future possibility, not phase 1 scope.
- Link the inline `internal-rfcs#46` and `hathor-wallet-lib#1062` references in the body text (previously linked only in the top-matter and in the Related work section). - Add URLs to Prior art entries (MetaMask Embedded Wallets, Binance Web3 Wallet, Argent, Phantom) — they were bold labels without hrefs. - Add URLs to Alternatives rejected entries (Magic, Privy, Dynamic, tss-lib) for consistency with the Prior art fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rendered
Summary
Foundation RFC for the Web3Auth integration: what Web3Auth is, how we talk to it, and what we have to do operationally to ship it. Implementation designs per layer live in companion RFCs.
Related work
Test plan