JAMON Tokenomics
Emission rate
Per block
| Metric | Emission/block (JAMON) | Emission/day (JAMON) |
|---|---|---|
Emission | 40 | 1,152,000 |
Burned Weekly | -25.75 | -787,600 |
Effective Emission | <14.25* | 364,400* |
*Effective Emission is in fact slightly below this amount: an additional 45,000 JAMON per day is diverted from the amount allocated to the lottery, and burned (PID 137 - Details below).
In addition to the above, a dynamic amount of JAMON is also minted to the Dev address at a rate of 9.09%. This means that if 100 JAMON are harvested, then 9.09 JAMON is minted in addition and sent to the Dev Address.
All JAMON minted to the Dev address is burned in the weekly burn and never enters circulation.
As such, we haven't included it in the above emission rate.
Distribution
| Distributed to | Reward/block (% of emission) | Reward/block (total JAMON) | |
|---|---|---|---|
Farms and Lottery | 10.62% | 4.25 | 122,400 (approx) |
Which diverted and burned | -46,000 | ||
Jamon Pools | 25% | 10 | 288,000 (approx) |
Total Daily JAMON Emission | 364,400 (approx) |
Other Deflationary Mechanics
As well as the above, JAMON is also burned in the following ways:
0.05% of every trade made on JamonSwap V2.
100% of JAMON sent to the Dev address.
100% of JAMON performance fees from IFOs.
100% of JAMON spent on Profile Creation and NFT minting.
100% of JAMON bid during Farm Auctions.
20% of JAMON spent on lottery tickets.
45,000 JAMON per day (historically assigned to the lottery) (The JAMON for this is generated by a farm - PID 137).
3% of every Prediction markets round is used to buy JAMON for burning.
2% of every yield harvest in the Auto JAMON Pool.
2% of every NFT sale on the NFT Market is used to buy JAMON for burning.
Why is the JAMON burn manual?
o hit the ground running, JamonSwap launched as an MVP (minimum viable product) with the Cutter Professional contract emitting 40 JAMON per block. For that reason, the early team didn't add additional functions such as the ability to customize the JAMON minting logic. As migrating to a new Cutter Professional would require a lot of time and effort, the team opted to reduce JAMON emissions instead through a manual burn process by creating two pools:
Burn Pool (PID - 137) - burned JAMON per block.
On the day of the burn, the supply shown on the homepage might suddenly jump by several million JAMON.
Don't worry - THIS JAMON NEVER ACTUALLY ENTERS CIRCULATION:
This apparent jump is just because of how all the JAMON that's allocated for the burn is stored during the week.
The JAMON sent to both pools PID-137 are harvested before completing the weekly token burns, and this makes the Total Supply shown on the site jumping by ~6M. This is because pending JAMON isn’t registered in the Total Supply until it's harvested on the burn day. Once the token burn transaction is completed, the ~6M is shown in the Burned to Date.
How to Confirm JAMON Supply for yourself
To confirm that the circulating JAMON supply shown on the JamonSwap homepage is correct.
Head to the JAMON token contract on PolygonScan and see how much JAMON is held by the Burn Address. That's the total amount of JAMON that's been burned (removed from circulation FOREVER, and impossible to ever retrieve).
Then, subtract this burned amount from the "Total Supply" that PolygonScan shows.
This gives you the actual JAMON supply.
Last updated