Facebook Announces More Details of Libra’s Technical Design

Facebook published the Libra whitepaper on June 18, 2019, through its Calibra subsidiary, proposing a global digital currency backed by a reserve basket of low-volatility assets — approximately 70% USD, 26% EUR, and smaller allocations to JPY and GBP government securities and money market funds. The Libra Association, incorporated in Geneva, Switzerland, launched with 28 founding members (later expanded to 100 targeted) including Visa, Mastercard, PayPal, Stripe, Uber, Lyft, and Spotify, each contributing $10 million. Facebook’s own subsidiary Calibra (later Novi) would build the consumer wallet, while the Association would govern the protocol.

The technical design chose permissioned Byzantine fault-tolerant (BFT) consensus rather than Bitcoin’s proof-of-work: LibraBFT, based on the HotStuff algorithm from VMware Research, required two-thirds of validator nodes to agree before finalizing a block — tolerating up to one-third Byzantine nodes. The transaction language, Move, was a resource-oriented programming language where monetary values were typed as resources that could not be copied or silently discarded, unlike Solidity’s unconstrained integer arithmetic that had led to Ethereum smart contract bugs. The Libra blockchain used a Merkle tree structure to allow lightweight proof of transaction inclusion. The whitepaper projected that the permissioned network would transition to permissionless operation as the ecosystem matured, though no concrete timeline was given.

Regulatory response was immediate and hostile: U.S. Senate Banking Committee hearings on July 16, 2019 and House Financial Services Committee hearings on July 17 grilled Facebook’s David Marcus over monetary sovereignty, privacy (given Facebook’s Cambridge Analytica history), and systemic financial risk. By October 2019, PayPal, Visa, Mastercard, eBay, and Stripe had all withdrawn from the Association, citing regulatory uncertainty. The project rebranded as Diem in December 2020 with a simpler single-currency stablecoin design; Meta sold Diem’s assets to Silvergate Bank in January 2022 and abandoned the project entirely. The Move programming language outlived the project: the Aptos and Sui blockchains, both founded by former Meta engineers in 2022, adopted Move as their smart contract language.

Why This Moment Mattered

The event is useful to read as a platform signal, not only as a product announcement. In the short term, it gave users and developers something concrete to react to. In the longer term, it became part of a larger pattern in artificial-intelligence, software, computing-history: hardware, software, services, and user expectations were all changing at the same time.

A good technology milestone usually matters for more than one audience. Enthusiasts notice the specifications or the interface first. Developers ask what new assumptions they can make. Companies look at cost, compatibility, and strategy. Ordinary users mostly notice whether the result makes their devices faster, easier, safer, or more useful.

The Broader Context

This period of computing was shaped by several overlapping transitions: faster networks, more capable mobile devices, cloud infrastructure, stronger security expectations, and software that changed continuously after release. Against that background, the milestone was not an isolated headline. It was one piece of a much larger movement away from static products and toward connected platforms.

That context helps explain why some announcements that looked modest at the time became important later. A browser feature, processor change, development tool, or platform policy can alter what future products are able to assume. Once enough users, developers, and vendors adapt, the new assumption becomes normal.

Looking Back

The value of revisiting the moment is that it shows how technology history is built from many medium-sized steps. Some are celebrated immediately, while others become meaningful only after the ecosystem catches up.

Looking back also keeps the story balanced. Progress usually brings tradeoffs: performance against power use, openness against consistency, convenience against control, and speed against stability. The most interesting milestones are the ones that reveal those tradeoffs clearly. This one belongs in that category because it helps explain not just what changed, but why the direction of computing kept moving the way it did.