• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
PanicSwapPanicSwapby0x1B5b5FB19d0a398499A9694AD823D786c24804CC0x1B5b…04CC

Introducing PanicSwap Improvement Proposal - 2

Voting ended about 4 years agoSucceeded

On the eve of our PanicSwap AMM launch we come to our growing community with a further proposal key to the ongoing token structure of our platform.

Community input from PanicSwap Improvement Proposal - 1 has determined emissions will reduce to 0.6 PANIC per block on launch of our AMM (down from the current 1.0 PANIC per block for the ‘10 days of Panic!’ initial distribution event).

This improvement proposal is centred around further emissions of the PANIC token, over time, once our next generation Automated Market Maker is live.

As per our first improvement proposal around token emission, all defi users would know that the balance of token emissions is important. This is the delicate balance between incentivising liquidity while still passing value onto holders.

Being able to emit a token helps drive liquidity and trading volume to the platform, resulting in rewards being passed onto our token holders and community. Throttling this emission reduces inflation, increasing scarcity of the token as well.

On launch of our AMM, PANIC emitted is vested, while vested it has several value accrual mechanics. Accessing vested PANIC prior to the conclusion of the vesting period, results in a 50% tax. This tax is then rewarded to vested holders, encouraging lockup of tokens and value share to these stakers.

Current PANIC emissions are set at 1 PANIC per block (around 1 PANIC per second, as Fantom blocktime ~ 1 second).

This proposal is for the gradual reduction of PANIC per block emissions from launch of our AMM over our first 2 year period.

Off-Chain Vote

No reduction on emissions
984.25 0.1%
0.6 per second to 0.4 per second
201.53 0%
0.6 per second to 0.3 per second
63.8K 8.6%
0.6 per second to 0.2 per second
679.28K 91.3%
Download mobile app to vote

Timeline

Feb 12, 2022Proposal created
Feb 12, 2022Proposal vote started
Feb 13, 2022Proposal vote ended
Oct 26, 2023Proposal updated