Recently, @boundless_xyz has been quite active, reminiscent of last year. Last year was the year I was most interested in ZK, even though it was the year of the BTC narrative. At that time, ZK still had a strong voice on BitVM (even though it was opZK 😂). Back then, @RiscZero and @SuccinctLabs took two completely different paths. R0 chose to focus heavily on applications, building a collaborative environment. Meanwhile, SP1 opted for ETH, being the first to launch a usable ZKRollup solution - RSP. To be honest, the results were significant, with multiple L2s adopting RSP or modified versions of RSP. Although R0 later followed up with ZKification of OP Layer2, it was a brief splash that quickly faded. (To be precise, the Layer2 race has ended, as everyone realized Layer2 is just a monthly $3000 SaaS.) Now, R0 and SP1 are also pursuing two distinctly different styles. Succinct has chosen to focus solely on its own brand, with the product being secondary; the priority is to establish its name. R0, on the other hand, has chosen to step back and fully support its Boundless, so most activities are now centered around Boundless. There’s not much to say about financing; these ZKVMs are all top-tier projects, and overall, they are among the fastest (of course, there are many other ZKVMs, like nexus, zkm, lita, blah blah blah, which we can discuss later). From an overall positioning perspective, Boundless actually resembles an ecological software package, encompassing a series of products from top to bottom, allowing developers to easily complete their content construction, including proof services, verification contracts on various chains, related ZK programs, execution layers, and so on. However, to put it bluntly, the main core business of R0 and SP1 still lies in the computational network they provide externally, which is also the core of ZK. Therefore, the two will engage in an arms race in the future due to the economic model and participation of this computational network. So, to be straightforward, the best way to participate in ZKVM projects is to become part of the computational network, which means running nodes (GPU nodes are more important). That said, the use cases of ZKVM still revolve around simplicity; in most cases, they are proving things that are difficult to compute on-chain, commonly involving cross-chain data reading and writing, or mechanisms like Rollup. These things feel a bit too far from consumers, and I hope there will be more scenarios closer to consumers in the future. (Perhaps RWA has a strong demand in this regard... but decentralized RWA is a bit strange in itself...) I have always found ZK to be a fascinating and interesting technology, but unfortunately, it still needs a strong wind to be recognized in the current environment. However, I remain firmly optimistic about the future of ZK (not necessarily in Web3).