Flowee is a family of products and our goal is to move the world towards a Bitcoin Cash economy.
Flowee started with the low level infrastructure: the Hub (full node), indexer, bitcore APIs, etc. Now available in git is a new direction: the Flowee Pay project, which gives you a wallet.
The basic wallet functionality is available, importing a paper wallet and getting your balance. Sending actual payments. The basics. This took about a month of development time to do. The short time to start a new wallet gives it away; this is not all new code. Instead the Flowee libraries have been used to do most of the heavy lifting. Flowee libraries are the product of various other Bitcoin Cash products and many of the classes in the libs stem from the Satoshi client itself. Proven, stable code.
Why make yet another wallet?
Its probably because I’m picky. But much more is that I think the user experience for Bitcoin Cash payments can be much improved. And I’ve been complaining and suggesting improvements there, but in the end you need to actually do the work to see the change.
For the vast majority of people that we want to start using Bitcoin Cash the wallet they run on their device is not just the main user interface, it is the only place of trust. Compromise the wallet and you lose control or even your money.
It should be obvious, then, that it is important for our ecosystem to avoid lock-in, to avoid big tech companies the ability to control our wallet.
There is a simple and known way to do this and that is by keeping the product open source. Because no matter how much you trust a company, the pressure to censor or otherwise control users money is always there when they can get away with it. Doesn’t even have to be approved by the CEO, governments can force them.
Don’t accept lock-in solutions, use open source wallets.
Have pure SPV as a way to get updates
Flowee Pay connects to the existing Bitcoin Cash Peer-2-peer network. This is another way to avoid lock-in as most alternatives have a very limited number of peers available to find your payment data. Next to this the P2P network provides the best anonymity opportunity for every resident of every country.
More details on how this provides a lot of privacy, see this post: https://read.cash/@TomZ/floweep2pnet-312d182c
The point here is that the client should have the possibility to fall back to the most secure and private method available: the p2p layer. A client that requires some central server is just too risky because it forces lock-in.
Payment Protocol innovation
This is a long topic. The short version is that the payer and the payee have their wallets talk to each other using a known payment protocol and finish the transaction with minimal user-interaction. The PP makes payments (and related actions) easier.
The main used one today is a simple QR code with an amount and an address. A better one is BIP70 which adds a lot of useful features. We don’t have enough wallets even supporting that one, and I think we need to continue research to make the payment experience better.
Another really long topic. From UTXO management to avoid connecting persona’s, to active mixing of outputs. All this is not really happening enough and we need the momentum to pick up again.
Easy to skin and port to new platforms.
In the last 5 or so years we’ve seen a lot of companies come and go which needed some wallet of their own. It is rather insane that those companies all ended up writing their own wallet. The wallet was NOT the core business of those companies, many have benefitted from sharing a wallet codebase for most of the features. Only adding your own GUI on top of the core design.
Wallet for users, not traders
The goal of Flowee Pay is to be the best solution for users, it therefore supports one chain (BCH) only. Traders that want to have a bunch of coins will likely be happier elsewhere.
What is it that you want to build?
In short, the best payment experience anywhere.
To do this a lot of research is needed, many of them are topics of their own. But here is my roadmap at this point:
Where can I find this?
This is part of Flowee, which has its home on gitlab.