-
Notifications
You must be signed in to change notification settings - Fork 96
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
Revise External signers
page in How it works
section
#59
Comments
Idea to add recommendations for users on how to handle hardware wallets by @moneyball (original comment).
|
Revisiting this discussion. My suggestion is to have this as a separate product section in the guide that goes into detail about all the different ways in which a HWW can be designed. The focus being on the UI components not the hardware design ofc. Relates to Moneyball's comment here
|
Just a note, this page can be the connector for our collab with the real-world projects, in this case, Square, which is now def working on a hardware wallet. |
This could be another "mega case study" section we include in the guide. |
Just picking this up again, when we have the Daily Spending Wallet section mostly fleshed out, we should start working on a 'Savings wallet' that covers this and has a more on-chain focus. Maybe change this issue to |
I'd start with a very basic page for people who know little to nothing about hardware wallets. Then we could build on that. |
External signers
page in How it works
section
Let's start with making an |
We already have one actually, we should expand on that section https://bitcoin.design/guide/how-it-works/private-key-management/external-signers/ Need to add new content around NFC privacy considerations #580 |
External signers
page in How it works
sectionExternal signers
page in How it works
section
This has been brought up a few times. It could cover topics like...
The "Hardware" overview page has a short section about hardware wallets. This new page would be a natural extension of that content, but could also be linked to from relevant content in other sections (like private key management and transactions).
The text was updated successfully, but these errors were encountered: