Extreme 🎒.

Hello @Backpack .

That’s going to be a lot of rate hikes for a bULL rUN.

- Hey gym manager, I’d like all the lights set to red. - Why? - For the tsunami. - For what? - 🎒.

Gm. Thank you @Backpack 🙏🏼🎒.

First you need a script. And a red @Backpack 🎒. 🎬🎥🍿.

Issued by @Backpack credit card.

Warm up 🎒

Cash is king…

Breakpoint London will be my first Breakpoint. Why am I going? To see my @MadLads family. Can’t wait to see you mfers. Fock it.

Gm. What does the Revolut outage from two days ago teach us? And why it’s a good lesson for Web 3 projects. At its core, a bank is software: the database that tracks your balance, the engine that grants or denies approval when you use your card at a terminal, and the programs that execute bank transfers. The cloud means not owning the computers that run all of this—instead, you rent them from providers like Google, Amazon, or Microsoft. Revolut made this choice from the very beginning, and in September 2025, they solidified it with a multi-year contract: Google Cloud now powers their global systems, from back-end operations all the way to the app itself. Google divides the world into regions, and each region into zones—facilities with their own independent power supply and network infrastructure. The promise to customers is simple: distribute your workloads across multiple zones, and a failure in one will not affect you. That morning, an electrical fault took one of London’s three zones offline. The entire region felt the impact: 38 Google products encountered errors, 28 Revolut services experienced degradation, and customers across seven countries—including France—were affected. The technical lesson here is invaluable: a multi-zone setup—and the immunity it implies—only holds true if nothing shared between those zones fails. A traditional bank keeps its core—the general ledger of accounts—on its own machines, sometimes for decades. The cloud only hosts the front end: the website, the app. If Google goes down, a bank loses a storefront—but not its engine. Revolut has no "home" of its own. Logins, card payments, transfers, stock trading, and even the customer support chat—everything ran through Google. And behind the app, there are no physical branches. When the screen stops responding, there is nothing left. Throughout the day, Revolut kept repeating that its customers' money was "safe." That is correct. IT security rests on three properties. Confidentiality: no one else reads your data. Integrity: nothing is altered. Availability: the system responds when you need it to. The outage affected neither the first nor the second property: the balance you had at 7:07 a.m. was still there at 7:09 a.m., recorded in an intact database. What was lost was the third property. Yet, for a bank, availability *is* the service—whether it’s a merchant paying a supplier, settling a grocery bill, or withdrawing cash before catching a train. Money that remains intact but inaccessible is, for the duration of the outage, money that effectively does not exist. Monzo, a competing British bank, runs primarily on Amazon. However, it has built "stand-ins"—a scaled-down backup banking system hosted on Google—that automatically take over for essential functions: card payments, cash withdrawals, transfers, balance inquiries, and card blocking. The cost of this safety net? Six engineers and roughly 1% of the total cloud bill. It has already been put to the test in real-world conditions as recently as 2024. This effectively dismantles the "cost" excuse: Revolut, with a valuation of $75 billion, can easily afford it. Since January 2025, the European DORA regulation has required every financial entity to map all its IT dependencies, assess its concentration risk (the classic scenario being an over-reliance on a single core provider), and document a contingency plan. As of November, 19 critical service providers—including Google, Amazon, and Microsoft—have been placed under the direct supervision of European authorities. The broader lesson extends well beyond Revolut: if ten banks host their payment systems in the same cloud region, a power outage could escalate into a nationwide banking failure. Conclusion : As a tech and financial project own your home.