# Share to Earn Earning fungible token rewards has traditionally required that you hold on to the assets that provide rewards, or that you stake the assets in a pool for a given period of time. There is no real reason this HAS to be the case, outside of limiting what is available on the secondary markets. We do not have these issues by design.\ \ Sharing tokens was the original point, so you will be rewarded for the fucks you give. Sharing and staking are the two easiest ways to earn $connect. Each method has a different multiplier on your earnings. A quick example:\ \ Tokens have a multiplier each time they are shared to instantly earn your $connect. This math is not final, but envision each token has a life (amount it can earn being shared). The first time a token is shared, it has a 1.25x multiplier on $connect, which then decreases (ultimately to 0) each subsequent share. \ \ \&#xNAN;*Credentials mints a token, and sends to Brewer. This send earns 1.25x baseline earnings and* Credentials is paid out on the share. Brewer decides to also share, but is now only eligible to earn 1.0x baseline rewards. A tokens earnings potential will be fully depleted after a select amount of shares. These figures will be released closer to the deployment of the tools. --- # 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://enlightenmint.gitbook.io/enlightenmint-whitepaper/the-whitepaper/fungible-token/share-to-earn.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.