Rename `Wallet` to `Bitcoin` in the sidebar
See original GitHub issueAs agreed on Mattermost in the UX channel.
Using wallet
for bitcoin payment method doesn’t really make sense. As when you want to address payment method settings, you have to change wallet settings, which is a bit incorrect.
Considering that we already have wallets title in the sidebar, I propose that we change Wallet for on-chain, to Bitcoin. Now segregating BTC and LN isn’t ideal UX, but one day we’ll get there to unify these. Users shouldn’t have to think on or off chain, they should only think bitcoin.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Create a new wallet
After creating a store, you'll be able to attach a wallet by first navigating to the sidebar or slide-out menu and clicking/tapping the...
Read more >Sidebar: Setting up your cryptocurrency wallet | rsts11
You can use a web wallet, with an exchange like Bittrex or Coinbase, and in this case your address is created and maintained...
Read more >How to change the name of a tracked wallet or adding a label
To do this, simply open the dropdown on the Wallets-page and then select Rename. Then enter the new name or label you want...
Read more >How to claim your .crypto and add crypto addresses to your ...
... and into your wallet. This transaction is being executed on the Ethereum blockchain and gives you ownership over your domains.
Read more >How can a hardware wallet generate a new bitcoin ...
Hardware wallets generate new Bitcoin addresses offline using a process known as "deterministic key generation." This process involves using a seed phrase, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@bolatovumar @pavlenex Great, the additional information is exactly the kind of thing that I’m trying to learn in order to use this efficiently and correctly. Thank you.
@phershbe you did everything correctly. One thing you can do is add something like “close #3571” and it will automatically close the issue once your PR is merged.
See here for more details: https://stackoverflow.com/questions/12235620/automatically-closing-issue-from-pull-request-in-github