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.

Sign up for GitHub

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

Jump to bottom

feat: Use standard key derivation for metamask and key hardware #1102

Open
stringhandler opened this issue Jul 29, 2024 · 1 comment
Open

feat: Use standard key derivation for metamask and key hardware #1102

stringhandler opened this issue Jul 29, 2024 · 1 comment

Comments

@stringhandler
Copy link
Contributor

Problem

Miguel: Switch key derivation in second layer to use BIP-44 instead of aezeed? Easier integration (metamask snap wallets would be interchangeable with wallet daemon) but we need to figure out layer1-to-layer2 integration

Proposal 1:

Discuss further. Using the same seed phrase standard as metamask for L2 makes sense to me. Since L1 and L2 wallets are independent there shouldn't be any issues with using a different scheme.

https://crates.io/crates/bip39
https://crates.io/crates/tiny-hderive
@stringhandler stringhandler converted this from a draft issue Jul 29, 2024
@stringhandler
Copy link
Contributor Author

Yeah, I second this. I don't think we need to use Aezeed. It makes integration much harder

@stringhandler stringhandler moved this from Not ready to Must do in Tari Digital Assets Network (DAN) backlog Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Tari Digital Assets Network (DAN) backlog
Status: Must do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stringhandler