VelvetX actually already supports Robinhood Chain, but when you open the @velvet_capital website for the first time, you’ll still see only seven chains listed.

This small discrepancy doesn’t seem significant, but it can easily cause new users to underestimate the product’s real progress.
I followed the usual way people explore a new project—went through the website, Blog, and Docs—and compared them. The website currently shows seven chains: Base, Ethereum, BNB Chain, Solana, Hyperliquid, Monad, and Sonic.
The Blog dated July 7 already states that Robinhood Chain has gone live on VelvetX. Users can move directly across chains like Solana, Base, BNB Chain, and Ethereum in a single transaction—no manual bridging required. Over the past few days, the team has continued to emphasize this, and the Docs also say the new feature will be prioritized for the flagship app VelvetX.
So my current impression is that the product iteration is running ahead of the information sync. I understand why—the team first pushed the feature to VelvetX, and it shows execution is indeed fast. But if someone only looks at the website, they might think VelvetX hasn’t caught up yet; if someone only checks the official X posts, they might assume the main interface has already updated.
What can be confirmed right now is that Robinhood Chain is in VelvetX, and it’s still invite-only to get in.
This also leaves ordinary users with a pretty useful decision habit: check the website for the baseline support scope, the Blog and X for what’s being pushed recently, and then check the Docs to confirm which product the feature belongs to and whether it’s in the invite stage or already open. When the three sources don’t match, first figure out which version you’re trying to enter and which entry point to use, then decide whether you need to request an invite code, connect a wallet, or trade directly—this can save a lot of back-and-forth hassle.
A direct recommendation for VelvetX: create a unified Network Status page that shows, all in one place, which product each chain is supported on, whether an invite code is required, the current status, the most recent update time, and exactly how to get in. Features only become usable once they launch, and only once the information is aligned will users feel comfortable using them.