Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

New web wallet category (multisign 2of2) #348

Closed
bitcoinuser opened this Issue Mar 16, 2014 · 4 comments

Comments

Projects
None yet
4 participants

I think on Choose your wallet page should have a new category for web wallets that implemented multisign as standard, ex: https://greenaddress.it/en/
I think this kind of web wallet is very secure because they can't go away with customers bitcoins.
Thanks

Contributor

saivann commented Mar 17, 2014

@bitcoinuser Adding more than 3 categories is probably a step that is going to make things more confusing for the end user IMO. I'd prefer we treat multisig as an attribute of a web wallet instead of a standalone category. Otherwise, we could end up with lightweight wallets, full node wallets, mobile wallets, web wallets, hybrid wallets, multisig wallets, hardware wallets, etc.

As an alternative solution, I was thinking of a new template for this page in which such attributes could be displayed within each wallet description (with clear icons and green/orange color codes). This would likely provide greater transparency for the end user, and better promote the idea that security isn't a binary yes/no choice.

@saivann Though I agree with not adding to confusion, GreenAddress is actively serving probably the most secure wallet out there atm. It is projects like these that we should encourage and support above all others.

If we don't support cutting edge innovation (multi-sig, nLockTime, etc) at its root, people will just settle for what they know and that's not acceptable. We need to push forwards the projects that embrace and implement the best solutions, simple as that.

Polve commented Mar 20, 2014

I support suggesting greenaddress.it since it's one of the most secure wallets out there.
A also it's to note that it's not only a website but it works also:

Contributor

saivann commented Jul 26, 2014

Closing this issue as it has been addressed differently by the new page layout.

@saivann saivann closed this Jul 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment