The Bitcoin Murmuration. A big Bitcoin exchange has just run into a problem with their bank making it impossible for customers to deposit or withdraw dollars. This sabotage is a symptom of a bigger problem; the design of Bitcoin businesses. TL;DR: “A swarm of bees is safer and more dangerous outside the hive. It is better to have 5,000,000 users using CoPay than it is to have 5,000,000 users in Coinbase.” What is Inspired by , It is a way of describing the advantages and disadvantages of different business architectures in Bitcoin. For example, if you have 5,000,000 users in a database with user names, passwords, KYC/AML documents, fiat balances and Bitcoin balances as MySQL entries, you are in a “The Pillar and Pond Problem”? Eric Raymond’s famous piece Pillar Configuration: All the users are siloed in your pillar. You have one bank interface to serve your customers You are on one hardware platform, at one network address There is one place to attack the owners. In the , things are very different… Pond Configuration All the users are not on a single platform. Each user has their own bank relationship. Every user is on their own hardware, at many network addresses. There is no single place to attack the users. A business owner has no long term user care, custody or contract. A column is . It stands very tall. It is heavy — made of stone. It is a landmark, a target that can be seen . A column can be fenced off and pulled down or blown up with dynamite. A pond on the other hand, is , and s_pread out_ . A missile shot into it makes a splash that is quickly covered over and smoothed by water. A pond cannot be pulled down or blown up; it is already at the lowest possible level in its constituents; the free molecule — . immovable for miles flat over miles the single user The pillar is inherently weak. Here are examples of services that are more or less in Pond Configurations: Bitsquare https://bitsquare.io/ LocalBitcoins https://localbitcoins.com/ HodlHodl https://hodlhodl.com/ Samurai Wallet https://samouraiwallet.com/ Bisq https://bisq.network/ Electrum https://electrum.org/ And others https://bitcoin.org/en/choose-your-wallet Very flat. Nothing to knock down. Each molecule is a Bitcoin user. Find a particular one and stop her. If you can. But what about ? Is it a Pond or Pillar service? Azteco It’s . neither Azteco and . It is simply a way to distribute Bitcoin. There are . As soon as you redeem your voucher, you have no relationship with Azteco…until you buy another voucher. And another. It’s a rolling, disposable service, that doesn't tie you down, restrict you or require your long term trust. doesn't hold customer funds doesn't have users no user accounts By removing “signed up” users, companies that are structured as flat Ponds have many advantages. They have a smaller attack surface, less burdensome administrative headaches, and are more agile. There is less to explain, keep tidy and manage; the cost of all of these problems is pushed on to other services, which if are designed correctly, make the problems disappear entirely from the user network. they Pillars have big SPOF (Single Point of Failure) problems that they can’t make go away; they are built into the assumptions and business model. This diagram could be superimposed on any company from Coinbase down. That company is under a very nasty attack, where all of its user data has been unconstitutionally demanded. That attack is possible because a single, “SPOF” monolithic service. “Pillar Bitcoin” Coinbase is a Pillar; Completely redundant system without SPOFs.(Note: Assumes Generator and Grid sources are each rated at N, Each UPS is rated at N and “A/C” and “Electrical” are in themselves completely fault tolerant systems This is a much better architecture. The system is entirely redundant, made of separate pieces. If any box (user or service) fails, the system carries on without interruption. In BitTorrent, it’s even better, and remember, this has been enough to prevent anyone stopping the vast majority from sharing files for over a decade, despite needing central search portals to find magnet links that hash the torrent locations. Not a BitTorrent diagram, but very pretty. And in a fully decentralized network, The picture is even , because there is no 2D line (underlying single owner services) that you can traverse and attack. An ideal Bitcoin would be like a . All the birds are connected by a protocol bound in nature, that cannot be changed. You can shoot a shotgun at it, and a hole will appear where the shot enters. It cannot be stopped, only . And marvelled at. better Murmuration of Starlings observed It’s a sky pond. They Can’t Win Eventually, the bank problem will be gone forever, but in order to get there, you can’t use a Pillar to break the system; only a pond can dissolve it. New pieces of software like and the very interesting by are the future in the long term. Eventually a very resilient system of many redundant parts, more resilient than the BitTorrent ecosystem will emerge from the market, and everyone will live with it, and embrace it, just like they embrace the Internet, and accept it as a fact of life. Bitsquare HodlHodl Roman Snitko Finally, it should be clear to everyone that the ideal, if you are running a Bitcoin business, is to have total control over every part of your service, and to never rely on any third party for anything but the basics, like operating systems, ISPs and hardware. Any service you can get from an API, like Bitcoin network connectivity should be done “in house”, with your own software instances and equipment. As soon as you rely on someone else, the begins. Pillarization Process Here are some off the cuff rules of thumb. Flatten and spread out. Reduce complexity. Absolutely reject all identity other than what Bitcoin provides by default. . Reduce footprint. Increase speed. Make it disposable. Conform to the nature of the tools; completely reject — making services that and other institutions. Think UNIX “Bitcoin Skeuomorphism ” mimic banks And then… we win. If you like the content and feel so obliged to send some love via BTC donations you can do so at the address below:↴
