XORA founder and CEO Joren Lundgren points to one core reason the company is building on the XRP Ledger. In the early days of XORA, he says “one fact shaped everything”: XRP has a “huge, unusually loyal retail base,” and retail still holds most of the circulating supply.
That contrast matters in Lundgren’s framing. He compares XRP to Bitcoin, where he says supply has moved toward institutions and exchange-traded funds, while XRP “stayed in the hands of everyday holders.” The pitch is simple. If your product targets consumer adoption, your asset layer should reflect consumer ownership, not just institutional access.
But there is a catch. The source text provided stops after that premise and does not include the operational details a neobank customer would care about. We do not get specifics on XORA’s ledger-side architecture, how it handles account custody, what finality or throughput users can expect, or what real-world outages or delays the team has seen. The argument you do get is mostly about who holds XRP, not how XORA’s payments, wallets, or compliance would behave.
Why the holder base became a product bet
Lundgren’s case turns on distribution. He claims millions of people hold XRP and that everyday holders own “the majority of circulating tokens.” In his view, that loyalty and scale of retail ownership reduce mismatch risk for a consumer-facing financial product.
This is a plausible go-to-market logic. Retail users are easier to target when the asset ecosystem they already recognize is the same one your application routes through. It also helps avoid a common mismatch where a platform depends on an asset primarily held by institutions that do not translate neatly into consumer product usage.
Still, holder distribution is not the same thing as network performance, user experience, or regulatory readiness. XRP’s retail skew might support adoption, but it does not automatically answer whether XORA can deliver a stable, secure neobank experience.
What the source does not cover
The TechBullion excerpt you provided includes no concrete infrastructure claims beyond the rationale for choosing XRP Ledger. It does not say what token flows XORA plans to support, whether it uses XRP directly for payments or swaps into fiat rails, or how it will manage risks tied to asset volatility.
It also omits the deployment realities that would make the pitch testable. For example, we are not told which validators or nodes XORA relies on, how it monitors consensus health, or how it plans around transaction failures or congestion scenarios.
For any asset-based product, those specifics are not optional. Users care about uptime and reversibility, not just narrative alignment between “everyday holders” and a retail neobank.
The practical takeaway
XORA’s story, as far as the provided text goes, is a distribution-first thesis. It says XRP’s unusually loyal retail base shaped the decision to build on the XRP Ledger. That may help explain the company’s product direction.
But until the company publishes more than holder demographics, the choice reads more like a marketing foundation than an implementation plan. Assets carry risk, and neobanks live or die on execution details. This pitch gives you the “why.” The missing piece is the “how,” with enough operational evidence to judge it fairly.