Here's the past 24 hours. All good. There is one spike in latency that only affected a few links that were already poor. The tiny drop in network b/w appears to be a monitoring dropout and doesn't show on the switch port's monitoring. I think we're nearly production ready.

The past 24 hours of the hub's performance looks solid. There's a tiny glitch at 12:58 that might be the monitoring system. Currently it's handling 11,000 requests per second from 173 peers with about 0.006 seconds from the average request coming in to the reply going out.

My two youngest grandkids call @McDonalds "Old McDonald's".

This is a lie. All the court held was that physically assaulting someone to remove their Israeli flag was evidence that could help show that the assault was motivated by racial or religious animus.

I have my first bit of weird data from the hub. I'm tracking peer round-trip latency at application level and there was a weird spike that shows significantly worse performance for a period of about 15 minutes. The spike starts at about 1:59 AM PDT. The thing that puzzles me about it is that if the issue was caused by the hub itself, you would expect roughly constant latency increases for all connections. Maybe it was an issue with the hub's network connectivity? I only have one day of good instrumentation, so I don't know if this is a fluke, an event that will repeat every day at the same time, or something that will happen randomly.

We’ve been seeing more and more players in the payments and stablecoins space launch their own blockchains. To me, that’s a clear sign the market sees blockchain as core financial infrastructure — something we’ve believed in and have been building toward on the XRP Ledger for over 13 years. Launching a blockchain is hard. Building an ecosystem with developers, liquidity, trust, and real-world usage is even harder. The XRPL has real traction and institutional adoption because it’s been battle-tested, updated, and improved upon for well over a decade. Some blockchains are built with permissioned validator sets controlled by one entity or a small group. This can provide control and compliance for specific, closed-network scenarios, but it limits reach, resilience, and the ability for anyone to contribute to securing and growing the network. Decentralization vs. centralization is constantly debated and there’s not a single answer that fits every use case for crypto and the concepts themselves have changed in definition over the years. As many of you know, the XRPL is public and permissionless at its core, with optional permissioned features for regulated use cases. This open foundation makes it adaptable, interoperable, and well-positioned to serve as critical infrastructure for the world’s financial system — connecting assets, markets, and participants seamlessly across borders. The XRPL was built so fees stay low and predictable, just fractions of a cent, without a separate gas token. You can pay directly in XRP for any issued asset, avoiding the friction and hidden costs of buying another token just to transact. XRP is counterparty-free, accessible by all, and used as a bridge asset with real utility for payments, settlement, and liquidity. (Every transaction on the XRPL uses/burns XRP.) It’s encouraging to see some newer chains adopt design choices that have long been part of the XRPL’s architecture, like deterministic finality and Proof of Authority-based consensus mechanisms. It shows there’s growing alignment in the industry on the importance of predictable, reliable settlement for financial applications without expensive validation. Looking forward to the next phase of XRPL innovations, bringing more programmability, compliance-grade capabilities, and deeper liquidity for institutional use. And to those just getting started… Welcome to the party! The crypto tent is only getting bigger.

This wasn't me. I guess I better change my "Twitter" "passwoard".

Hey @grok, from 1 to 100, what’s my political lean? 1 being extreme left and 100 being extreme right.

You ____ my battleship!

I haven't run any XRPL infrastructure myself in a few years. Looking at the network, it seems like the most useful thing would be a high-quality hub with reserved slots for UNL validators, other hubs, and servers serving applications on XRPL. This would be me personally, not Ripple. My current plan is to deploy a server using an AMD 9950X CPU, 256GB of RAM, a 2TB boot SATA SSD, 2x2TB NVME SSDs (s/w RAID 0) for NuDB, and a 10GB (unmetered) link. It'd run Ubunutu LTE and be in a datacenter in NYC. It would be a single server run as a production service aiming for maximum uptime and reliability. Though nobody should rely on it because an important XRPL server should never rely on a single hub. I would also gather data from it to understand network behavior and performance but no disruptive testing would be done unless there were very unusual circumstances justifying it. This would be my server run by me with no official connection to Ripple other than that I'm a Ripple employee. Anyone think this is not useful or that something else would be more useful? Anyone see anything wrong or suboptimal in the configuration?