Thank you, Michael. I hope he has a chance to see this. I had a brief conversation with him before he completely withdrew and cut off all known communication channels. I can say with certainty that 150,000 followers were never the real issue. Even if they were, that number isn't outrageous. I also think Wolfie's decision was entirely reasonable. You're right, I think the accusations and attacks against CK were one of the real reasons that led him to leave. I sincerely hope he can return someday so we can continue working together. This has clearly hit him hard. Let's give him some time, and let the community learn from this and grow together.

#Kaspa open interest has fallen back to the lows of summer 2024, but prices have already dropped by approximately 80%. The difference lies in market participation. In 2024, similar open interest levels were accompanied by strong spot demand and rising prices. Today, low open interest reflects reduced leverage, diminished speculative interest, and a decline in overall risk appetite. This situation typically occurs at the end of a bear market/early accumulation phase. Leverage has been liquidated, speculative activity is limited, the market is calmer, and trading is thinner. Both bullish and bearish directional convictions are weak, leveraged positions are reduced, and sensitivity to forced liquidation is decreased. In short: prices have fallen sharply, but leverage has not yet recovered. This suggests market apathy rather than overactivity, and any sustained movement will likely require a recovery in spot demand rather than being driven by derivatives trading. #kas

I don't see anything wrong with Cryptok's request, and rejecting it is fine too. These are reasonable figures that can be negotiated. As for some comments—attacking a talented volunteer contributor who built and maintained an excellent platform with a top-notch user experience is completely unreasonable, simply because he decided to leave and has his own principles and aspirations. --- Thank you @cryptok777 for everything you've done for Kaspa. I sincerely hope you can find the time and opportunity to rejoin us, because I can assure you, Kaspa will always be there waiting for you <3

All members of $KAS Krew—this team was meticulously created and maintained by @cryptok777, a very friendly person, but he's had enough and doesn't want to continue anymore :( He's asking for $150,000 to relinquish control. After careful consideration by @kasmediadotcom and several other key members, we declined. We are committed to supporting @asaefstroem and developing a brand new second-generation browser from scratch, backward compatible with all of VPROGs' L2 synchronization, composability, real-time decentralization, all APIs, and new opcodes.

Kaspa currently ranks first in bullish sentiment. Despite recent price volatility, market sentiment towards KAS has actually increased. A growing number of traders and holders are taking an optimistic stance, reflecting their increasing confidence in the network and its long-term prospects.

I've never felt such a stark contrast between the thriving Kaspa R&D team and the feelings of (some) members of the community—at least in some aspects I've observed, and certainly not in others :) In short: the R&D team's talent and expertise are constantly growing, and they're getting real work done. More specific updates are coming soon. I believe the ever-expanding size of the Kaspa R&D team is the strongest indicator of its long-term growth. You can feel not only its increased size but also its maturing spirit. More and more contributors are emerging, passionate, eager to understand, explore, and contribute to core technologies. More and more programmers are submitting PRs, and more and more people are writing KIPs. Parallel research/development is converging into a unified vision. The timeline is becoming clearer, veteran contributors are reuniting, and programmers are even talking about DK's cascading voting algorithm in their sleep (I have no proof, but it's certainly true). Meanwhile, the core concepts that will guide the direction of near-term products are being refined and understood. These products will eventually be released. Kaspa's key advantages are gradually becoming apparent: its fast PoW mechanism achieves true real-time decentralization (RTD), perhaps unprecedented. I know I've always been optimistic, but this paradoxical situation is particularly noteworthy. Bitcoin has "died" multiple times, Ethereum has gone through the "is it over?" phase, and Solana, after SBF, certainly gave the impression of being nearing its end—it's easy to link weak price movements with long-term prosperity, even when fundamentals are quietly improving. One of my challenges is sharing my perspective so that more people can experience what I see firsthand. I truly believe that without troughs, there are no great achievements, and troughs are precisely where your resilience is proven, not only to yourself but also to everyone who cares about you.

#BreakingNews: Kaspa founder @hashdag revealed that he has met with a professional media outreach team and will begin working with them next week—is $KAS about to experience a major breakthrough? 🚀

@kasfyi By mid-October, everything had already begun to show signs.

I have a slightly different perspective on this part. The work within vprogs (especially @hus_qy and I) is well-coordinated, although it's still in a somewhat "exploratory" phase, resulting in low coupling (e.g., he's building a comprehensive cross-vprog execution runtime; I'm exploring the underlying Cairo to understand the specific forms of virtual machine instantiation). Integrating elements from previously known Sparkle implementations with vprog research concepts is indeed the harder part, and coordination is still lacking, but we're working in that direction. We had a great discussion about this yesterday on Discord and privately. I'm happy to say that the two perspectives are rapidly merging, and we share the same grand vision: building a fully composable ZK program space.

@coderofstuff_ is currently focused on the dk project, while I try my best to mentor him and review his work. The codebase is currently private, but plans are underway to open it up soon. He also participates in the daily development and maintenance of rk, which naturally takes priority over the dk project. My primary role is vprogs (including actual coding and project coordination; @CryptoAspect has also begun sharing coordination/project management responsibilities), but I also need to be involved in other areas—especially the dk project, where translating papers into practical algorithms requires my cross-disciplinary knowledge. Other tasks will be handled by others. In fact, a complete report on the work allocation is currently being written.