# Introduction ## 1.1 Why we built Solyx Solana is fast. Tokens move quick. But trust isn't there. Every day wallets fly in and out of launches and dumps, but none of that history sticks around. One wallet fades into the next. There’s no memory onchain. No way to tell who’s really building and who’s just circling for exit liquidity. We change that. No names (if you want to remain anonymous), no IDs, no KYC. Just behavior. We track what wallets do, not what they say they are.\ \ Onchain ecosystems are decentralized, but not necessarily trustworthy. Wallets blend into each other. Protocols can’t spot long-term contributors from short-term extractors. Bots and sybils game every system they touch, and pseudonyms offer zero nuance. \ \ We built Solyx to change that. To give chains the memory they’ve been missing. Instead of trying to enforce real-world identity, we focus on what wallets *do* over time. It scores behavior, tags patterns, gives the community tools to call things out or vouch things up.\ \ It’s coordination without compromise. Signal without surveillance. Trust built on actions, not assumptions, without sacrificing decentralization. *** ## 1.2 Vision & Mission Solyx envisions a future where pseudonymous onchain identities can earn credibility through action, not affiliation. Our mission is to create an open, modular system for surfacing trustworthy wallet behaviors and mitigating sybil or malicious actors without sacrificing decentralization. We believe: * Reputation should be earned * Trust should be composable * Transparency should be the norm Solyx seeks to make reputation programmable. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://solyx.gitbook.io/solyx-docs/introduction-1.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.