The previous article about ZK received quite a bit of feedback, and I didn't expect everyone to have similar confusions. To be honest, there are no shortcuts to understanding the technology; spending more time pondering will gradually lead to comprehension.

Currently, there are many projects in the ZK space. Just looking at official promotions, they are all labeled as "high performance, low cost," which can really lead to aesthetic fatigue over time. But to truly distinguish the differences between these projects, you need to start from their technical architecture.

For example, solutions like client-side proving transfer the computational load to the client, which is completely different from traditional server-side verification approaches. Recently, I delved into this and found that different ZK projects have quite significant implementation differences in this area—some focus on throughput, some prioritize proof speed, and others put effort into developer friendliness.

So the question is: how can we categorize these ZK projects based on their actual technical characteristics rather than marketing slogans? This is something worth sorting out carefully.