# Tokenomics

$SHARE's tokenomics on the Solana blockchain allocated 80% of the token supply to the Liquidity Pool and 20% to the Impact Fund.

The Impact Fund unlocks 5% of its holdings at every market cap milestone (outlined below).
For every market cap milestone, a new SHARE impact fund is raised, and via a democratic voting process the $SHARE community chooses which entity/entities will receive the funding.

Given the exponential growth factor pacing the market cap milestones (r = 1.618, the golden ratio) and the constant fractional dilution factor of the Impact Fund (5% of tokens left in the pool), the pool will never run out of tokens; the $SHARE funding protocol will last forever.
While the amount of tokens liquidated at each milestone will decrease, their value will always be higher than the last and the impact on token price continuously diminished. The parameters that dictate the market cap milestones and the dilution rate of the fund have been chosen to respect a mathematical harmony that avoids exponential decay and unnecessary pressure on the token’s price. This balance also guarantees the project’s longevity by virtue of mathematical relations that will be sustained towards infinity. The table below showcases the fund’s behavior in detail throughout the various stages of growth:

| Fund # | Market Cap ($) | Amount (Tokens) | Remaining Tokens | Token Price ($) | Fund Size ($) |
| ------ | -------------- | --------------- | ---------------- | --------------- | ------------- |
| 1      | 1,000,000      | 100,000,000     | 1,900,000,000    | 0.0001          | 10,000        |
| 2      | 1,618,000      | 95,000,000      | 1,805,000,000    | 0.0002          | 15,371        |
| 3      | 2,617,924      | 90,250,000      | 1,714,750,000    | 0.0003          | 23,627        |
| 4      | 4,235,801      | 85,737,500      | 1,629,012,500    | 0.0004          | 36,317        |
| 5      | 6,853,526      | 81,450,625      | 1,547,561,875    | 0.0007          | 55,822        |
| 6      | 11,089,013     | 77,378,094      | 1,470,183,781    | 0.0011          | 85,805        |
| 7      | 17,942,013     | 73,509,191      | 1,396,674,591    | 0.0018          | 131,890       |
| 8      | 29,030,175     | 69,833,731      | 1,326,840,860    | 0.0029          | 202,729       |
| 9      | 46,970,820     | 66,344,204      | 1,260,496,655    | 0.0047          | 311,614       |
| 10     | 75,987,900     | 63,024,983      | 1,197,471,672    | 0.0076          | 478,982       |
| 11     | 122,966,000    | 59,873,684      | 1,137,597,988    | 0.0123          | 736,243       |
| 12     | 198,959,000    | 56,880,019      | 1,080,717,969    | 0.0199          | 1,131,679     |
| 13     | 321,915,662    | 54,036,018      | 1,026,681,952    | 0.0322          | 1,739,504     |
| 14     | 520,859,700    | 51,334,098      | 975,347,854      | 0.0521          | 2,673,791     |
| 15     | 843,750,900    | 48,767,393      | 926,580,461      | 0.0844          | 4,109,885     |
| 16     | 1,365,188,956  | 46,329,123      | 880,253,337      | 0.1364          | 6,317,304     |
| ...    | ...            | ...             | ...              | ...             | ...           |

The Impact Fund, containing 20% of the tokens in circulation, has been distributed equally across 20 different multi-sig wallets, each containing 1%. This token distribution across several wallets aims to increase security for the community funds. These wallets will be diluted exactly as outlined in the chart above.

For the sake of constant transparency, below you’ll see a list of the 20 wallets that are holding the tokens in the Impact Fund:

| Impact Fund Wallets | Wallet Address                               | $SHARE token balance |
| ------------------- | -------------------------------------------- | -------------------- |
| 1                   | 4RezHNgPaCzdatkdSyrUqs4PYZrMDBCof7gNx7weSm9M | 100,000,000          |
| 2                   | DYZgjCy689fErVpdZgy3mPZxyoM6vnxTYyN3QZvCAavC | 100,000,000          |
| 3                   | BmiGzGzo6by1i1Bm9KsDWSJ6geVyJM1XJVHWuQLWZw3A | 100,000,000          |
| 4                   | D2aLQFMUTvUBffDMD6VX8qinviwBFEZyLvx1dsqbg4Qi | 100,000,000          |
| 5                   | 3QR1s8ARejeA4YuwdVZ1ZiFfUiGD4ZR3HnzUzPcqK4fr | 100,000,000          |
| 6                   | 8YbyHr7eoVFX4hLSFN32zkUWzoZ4kLgPywB212rvczqf | 100,000,000          |
| 7                   | 7zRstgfh3fEwZecfyj4jqDYwWn3eYvQf26gjuq717xHb | 100,000,000          |
| 8                   | DQBhxBTL4PzHumNS7Vk9mEz2DijvivKV1QbGRGHuCqdX | 100,000,000          |
| 9                   | 8mb9vfnskowuLFJuZEEiRBAJWDc62FLF7hoz7nbewU8t | 100,000,000          |
| 10                  | HuDzxtEqRbozot7GFSSADXCMR7TY5LVJLVDVC6863QyX | 100,000,000          |
| 11                  | QGwKSkKEfN2QigtkSzzjxgaM6ga5khA3bG5cjt7u429  | 100,000,000          |
| 12                  | 88MfEEhri5X4R9E1jPD9z9t6x8PbXCZjLGvk2RL7TQFU | 100,000,000          |
| 13                  | HXFLFjNEdHUHnN8Eszpx7gcA3HL3sELJp2Dy9LBXBY9G | 100,000,000          |
| 14                  | bRL8Z39Sg55oqN9zJiN271f4UaWXroZw9V8V121goRM  | 100,000,000          |
| 15                  | 9B9YnmumgYq16TiV9K7jvZGrgGNgYQYp9ZgwBaThsh9X | 100,000,000          |
| 16                  | 6rs9UzpZvwqZf5kwQ8EaBYBqXTrNCa945quSdmGQyM3Z | 100,000,000          |
| 17                  | 9XrD7hxcpvfQXsxLdTqQovETrZMnf47oHP5agvvQrFwN | 100,000,000          |
| 18                  | B8UxYGmYk5jjsShX9zvpocApGirrs5M3bZQwAToDvoWo | 100,000,000          |
| 19                  | ArE4MXxL7Kw8Pb7Lsp5qB6s2D3wg1VUD8v6xua4UNXwQ | 100,000,000          |
| 20                  | 75w9oPhQZZEvW2rDUUe2Bj5wabUnFBYnXzv5NS6p4ekd | 100,000,000          |


---

# 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://sharefoundation.gitbook.io/whitepaper/usdshare-tokens/usdshare-on-solana/tokenomics.md?ask=<question>
```

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.