r/btc•
Metallaxis

Idea for wallet developers to help adoption

First, my background thoughts: I believe that key to the success of BCH is wider user adoption. But for widespread user adoption, we need orders of magnitude more merchants to be accepting BCH as payment for services and goods so that newcomers will see a compelling case of an ecosystem where they can use BCH in their everyday life, not in fringe cases. Having one or two merchants (in the best case scenario) within one's home city just won't cut it. Of course, in order for merchants to be accepting BCH, they need to see meaningful business in BCH, they won't go into all that trouble for the occasional monthly customer. And here is the problem: Unfortunately, even people that could be spending BCH with the merchants that are currently open to try this new currency often prefer to use fiat, that's Gresham's law in action. Way too many times I have read stories here of people noticing a merchant that is accepting BCH but they themselves did not give any business to said merchant.

I have seen this in myself also, as in the few cases when I had the chance to use either fiat or BCH, usually I chose fiat not for the convenience, but because I did not want to see my "BCH total" go down.

Of course, in order to combat this there is the "spend and replace" strategy, which I fully support. But it's hugely inconvenient to have to remember to go and buy BCH after you are done with your shopping, and calculate what you spent etc etc, I have never done it and I figure few people do.

So here's my idea: How about wallets have an automatic "spend and replace" option? For the bitcoin.com wallet it would be as easy as integrating an exchange.bitcoin.com account with the wallet. But it could get even better and more versatile for all wallets: With an initial setup of API keys and syntax settings from an exchange of preference, each wallet could offer this functionality, which I believe would do a great deal of incentivizing people to use BCH whenever they have the chance.

What do you think?

Posted Apr 6, 2020, 7:57 AM UTC

127
lubokkanev •

There was such a wallet before, called CashPay. It had Coinbase integration to achieve it. Sadly the creator went to BSV.

3
MetallaxisOP•

That's both good and sad to know, did not know of that wallet. But preferably, a wallet would not force a particular exchange, the user should be able to chose and setup the exchange of their choice, which would also reflect the fiat currency they use and not be confined to the supported fiat currencies of coinbase or what have you...

1
georgedonnelly George Donnelly -BizDev @ Bitcoin ABC / BCH Latam / BCH Ignite•

More important than merchants is that we solve the inflows challenge. https://read.cash/@georgedonnelly/merchant-adoption-is-pointless-without-regular-growing-inflows-8e8446d2

2
zeptochain •

Yes, it's a reasonable idea... but there's a privacy caveat -- you'd need to trust the wallet developer enough to give them access to your bank account. For me, that's a... maybe not. Other people may see it differently.

1
MetallaxisOP•

Thanks for your input. There is no need for bank information, just API keys for commands to the exchange, in which the user should maintain a reasonable balance (like people keep a reasonable balance in their debit card accounts).

Also, the API keys should ideally be stored in the app, not in a server or back-end or anything, so the developer would have no access to that. Now, if you are talking about trusting the developer in terms of the wallet not maliciously sending info to the developer, users already either 1) inspect the code or open source wallets or 2) already trust that the developer does not steal their crypto keys anyway.

1
zeptochain •
  1. What guarantee is it that the code run is the code made public?
  2. Same as before?
1
MetallaxisOP•
  1. In an open source program, you can compile the source yourself.
  2. Yes, but my point is that my suggestion does not add any risk vectors that do not already exist for closed source wallets like bitcoin.com, yet people still use them, so why not have the additional functionality?
1