Virtuell daglig uppdatering | ... | Graeme OKX Feed

Virtuell daglig uppdatering | 24 juni, 2025 Håll dig uppdaterad om alla nyheter från @virtuals_io ekosystem under de senaste 24 timmarna... ⏬

for you data-driven virgens out there. ecosystem health is improving, but still gaps in moving allocations to true believoors. this chart is how the eco looks like per token launched since genesis. LHS is first genesis token, RHS is the latest genesis. Red is bad - genesis participants who are here to jeet. Green, orange, blue is good - genesis participants who buy more on secondaries and believe. This snapshot makes sense coz post jeets (e.g., macro downturn weak hands, high genesis ROI TP weak hands). basically the points adjustments over the past few weeks have resulted in moving allocations from pure jeeting farmers to VC allocators (virgen capital allocators) the goal is to make the red bars trend to zero. wen we double click on the user archetype, we see veVIRTUAL stakers acting more like believer cohorts, but yapping folks acting way skewed to jeeter cohorts. the maths is constantly evolving, but we have a very clear objective. more into the hands of believing virgens. got distracted by points team lol, back to ACP work. virgenity

Hey Virgens and Arbusians, just wanted to share a quick update on how things are going on our side, both in terms of the broader market context and what we’re building at Arbus. The overall market remains sideways, partly due to macro uncertainties like the ongoing Israel-Iran tensions. While Bitcoin hasn’t reacted with a sharp decline, risk appetite has clearly dropped, especially in altcoins, pushing many investors back toward safer assets. This naturally impacts valuation and sentiment across the board. On the Genesis Launch side, we’re aware that things have slowed down. Shifts in framework rules (like Greenlock/Yellowlock mechanics) and the increasing allocation to specific projects have made staking into Genesis Agents feel less relevant. Combined with some ambiguity around Virgen Point calculations, this has raised question marks across the ecosystem. Add in a wave of lower-quality launches and general project fatigue, it’s clear we’ve entered a phase where not everything is winning just by showing up. That said, we’re sure the Virtuals team will find a way to take things forward, their track record speaks for itself. But those are external factors, things we can’t control. What we can control is how we build and execute. And on that front, nothing has changed for us. We’re still working around the clock, with multiple streams running in parallel: – Our API service is nearing completion. We’ve already shared a trial version with one of our partners, and others are in the pipeline. Once final integration is done, we’ll begin onboarding clients in a closed, revenue-generating setup. This marks our first monetization step beyond the Terminal. – ACP integration was prioritized recently at the request of the Virtuals team. We deployed the Arbus Assistant into ACP’s dev environment and completed our internal testing. It’s working smoothly and now Arbus Assistant is officially active within ACP. Expect more news on this soon. – Terminal improvements are ongoing. We’re actively gathering feedback from power users, planning our feature backlog accordingly, and refining based on usage analytics. The Index page remains the most used feature, followed closely by the Arbus Assistant, which is now our upcoming focus area. Zooming out a bit it’s worth noting that we started building in this space long before “InfoFi” became a trend. Back then, there were no categories for what we were doing. Now, as dozens of projects pop up weekly, we see the rise of copycat platforms mimicking surface-level metrics. Many of these projects skip over the core engineering and data quality challenges, which leads to shallow insights and misleading scores. For example, most Yapper platforms simply count likes, RTs, and replies, and derive mindshare from that. But without context, source quality, or signal-vs-noise logic, that doesn’t work. That’s why we built Arbus in the first place, to measure real reach and real value. Our Arbus Score, developed over two years of R&D, solves this. It’s already being used in the Vader YAP program, helping determine true impact and ranking weight. Without a high-signal metric like the Arbus Score, mindshare metrics become easily gamed and lose meaning. We’ve also analyzed other Yapper platforms. Even the most solid one gives too much weight to low-value replies, while some others show poor mindshare accuracy overall. The key takeaway? Strong infrastructure wins. Our native Virtuals-ready YAP solution is fully built on top of our custom data pipelines, and it’s nearing its final roll-out. We always execute with three things in mind; $ARBUS, our Virgens, and our stakers. Thanks for reading, we’ll keep shipping. The roadmap is clear, the work is in motion, and every item gets done. Priorities may shift temporarily, but the direction doesn’t. More updates soon.