#KAS The Kaspa core team is working hard to convey the message of Kaspa and coordinate the community to work on products that can reflect its fundamentals. We welcome feedback and will seek a better balance between depth work and continuous communication.

As long as our platform continues to develop, the responsibility of shaping its narrative falls on its builders. The core team implies the narrative in architectural decisions and feature selections, as they suggest the product—whether as the L1 of the product or the default nature of L2 applications. Therefore, the core members are the ones who first understand and can clearly articulate this narrative. The rules of the crypto space—especially in infrastructure projects, as far as I know, without exception—are that core developers and researchers drive the dissemination of information, whether they want to or not, and whether they are good at it or not. A very simple example: when Bitcoin Core decides to keep blocks small and slow, they (hopefully) understand that they are replacing the agenda of "digital gold" with that of "electronic cash."
The community conveys information through its creativity and diversity; and the information itself is created by products, that is, by the builders of the products. Building infrastructure is both a privilege and a form of self-torture, which is not fun—until we make it to the finals.