A web-based solution for CashShuffle (and a path to CashFusion) integration into the Bitcoin.com mobile wallet.
Download the Bitcoin.com Dev Wallet and try it for yourself:
https://ipfs.io/ipfs/QmTaAWcTJUw2QaoTLa6cM2ERLfnrtiVrHLPtoic21fFbTz/bitcoin-wallet-dev.apk
(works on ANY Android device)
This decentralized app is LIVE right now:
https://bchdevcon3.hushyourmoney.com
(open in the Bitcoin.com Dev Wallet)
Help bring CashFusion to your mobile wallet:
https://causes.cash/@bchplease/hush-your-money-7a1589216c59
(accepting pledges starting at $0.01)
After learning that the Bitcoin.com wallet offered a 3rd-party app API called Link; I immediately made the move to join the BCHDevCon. I believed this would offer me an ideal opportunity to finally connect with the Bitcoin.com wallet developers.
I've been working on a CashFusion solution for mobile since January, when I released the Nito Cash web wallet, then later the NitoJS App. Unfortunately, as I'm not on Telegram, I found it difficult to garner the attention and support of the Electron Cash or Bitcoin.com wallet teams for supporting my research efforts.
BCHDevCon3 has changed that! I've directly connected with Corbin Fraser (@maplesyrupsuckr), the lead developer of the Bitcoin.com wallet, and now... it's time for daddy to go to work. 💪
Can't help but to be overly ambitious, so there are THREE!
As this was my motivation from the start; I value this as the top goal. Working directly with the team at Bitcoin.com would allow me the access & resources necessary to produce a CashFusion integration into their mobile wallet by end-of-year.
I strongly believe this would be the greatest immediate boost for adoption (particularly amongst current crypto users) as the promise of anonymity is how Bitcoin was born and will surely be how it continues to thrive in the near future.
The Bitcoin.com wallet's Discover tab offers in-app access to several 3rd-party services; some of which have direct wallet integration. Bitcoin.com Hush will be the next integration released in Discover (at least if I have anything to say about it).
By offering Hush directly in-app, users are offered not only a better service experience, but the confidence in security that comes with a native integration.
Inspiration for this comes from Blockchair's Privacy-o-meter as well as their excellent docs.
Users will paste an address or transaction id into the analyzer and receive a Privacy Score along with a detailed breakdown of the blockchain analysis data.
There are currently 5 methods offered by the API: getAddress, sendAssets, payInvoice, createToken and getWalletProviderStatus.
I would aim to add one new method called getAccount. This would specifically permit the application to call for the Extended Public Key (xPub) of the wallet. With an xPub, we are able to query ALL addresses owned by the wallet, NOT only the "active" address.
This would enable the application to:
- Automatically verify CashShuffle transaction success.
- Provide automated wallet privacy analysis and alerts.
- Provide custom address and transaction analysis.
Due to the fact the Bitcoin.com mobile wallet is currently closed-source, this goal will be developed and tested using the Badger plugin for Chrome/Brave. Fortunately, the functionality should be nearly identical if the Bitcoin.com wallet developers should choose to extend it to their app as well.
- Q: Will this project allow me to use CashFusion from within the Bitcoin.com wallet?
A: There's a 100% chance of that NOT happening by the end of this hackathon. However, this project WILL advance the groundwork necessary to see that happen by year's end.
https://lbry.tv/@BCHPlease:1/BCHDevCon3-Hush-Your-Money-Presentation:7
- Copy a fully-developed wallet (ie. Causes Cash) for a proper UX when shuffling and managing coins.
-
Recommend allowing requests for the "current" address (w/o iterating account index) on the Bitcoin.com wallet. NOTE: This is how it currently works on Badger.
-
Improve "services" infrastructure to avoid messages like:
{"errors":["MongoError: Executor error during find command :: caused by :: operation exceeded time limit"]} -
On a scale of 1 to 10 (1 being low, 10 being high); what is the risk of using the Extended Public Key (xPub) to derive the Hush wallet private key?