New Open-Source Web/Mobile Wallet: Radically easy-to-use with Proof-of-Keys

[msg768]

SwiftCash - Web Wallet
SWIFT's web wallet is an open-source wallet written in html, css and javascript. All signatures are handled on the client-side and private keys never leave the browser. To secure the account of users who login with an email and password rather than a private key, the wallet hashes the email and passsword 144,000 times, and then uses the final hash to create an address and private key in the end. The wallet also enforces very strong passwords using a password strength meter to further secure the accounts against brute-force attacks.

Hosting
This web wallet is hosted on github, and can be accessed via:

https://swiftcashproject.github.io/webwallet/
https://wallet.swiftcash.cc/

To avoid becoming a victim of phishing attacks, make sure you always double check the domain in your browser's address bar. You can also download the wallet and run it locally. But you're still going to need Internet in order to transact with the blockchain.

BTC and LTC Support
Bitcoin and Litecoin transactions are created and signed locally and then sent to their own networks using api(s) provided by https://chain.so/ - https://www.blockcypher.com is also used for following up on transaction details.

Login With Your Private Key(s)
You can login with a SwiftCash, Bitcoin, or Litecoin private key. If you login with a SwiftCash private key, the wallet will generate a Bitcoin and Litecoin address using your SwiftCash private key. If you login with a Bitcoin private key, the wallet will generate a SwiftCash and Litecoin address using your Bitcoin private key. And if you login with a Litecoin private key, the wallet will generate a SwiftCash and Bitcoin address using your Litecoin private key. It is however highly recommended to use email and password to login if you intend to stash all your cryptos in the same wallet and only use the private key login feature with your paper wallets.

Transaction Fees
The wallet enforces a minimum of `0.002 SWIFT`, `0.0001 BTC`, and `0.001 LTC` transaction fees and allows users to increase this fee. To help avoid situations in which ridiculously high fees are paid by accident, the wallet enforces a maximum of `0.2 SWIFT`, `0.01 BTC`, and `0.1 LTC` transaction fees respectively.

Change Addresses
N/A. Changes are sent back to the sender's address.

License
Copyright (C) 2018-2019 SwiftCash Developers. This software is provided as is and with no warranty under the MIT license.

Support
For support, join http://discord.swiftcash.cc
Tweet: https://twitter.com/swiftcashcc/status/1101727445399482369

Donation Addresses
SWIFT: SXucSXaV5HURNyJUWnPrVFHTdRzoU2u19F
BTC: 13atMuQvjApUEuV5voxRVFMV6HHA5FjMFT
LTC: LMoqd7ikoq4XViBF6wwimGRFJVeSB6JmDh

STEEM: https://busy.org/@swiftcash
DISCORD: http://discord.swiftcash.cc
TWITTER: https://twitter.com/swiftcashcc
GITHUB: https://github.com/swiftcashproject
TELEGRAM: https://t.me/swiftcashcc

[1713493157]

1713493157

[1713493157]

1713493157

[1713493157]

1713493157

[1713493157]

1713493157

[OmegaStarScream]

Shouldn't be there some kind of verification (proof of ownership) for the email address? I managed to make multiple wallets using the same email address and different passwords, is that the expected behavior? Nevermind, that should be it since nothing leaves the browser and goes to your servers. Aside from that, few suggestions:

- I'm not sure about sending, but it might be a good idea to support native SegWit (bc1).
- If you're going to enforce people to use a strong password, maybe just give them a hint of the characters and length they should use.
- Instead of a blank page, It's better to display an error message in case the webcam is not plugged or cannot be accessed.

[columbiamining]

Nice work, msg768. I'll be trying this out today. Will let you know how it goes and if I run into any issues.

[msg768]

Shouldn't be there some kind of verification (proof of ownership) for the email address? I managed to make multiple wallets using the same email address and different passwords, is that the expected behavior? Nevermind, that should be it since nothing leaves the browser and goes to your servers. Aside from that, few suggestions:

- I'm not sure about sending, but it might be a good idea to support native SegWit (bc1).
- If you're going to enforce people to use a strong password, maybe just give them a hint of the characters and length they should use.
- Instead of a blank page, It's better to display an error message in case the webcam is not plugged or cannot be accessed.

Good suggestions! I'll see what I can do :-)