# Community Codes and Operator Incentives A unique feature in HyperFlash is the concept of **Community Codes**. Once validators are onboarded, they become eligible to receive a community code – a kind of referral code or identifier that they can share with their own community or delegators. If a user stakes through that code (meaning the stake transaction carries that code as metadata), HyperFlash will **directly delegate that user’s stake to the corresponding validator**. This gives operators a direct way to increase their stake by rallying their supporters to stake via their code. Additionally, HyperFlash may allocate a bonus: a portion of the global pool that is not assigned via direct codes could be split among code-using operators proportional to how much they attracted. This system creates a powerful incentive alignment: * Validators are encouraged to promote HyperFlash (because any user they bring in bolsters their own node’s stake and rewards). * Users might be incentivized (perhaps via promotions or just by supporting their favorite operator) to use a specific code, knowing it helps a trusted validator get more weight. * Users earn points and additional MEV profits without losing any yield to commissions. This is a direct upgrade over delegating directly with a validator. * However, it doesn’t compromise decentralization or security because **all operators still must meet performance standards**. Even if an operator brings in a lot of stake, if they fail to perform, they can lose their spot. The community code feature is permissioned – only officially onboarded validators get codes, so unknown or unvetted parties can’t siphon stake away from the main pool. --- # 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.hyperflash.xyz/staking/staking-docs/community-codes-and-operator-incentives.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.