We recently announced the formation of the Common Knowledge Base Association, or CKBA. Naturally, there are questions. Why are we doing this? What are our plans? What does this mean for CKB? We’ll answer all of these in time. But before we do, it’s worth clarifying something important: These questions are loaded with assumptions about CKB and our relationship to it. The confusion is understandable. Somewhere along the way, the industry became comfortable treating blockchains like products—operated by companies. CKB is not that. CKB is public infrastructure—maintained and advanced by people who share a common set of ideas. Like Bitcoin, it is not dependent on, owned by, or controlled by any one entity. And that includes us. We’re old school; to us, a blockchain that can be halted, reorged, restarted, or have its assets seized by a controlling entity is not a blockchain. It may be marketed as one, it may be treated as one, the market may even believe it is one. But not us. To us, decentralization, security, immutability, and permissionlessness are non-negotiable. They are what make blockchains blockchains; everything else is a glorified database. So when we say that “CKBA is the new coordination layer for the CKB ecosystem,” we mean something that may surprise many people. Heavily inspired by Bitcoin, CKB is based on Nakamoto consensus. And, in Nakamoto consensus-based systems, there’s no (need for) coordination. They still produce order, but that order emerges from the behavior of independent and free entities that pursue their own incentives by following an optimal strategy introduced by the system’s constraints. In simple terms, CKB doesn’t need CKBA. The system works because everyone minds their own business, and everyone minds their own business because the system works. We have no control over that. CKBA operates somewhere else entirely: at the social layer. Our role is not to govern CKB; it’s to support the diverse and decentralized ecosystem of contributors around it. To coordinate resources, improve communication, support contributors, and help aligned people find each other. We’re a group of cypherpunks and misfits defined, perhaps most of all, by low time preference. This has its downsides—and it’s unfortunate that this has become a contrarian position—but for better or worse, we can’t help ourselves. We’re painfully aware that we’re building public infrastructure that should outlive us. And we’re not the only ones building. We have our vision and all, but we’re not calling the shots. If you don’t like our vision, impose your own. Build on CKB. Who’s stopping you? CKB will keep ticking, block by block, from one state transition to another, whether we’re here or not. Whether we, or you, approve of it or not. And if you are aligned with our vision, join us 👇 ckba.build/

One intriguing parallel could be investing in decentralized AI infrastructure, like open-source models or compute tokens (e.g., projects akin to Bittensor). It's still niche, dismissed by many as hype, but could explode with AI's growth. Another: quantum-resistant cryptography tech, undervalued amid rising quantum threats. Always DYOR—high risk, like early BTC. What's your take?