Example: The single biggest payment processor only takes BIP70 payments. Someone with little coding experience should be able to easily build a BIP70 enabled service. Im a sftwr engineer & don't know where to start..
BIP70 is one part of it, much like BIP32, BIP39, sort-of BIP43, and BIP44 all make up a "wallet."
Well, yes... But my point is that there are no frameworks or tools to easily build a wallet with BIP70 support. No tutorials or guides, even. You literally have to do it from scratch.
Search for it. Literally 5 docs and 3 open source wallets pop up on the first page 🤔
Uh, you got a link (or 8)? The closest I could find last night was bitcoinj's API - which is for BTC only, unless I am mistaken.
BitcoinJ, Electrum, bread. Converting between BTC and BCH should be the easy part.
Lol, yeah, so the easiest method is to rewrite a BTC framework/wallet to run on BCH? My point is made. Should not be this hard to build a service that can interact w/ the
#1 merchant.
Are you being serious? Change “bitcoin” to “bitcoincash” in the HTTP header and URI.
Bitbox is a great step in the right direction, but it is still very barebones. Not everyone should have to understand the fine details of the protocol to use it.
It's a simple matter of abstraction. Every software protocol ever has solved this same issue with innumerable frameworks, APIs, etc. Something BCH currently severely lacks.
Are you serious? Do you know what an API is? The point is I shouldn't have to figure out how a complex wallet /API implementation works & change it to BCH to build a simple service.
"You stood on the shoulders of geniuses [...] and before you even knew what you had you patented it and packaged it and slapped it on a plastic lunchbox and now you’re selling it..."
These aren't dinosaurs. This is a global public protocol that the whole world needs to be able to easily build on. And soon - we need massive adoption b4 block reward drops too low.
My misunderstanding. I was looking at your question from the server side, not the client.
