• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
CheesecakeSwapCheesecakeSwapby0x42F9bADFB084FA445965CB8006965E2c9dC2b1460x42F9…b146

About Expanding on Polygon

Voting ended over 4 years agoSucceeded

Hi All,

We’re sorry for our delayed announcement; the reason behind this delay was our extensive research after deciding to launch our Polygon branch. We’ve weighed our options here, and decided to offer our community 2 main options regarding how our Polygon branch should be opened;

1- Bridging $CCAKE Between BSC and Polygon

After our correspondence with the Polygon team, we’ve established that AnySwap is the official, and most preferred bridge platform between two networks; but after reviewing their contracts and methods, we realized AnySwap does not offer a “Mint & Distribute” style of rewarding. That is, there will be no minting on our Polygon Masterchef; so supply required for the rewards in the Polygon chain will be provided from our dev account in BSC.

As you know, we currently have a 0.75 $CCAKE / block reward in BSC, and our dev account’s share, which will be the reward distributed in the Polygon network, is 10% : 0.075 $CCAKE / block. In the Polygon network, this will amount to 2160 $CCAKE/day. Naturally; There will be no burning in BSC network, as all rewards for the dev account will be transferred into Polygon Masterchef contract for reward supply. Our dev account in Polygon Masterchef will not be getting any rewards as well.

AnySwap executes the following method of bridging;; For BSC -> Polygon: Lock $CCAKE in BSC, mint $CCAKE in Polygon, For Polygon -> BSC: Burn $CCAKE in Polygon, release locked $CCAKE in BSC.

Therefore, while BSC -> Polygon will be available, Polygon -> BSC bridge will only be available for users who used BSC -> Polygon beforehand. Here are some clarifications; A user cannot bridge from Polygon -> BSC from scratch. If a user has bridged X $CCAKE from BSC -> Polygon, then user can use Polygon -> BSC bridge for maximum X $CCAKE Therefore, there will be a direct link between $CCAKE BSC and $CCAKE Polygon, which allows one token and different block rewards on both networks.

For this option, there is something we like to add; despite being the official bridge platform in Polygon network, AnySwap is not ensuring 100% transaction success for their bridge services as they are still offering their Beta Version currently. However, it is also important to mention that AnySwap has not encountered any transaction malfunction or security breach yet.

Nevertheless, as CheesecakeSwap, we have always put security first and operated on a “simple but secure” approach. Although we believe this is a viable option, we’re sorry to say that we will not be accepting any responsibility in case of a transaction error, contract-wise security breach etc. on AnySwap’s part. As always, we recommend to DYOR, and use this bridging service at your own risk, if this option is preferred.

2- Launching a Separate Project in Polygon

In this option, we will be launching a new, separate project in Polygon. Our contracts ( Token, Masterchef and Timelock) will be identical code and structure-wise. We will be creating a new token, $PCCAKE, for the Polygon network. There will be no link between $CCAKE in BSC, and $PCCAKE in Polygon. After launch, the general state will be as follows;

Block rewards will be higher compared to $CCAKE, Initial Supply will begin from 0, Naturally, TVL will be 0 as well, so high APRs, There will be no link between BSC $CCAKE.and Polygon $PCCAKE, Since Polygon $PCCAKE is a new launch, it will have higher rewards & APRs, Because of the listed issues above, BSC $CCAKE will have a lower priority in the beginning and Polygon $PCCAKE will be more preferable..

Fair launch strategy will be assumed in both options. Launch date / Block number will be announced accordingly, after poll results.

Off-Chain Vote

Bridging Between BSC and Polygon
168.09K 88.7%
A Separate Project on Polygon
21.48K 11.3%
Download mobile app to vote

Timeline

Jul 03, 2021Proposal created
Jul 03, 2021Proposal vote started
Jul 06, 2021Proposal vote ended
Oct 26, 2023Proposal updated