Last night, I checked out @RialoHQ’s Builder Hub—and honestly, it was well worth the late hour. After seeing so many Web3 pitch events, what I dread most is the ones that spend the whole time spinning narratives and overpromising. This one was different: almost everyone was a real builder actually building something. None of the projects are at an advanced stage yet, and none claim to be world-changing—but at least they’re all shipping, not just spinning wheels. That alone puts them ahead of many others. First up: V a L low Race (a crypto price racing prediction platform) I thought this idea was pretty clever—it turns crypto price movements into a race. Instead of staring at K-lines trying to guess direction, you watch which coin crosses the finish line first. It feels more like a game of strategy than passive trading, and adds a layer of engagement beyond just watching charts. The features aren’t half-baked: 1. Supports 10 major cryptocurrencies 2. Lets users filter by racing categories 3. Offers single, double, or triple bets 4. Includes estimated returns 5. Built-in live chat and player leaderboards 6. Daily 100-point rewards—details are surprisingly polished The demo was straightforward: they ran it live. Coin speed directly correlates with price movement over 5-second intervals—the bigger the swing, the faster the coin moves. It’s intuitive. You can also review historical races and track your own profit/loss history—big plus. But there are issues: latency. When two coins are neck-and-neck, frontend and backend occasionally desync, creating a jarring visual experience. The data comes from reliable financial APIs, so settlement is solid—but the display layer still has minor bugs. If these aren’t fixed, they’ll hurt user experience. On monetization, they were refreshingly honest: no clear plan yet. For now, they’re using a points system to navigate regulatory gray areas. If they ever move to real-money betting, they might take a small fee. The host suggested borrowing from mobile gaming: implement an energy system unlocked with USDC. Honestly, I think that’s a pragmatic approach—far smoother than jumping straight into gambling. ————————————————————————— Second: Cyferrun (a Rialo chain tool) This one really resonated with me—no-code tools are a game-changer for non-technical users. It has two core functions: scenario building and idea validation. For example, if you want to simulate what happens when ETH drops below $1,000, you just click “simulate” and instantly see node support rates, latency (around 42ms—not bad), and other metrics. Another useful feature: you input a DeFi or gaming idea, and it tells you whether it can run on Rialo—and even auto-generates a tweet to post it. Simple, blunt, but effective. There was a small hiccup: Discord froze during the demo and needed a restart—slightly awkward—but the rest of the flow went smoothly. The overall vibe is minimalist tooling—no fluff, clear positioning. As long as they avoid feature creep and keep iterating steadily, they could organically build a user base. No-code is genuinely compelling to a lot of people. ————————————————————————— Third: A governance tool (I didn’t catch the name…) Also built on Rialo, focused on community voting and governance—users can create polls just by logging in via Discord. Features include: - Public or private voting - Password protection - User filtering based on Discord activity (message count, online time) - Integration of points + SBTs as incentives The concept is solid—aiming to combat vote manipulation. But there are clear gaps: First, preventing sybil attacks is extremely hard—even with these metrics, multi-account users can still exploit the system. Second, it currently doesn’t support native content submission (e.g., proposals, models), citing performance concerns. I think this is a red flag—it severely limits use cases down the line. When asked about anti-sybil strategies, the founder gave a grounded answer: only reward points for verified, genuine votes. No vague future promises—just realism. But implementation remains challenging. Overall? The project isn’t wrong in direction—it’s just early. Limited practical use cases today, and many details still need refinement. ————————————————————————— Also worth noting: the voting rules for Shark Tank have been adjusted. Only those who fully participated in the previous round can vote now. The reason? Previous rounds were flooded with bot votes—so results were invalidated. I support this change. It’s low-cost but significantly improves vote quality by reducing external manipulation—a practical improvement. Another small but thoughtful tweak: Shark Tank was originally scheduled for tomorrow—but it got canceled. Instead, the voting system will go live tonight or tomorrow, with a full week to cast votes. Very user-friendly—no rushed deadlines. ————————————————————————— Looking at all three projects together: none are groundbreaking, but none are half-hearted either. They’re all in that real, messy middle ground—transitioning from testnet prototypes toward genuinely usable products. They have shape and direction, but still need polish. In short? This is probably what most Web3 builders look like right now: no flashy stories, no overhyped visions—just steady progress, iterative improvements. They won’t blow up overnight—but they’re far more likely to survive. #CNUGC