КУ

🪦 The site is dead. The token is still trading. We measured how common that is on XRPL — and it turns out to be the norm, not the exception. 🔬 METHOD Every XRPL project with 500+ trustlines — 1,443 of them. Two axes checked per project: ▸ Is the infrastructure alive (domain, website)? ▸ Are trades still happening on the ledger? On-chain from a full-history node. Website state from Wayback archive snapshots. Upfront: this is about abandoned infrastructure, not about scams or exit schemes. We make no claims about intent. 📊 WHAT WE FOUND 758 projects had a website at some point. Of those, 413 — 54.5% — now have a dead domain: DNS doesn't resolve, the server doesn't answer, or it returns a parked placeholder. And the part that matters: 344 of those 413 — 83% — executed trades in July 2026. With a dead site. 🧩 YOU CAN'T TELL FROM THE LEDGER You look at a token: trades happening, holders, a price, sometimes an AMM pool. It all looks operational. And the project's website hasn't responded in two years. We compared trading profiles of abandoned and live projects — unique traders, trade concentration. They're statistically indistinguishable. Residual and arbitrage liquidity looks exactly like a live market. Median time with a dead domain: over 786 days. That's a lower bound, because trading never stopped during it. Out of 734 measurable projects, trades ceased in six. 💸 THE SCALE ▸ 882,223 addresses with non-zero balances sit in projects with dead domains ▸ ~1.5 million in live projects Roughly two stranded wallets for every three in projects whose sites still open. 🔍 TWO EXAMPLES CX1 — 38,031 holders, KYC passed. Last live snapshot of the site: December 2023. Today the domain's certificate is issued to a different host and serves no content. The token trades, has an AMM pool against XRP, last payment July 22, 2026. XRSHIB — 12,928 holders. Domain stopped resolving after October 2024; DNS simply doesn't know the name. Last trade July 22, 2026. We describe what we measured — the site and the ledger. We draw no conclusions about the teams themselves. ⚠️ A TRAP WORTH KNOWING Trustline count is not holder count. Sell everything and your balance hits zero, but the line remains — removing it takes a separate action to reset it to default, which almost nobody does. So we counted only non-zero balances throughout. 📐 WHAT WE DON'T KNOW For 685 of the 1,443 projects (47%) we have no domain at all — neither on a site nor in the ledger itself. They can't be assessed on infrastructure. That's 958,000 addresses, and it could be abandonment or gateways with internal units that never needed a website. We count them as neither alive nor dead. #XRPL #XRP #OnChain

💵 @ournuvion — an AI-powered global banking platform for cross-border payments — has integrated RLUSD into its infrastructure. 🧩 The integration lets businesses move between traditional banking rails and blockchain payment networks through a single API: cross-border settlement, treasury and liquidity management, embedded blockchain payments. 📈 Context: RLUSD supply on XRPL has grown from ~$20M in late 2024 to ~$800M by June 2026 — now around 51% of total RLUSD supply (up from ~17% in April), per Evernorth. Monthly RLUSD transactions on XRPL have risen from ~54K to 600K–1.1M. 🏛️ Timing: the announcement landed the same week @Ripple secured full MiCA CASP authorization in Luxembourg, opening regulated access across 30 EEA countries. "Integrating RLUSD expands the infrastructure available to businesses operating internationally," said Keisha Clark, Managing Director of Nuvion. Source: Nuvion/Ripple press release, July 6, 2026. #XRPL #RLUSD #StablecoinPayments

💱 Building on XRPL in .NET? Your money math shouldn't fight you. XrplCSharp keeps XRP amounts as a real C# decimal — set ValueAsXrp = 1.5m and drops⇄XRP stays exact, no float rounding in financial code. What you get: ▸ a mature, open-source (Apache-2.0) pure-C# XRPL SDK — connect, sign, submit in a handful of lines ▸ async + WebSocket client ▸ .NET 8 / 9 / 10 ▸ C# models, binary-codec serialization and integration tests for the newest XRPL amendments — XChain Bridge (XLS-38d), Single-Asset Vault (XLS-65d), Lending (XLS-66d), Credentials, MPT — ready the moment each one activates on your target network Built on earlier C# XRPL work by @AskChrisW and @angell_denis (CTO @XRPLF). Now maintained and published by StaticBit. Get started: ▸ dotnet add package Xrpl ▸ github.com/StaticBit-io/Xrpl… cc @RippleXDev @XRPLF

🧮 The headline making rounds: XRP has a $71B market cap, but the XRP Ledger earned just $119K in fees this year. True — and it's not a bug. It's the design. ⚙️ Why protocol revenue is tiny by construction: ▸ XRPL fees are a fraction of a cent — and they're burned, not paid to anyone ▸ validators (150+: universities, exchanges, businesses) run for free — no block rewards, no staking yield (see the quoted post) ▸ so "protocol revenue" was never the model — it's anti-spam + deflation, not a fee-extraction business 📊 Where the value actually shows up: ▸ RLUSD on XRPL $760M+ ($1.6B with Ethereum) ▸ tokenized real-world assets $3.6B+, 30-day transfer volume +132% ▸ 3M+ transactions/day, settling in 3–5s 🧱 The honest tradeoffs (not hand-waving them): ▸ no fee rewards means validator economics lean on aligned incentives and reputation, not pay — a real, debated design choice ▸ XRPL DeFi TVL fell from $120M to $40M — a genuine weak spot, not a rounding error Comparing XRPL fee revenue to Tether's $2.5B (an issuer's margin) or to fee-extraction chains is apples-to-oranges. XRPL's bet is utility, not tolls. cc @RippleXDev @JoelKatz @XRPLF #XRPL #XRP #RLUSD

🛡️ We covered what native lending on the XRPL is. Here's how hard they tried to break it before shipping. RippleX is calling XLS-66 the most rigorously tested amendment in XRPL history — and the numbers back it: 🔬 Immunefi Attackathon ($200K in RLUSD, 35K+ lines of C++): ▸ 131 researchers, 455 submissions ▸ 94 valid findings — 15 critical, 19 high, 17 medium ▸ critical bugs found → full pool unlocked, all fixed 🧱 Layered on top: ▸ Halborn audit — 7 findings in the Single Asset Vault, 2 critical ▸ AI-assisted red team (Mar–May) — 20 tickets, 7 confirmed bugs Every issue resolved before the code moves toward mainnet. XLS-66 (lending) and XLS-65 (vaults) are still in validator voting — this is why the pace is deliberate. Not a price catalyst. A signal that institutional rails get institutional-grade testing. cc @RippleXDev @ja_akinyele @XRPLF #XRPL #XRP #DeFi #RLUSD

🧮 Every trustline you open locks 0.2 XRP in owner reserve. That airdrop you farmed. That memecoin you flipped. Each dead line is still holding XRP you can't spend. 20 forgotten lines = 4 XRP frozen, doing nothing. 🧵👇

🔐 Q-Day, part 3: how the XRPL actually goes post-quantum — without a hard fork. The threat is concrete: every time an account signs, its public key lands on-ledger forever. Harvest-now-decrypt-later makes that exposure a liability today, and Google Quantum AI research keeps pulling the timeline in. 🔑 The XRPL's edge is structural. It natively supports key rotation — move to a new signing key without changing your account — plus seed-based deterministic derivation. Ethereum has no protocol-native equivalent; there you'd manually migrate assets to new accounts. ⚙️ The approach is hybrid, not a one-off patch: ▸ a post-quantum scheme runs alongside ECDSA ▸ crypto-agility across several NIST algorithms, not one ▸ a Q-Day contingency plan if standards break early All without a hard fork and without permanent performance overhead. 🗓 Rollout: a hybrid-signing PoC with Project Eleven, validator testing and Devnet benchmarking now → candidate PQ signatures alongside ECDSA on Devnet next → a formal amendment for native PQC. Full readiness no later than 2028. This isn't a patch. It's a multi-year architectural migration of a live financial network — done without halting it. cc @RippleXDev @ja_akinyele @XRPLF #XRPL #XRP #Quantum #PostQuantum