# Use Cases ### Subscription Payments, Rewards, & Governance $SP is not just a token—it is the economic foundation of Silent Pass. Every user interaction within the network strengthens the ecosystem, making $SP an essential component of Silent Pass’s long-term success. 🔹 Use Case #1: Subscription Payments Traditional VPNs require fiat payments—which means exposing credit card details, personal information, and banking data. This is a major privacy risk for users who need anonymity the most. ✔ Silent Pass eliminates this issue by allowing users to pay for VPN & Proxy services with $SP. ✔ No credit cards, no centralized payment processors—just pure, anonymous transactions. ✔ Seamless integration with CoNET Chain and Solana for decentralized payments. \ 💡 Example: A Silent Pass user in a censorship-heavy country needs complete privacy. They don’t want to reveal their identity by paying with a traditional bank account. By using $SP, they purchase a Silent Pass subscription completely anonymously, avoiding government tracking. *** 🔹 Use Case #2: Governance & Community Voting Silent Pass operates as a decentralized, community-driven network. Instead of decisions being made by a central company, $SP holders can vote on future upgrades and ecosystem developments. ✔ Decentralized governance ensures no single entity controls Silent Pass. ✔ Users propose and vote on network improvements. ✔ True Web3 principles—where privacy advocates shape the future of online security. \ 💡 Example: Silent Pass users vote on whether to integrate new privacy-enhancing features into the network. $SP holders participate in governance proposals, ensuring that the community directs the project’s future. --- # 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://docs.silentpass.io/usdsp/use-cases.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.