CINXE.COM
Cryptocurrency doesn’t address the hard parts of financial inclusion - Wave Blog
<!doctype html> <html lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0, shrink-to-fit=no"> <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css" integrity="sha384-Vkoo8x4CGsO3+Hhxv8T/Q5PaXtkKtu6ug5TOeNV6gBiFeWPGFN9MuhOf23Q9Ifjh" crossorigin="anonymous"> <link rel="stylesheet" href="/walsheim.css"/> <link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;700&display=swap" rel="stylesheet"> <link rel="stylesheet" href="/main.css"> <link rel="icon" type="image/png" href="/img/favicon.png"> <script async defer data-domain="wave.com" src="https://plausible.io/js/plausible.js"></script> <meta property="og:type" content="article" /> <meta name="twitter:site" content="@WaveSenegal" /> <meta property="og:title" content="Cryptocurrency doesn’t address the hard parts of financial inclusion" /> <meta property="og:description" content="People sometimes ask us whether Wave uses cryptocurrency or blockchain technology. An important part of the cryptocurrency narrative is that it can help financial inclusion—after all, it’s a way to put your money on a computer, with no legacy banks or regulators acting as gatekeepers. Surely that’s what we need, right? Unfortunately, in reality, cryptocurrency doesn’t address the hard parts of financial inclusion. To see why, let’s look at the different problems that Wave needs to solve in order to serve our customers." /> <link rel="stylesheet" href="/jetbrains-mono.css"/> <title>Cryptocurrency doesn’t address the hard parts of financial inclusion - Wave Blog</title> </head> <body> <header> <nav class="navbar navbar-expand-lg navbar-light"> <a class="navbar-brand" href="/en/"><img src="/img/nav-logo.png" class="logo-small" alt="Wave logo"></a> <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarCollapsible" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation"> <span class="navbar-toggler-icon"></span> </button> <div class="collapse navbar-collapse" id="navbarCollapsible"> <ul class="navbar-nav mr-auto"> <li><a href="/en/">Personal </a></li> <li><a href="/en/business/">Business </a></li> </ul> <ul class="navbar-nav ml-auto"> <li><a href="/en/about/">About</a></li> <li><a href="/en/careers/">Careers</a></li> <li><a href="/en/blog/">Blog</a></li> </ul> </div> </nav> </header> <main id="articleWrapper" class="waverow longform-content"> <article> <h1>Cryptocurrency doesn’t address the hard parts of financial inclusion</h1> <div class="byline"> <img class="authorThumbnail" src="/img/blog-authors/ben-kuhn.jpg" alt="picture of Ben Kuhn"/> <div class="authorDescription"> <div class="name-and-date"> <span class="name">Ben Kuhn </span> <span class="date"><span class="date-on"> on </span>March 30, 2022</span> </div> <div class="tag"><div class="tag-text">engineering</div></div> </div> </div> <hr> <p>People sometimes ask us whether Wave uses cryptocurrency or blockchain technology. An important part of the cryptocurrency narrative is that <a href="https://www.weforum.org/agenda/2021/06/cryptocurrencies-financial-inclusion-help-shape-it/">it can help financial inclusion</a>—after all, it’s a way to put your money on a computer, with no legacy banks or regulators acting as gatekeepers. Surely that’s what we need, right?</p> <p>Unfortunately, in reality, cryptocurrency doesn’t address the hard parts of financial inclusion.</p> <p>To see why, let’s look at the different problems that Wave needs to solve in order to serve our customers. Here are the main ones, ranked in increasing order of difficulty:</p> <ol> <li>We need to keep track of our customers’ account balances.</li> <li>We need them to trust that their Wave balance is correct and Wave won’t lose the money.</li> <li>We need to comply with relevant regulations—know-your-customer laws, capitalization requirements, account limits, etc.</li> <li>We need to provide an easy way for users to exchange their balance for cash and vice versa. (This is especially important in low-income countries, where many of our users have little enough cash that keeping extra balance in their Wave account isn’t practical.) For Wave, this is our agent network.</li> </ol> <p>Does cryptocurrency help with any of these?</p> <p>Cryptocurrency is a fine solution to the first problem—tracking account balances—especially between third parties that don’t trust each other. <a href="https://www.wave.com/en/blog/simple-architecture/">At Wave, though, we prefer to use boring technology,</a> and a simple relational database like <a href="https://www.postgresql.org/">Postgres</a> does an equally good job at this. In fact, our Postgres-based accounting ledger supports more transactions per second, with dramatically quicker transaction confirmation times, than most blockchains.</p> <p>The second problem, trust, is one that cryptocurrency does help with under some circumstances—but not in the context of financial inclusion. For a technically sophisticated early adopter, the cryptocurrency pitch—“these algorithms guarantee that we can’t get your balance wrong, even if we’re malicious”—makes some sense. But a typical underbanked person in Senegal, who may not understand Merkle trees or Byzantine fault tolerance, might justifiably be skeptical. For us, it’s much more important to have more traditional markers of trust, like approval from bank partners, billboards in major cities, TV and radio ads, and so on.</p> <p>Cryptocurrency proponents often claim that crypto <em>does</em> help with the third problem, compliance—because crypto doesn’t technically fall under central bank jurisdiction, since it’s not fiat money. In our experience, though, this is a badly mistaken assumption about how regulators work. Regulators gonna regulate, regardless of your aggressive interpretation of the letter of the law. If you’re facilitating a substantial fraction of economic activity—as Wave is in Senegal—the central bank needs to be comfortable with what you’re doing.</p> <p>But the hardest problem we have to solve by far is the fourth: providing an “on-ramp” for our customers to convert their balance to and from cash. Cryptocurrency actually makes this <em>harder.</em></p> <p>The importance of a smooth on-ramp is seriously underrated by cryptocurrency enthusiasts. That’s understandable—the enthusiasts are exactly the people who were most willing and able to go through all the difficult steps of investing in cryptocurrency today, and it’s easy for them to assume that it would be just as doable for other people. But most of our customers aren’t tech-savvy, number-savvy crypto enthusiasts; they’re normal people with better things to do than stress out about exchange rates, transaction fees, confirmation times and wallet passwords. Plus, they don’t have enough savings to be happy keeping some of it locked away in a parallel financial system. It needs to be frictionless to get money in and out whenever it’s needed.</p> <p>Suppose you’re a typical Wave user—a Senegalese fisherman who gets paid for your fish via Wave. On an average day, you make around 5,000 CFA francs, or about US$10. You don’t have any savings. When someone pays you for fish, you immediately walk to the nearest agent and withdraw the money.</p> <p>Now imagine the same scenario using cryptocurrency. If someone’s going to pay you for fish, you need to have the current crypto exchange rate memorized, then do mental multiplication to convert your CFA price for the fish to crypto. When you go to the agent to withdraw your balance, you’ll need to know what exchange rate the agent offers to convert your balance back into cash. You’d also need to pay a high (and unpredictable) transaction fee, and wait a long time for the transaction to be confirmed so that the agent could be protected from double-spending.</p> <p>These problems are solvable in principle, by using a stablecoin on a much more efficient blockchain. But that’s a whole lot of effort just to get the user experience back to the baseline that we’ve already built! And even once you’re there, it doesn’t seem like the blockchain has any meaningful advantages that are worth that cost.</p> <p>Meanwhile, most people trying to use cryptocurrency to improve financial inclusion aren’t even thinking about on-ramp problems. When I mentioned this problem in a Twitter thread, someone pointed me towards what they considered to be the best project in the “cryptocurrency plus financial inclusion” space, run by a person they described as very strong on product. I read a description of how to use the product, which ended with “[the money transfer recipient] can simply go to a Bitcoin ATM or local Bitcoin teller and receive their local fiat currency.” I looked up the number of Bitcoin ATMs in the country in question; the first one had launched the previous week. The description did not mention transaction fees, confirmation times, or any expected growth in the number of Bitcoin ATMs.</p> <p>Our view is that the narrative on cryptocurrency and financial inclusion is mostly a case of “if all you have is a hammer, everything looks like a nail.” If you want to improve financial inclusion, that’s awesome, but we’d suggest approaching it the way Wave does—by thinking from first principles about what the simplest, most effective solution to the problem would look like—instead of by throwing your favorite vaguely-related shiny technology at it.</p> <p>That doesn’t mean we think cryptocurrency is useless. It has several features that could make it well-suited to other use cases:</p> <ul> <li>As a store of value that’s not pegged to a fiat currency, cryptocurrency can be a relatively accessible safe asset in countries experiencing hyperinflation.</li> <li>It’s much easier to build software that interoperates with blockchain systems than with, say, bank accounts.</li> <li>Cryptocurrency transfers settle in minutes, compared to hours or days for other types of inter-bank transfers in many countries.</li> </ul> <p>The last benefit is especially underrated, in our view. Businesses with high cash turnover (like Wave!) can end up with huge amounts of funds tied up “in transit” between different bank accounts. We spend an enormous amount of time and effort optimizing this “back-end” funds flow; if we were able to use cryptocurrency to settle these transfers instantly, we would need dramatically less working capital, which would allow us to scale faster and charge our users less.</p> <p>Of course, the above aren’t the main use cases of cryptocurrency today: those are speculation, <a href="https://selfkey.org/list-of-cryptocurrency-exchange-hacks/">theft</a>, <a href="https://www.coindesk.com/ransomware-is-a-crypto-problem">extortion</a>, <a href="https://www.bbc.com/news/uk-england-birmingham-57280115">more theft</a>, <a href="https://academic.oup.com/rfs/article-abstract/32/5/1798/5427781?redirectedFrom=fulltext">drugs</a>, <a href="https://github.blog/2021-04-22-github-actions-update-helping-maintainers-combat-bad-actors/">even more theft</a>, and <a href="https://www.visualcapitalist.com/visualizing-the-power-consumption-of-bitcoin-mining/">speeding up climate change</a>. It remains to be seen whether legitimate, productive uses of cryptocurrency will ever justify the hype. We hope so!</p> <p><em>If you’re interested in leveraging <a href="https://www.wave.com/en/blog/simple-architecture/">boring, untrendy, and mature, technologies</a> to <a href="https://www.wave.com/en/blog/world/">improve the lives of our users</a>, we’re hiring at every level, from director (basically the highest management level we have since we’re not large enough to have VPs, etc.) on down.</em></p> <p><em>At the moment, some particular critical hiring needs are <a href="https://grnh.se/72f35bff4us">on-prem knowledgeable SRE</a>, <a href="https://grnh.se/bf82e3da4us">generalist SRE</a>, <a href="https://grnh.se/c6b84d2c4us">iOS engineer</a> and <a href="https://grnh.se/780f49864us">Android engineer</a>. Of course, we’re also hiring for <a href="https://grnh.se/bfe537594us">generalist software engineers</a> as well as <a href="https://www.wave.com/en/careers/">many other other positions</a>. We’re fully remote and have people all over the world!</em></p> <hr> <div class="closer"> We work on Wave because we think it’s <a href="/en/blog/world/">an extremely effective way to improve the world</a>. If that’s how you want to spend your career too, <a href="/en/careers/">come work with us</a>! <hr> <p>If you liked this post, you can subscribe to <a href="https://www.wave.com/en/blog/index.xml">our RSS</a> or our mailing list:</p> <div class="subscribe"> <div id="mc_embed_signup"> <form action="https://wave.us10.list-manage.com/subscribe/post?u=9c1c2a3d440cde1068d9c58dd&id=3de6dee936" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate> <div id="mc_embed_signup_scroll"> <div class="mc-field-group"> <input type="email" placeholder="Email Address" value="" name="EMAIL" class="required email" id="mce-EMAIL"> </div> <div id="mce-responses" class="clear"> <div class="response" id="mce-error-response" style="display:none"></div> <div class="response" id="mce-success-response" style="display:none"></div> </div> <div style="display: inline-block; position: absolute; left: -5000px;" aria-hidden="true"><input type="text" name="b_9c1c2a3d440cde1068d9c58dd_3de6dee936" tabindex="-1" value=""></div> <div class="clear"><input class="wavebutton" type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button"></div> </div> </form> </div> </div> </div> </article> </main> <footer> <div class="main-footer"> <section class="logo-lang"> <a class="logo" href="/en/"><img src="/img/nav-logo.png" class="logo-small" alt="Wave logo"></a> <div class="lang-menu btn-group dropup"> <button type="button" class="btn dropdown-toggle" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> <h5>English</h5> </button> <div class="dropdown-menu"> <a class="dropdown-item" href="/en/blog/crypto/">English</a> </div> </div> <p class="copyright"> © Wave Mobile Money Inc. </p> </section> <section class="wavecol" id="footer-navigation"> <h5>Company</h5> <ul> <li><a href="/en/about/">About Us</a></li> <li><a href="/en/careers/">Careers</a></li> <li><a href="/en/blog/">Blog</a></li> </ul> </section> <section class="wavecol" id="footer-navigation"> <h5>Legal</h5> <ul> <li><a href="/en/terms_and_conditions/">Terms and Conditions</a></li> <li><a href="/en/security/responsible_disclosure">Responsible Disclosure</a></li> <li><a href="/en/wdf/">Wave Digital Finance</a></li> <li><a href="/en/privacy/">Privacy Notice</a></li> </ul> </section> <section class="wavecol"> </section> <section class="download-links"> <a href="https://play.google.com/store/apps/details?id=com.wave.personal"><img class="download-badge" src="/img/en/google-play-badge.png" alt="Get it on Google Play"></a> <a href="https://itunes.apple.com/sn/app/wave-mobile-money/id1523884528"><img class="download-badge" src="/img/en/app-store-badge.svg" alt="Download on the App Store"></a> </section> </div> </footer> <script src="https://code.jquery.com/jquery-3.4.1.slim.min.js" integrity="sha384-J6qa4849blE2+poT4WnyKhv5vZF5SrPo0iEjwBvKU7imGFAV0wwj1yYfoRSJoZ+n" crossorigin="anonymous"></script> <script src="https://cdn.jsdelivr.net/npm/popper.js@1.16.0/dist/umd/popper.min.js" integrity="sha384-Q6E9RHvbIyZFJoft+2mJbHaEWldlvI9IOYy5n3zV9zzTtmI3UksdQRVvoxMfooAo" crossorigin="anonymous"></script> <script src="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js" integrity="sha384-wfSDF2E50Y2D1uUdj0O3uMBJnjuUD4Ih7YwaYd1iqfktj0Uod8GCExl3Og8ifwB6" crossorigin="anonymous"></script> </body> </html>