• © Goverland Inc. 2026
  • Privacy Policy
  • Terms of Use
PangolinPangolinby0xFd7b8597cF8eE5317439B0B5C55a111F6Eec449D0xFd7b…449D

Permanently Disable Migrator

Voting ended about 4 years agoSucceeded

What does the "migrator" function do?

A common problem in DeFi is a seamless migration when token upgrades or contract replacements happen. Often rewards for the previous farm will end and continue at another farm. Users will want to migrate to this new farm, but might not be aware of this happening or how to move. The "migrator" function would handle this for users automatically and instantly. Many auto-compounders have functionality like this providing a great user experience.

Dangers of the function

The "migrator" function moves funds from one farm to another location. This location is intended to be a replacement farm, but malicious owners could use the function to steal funds. Only the Pangolin multisig can execute this function which provides some security that enough multisig members won't collude. Another risk is that the function would be used incorrectly leading to lost funds.

Benefits of the function

When a migration event happens in the future, Pangolin can automatically and instantly migrate all farms to ensure a seamless transition of farming rewards for all stakers.

What would changing?

Pangolin will no longer have the ability to automatically migrate staked funds. We would still provide a migration UI to walk users through the process should a scenario like this happen.

Clarification

The "migrator" function being discussed in this proposal is totally separate from the migrate prompt and UI in Pangolin's app currently. That UI walks users through the multiple transactions required to migrate farms themselves when required.

Technical Proposal

We will call disableMigrator() on MiniChefV2 permanently disabling the migrator functionality.

Off-Chain Vote

For
346.49K 80.7%
Against
15.92K 3.7%
Abstain
66.97K 15.6%
Download mobile app to vote

Timeline

Dec 15, 2021Proposal created
Dec 16, 2021Proposal vote started
Dec 23, 2021Proposal vote ended
Oct 26, 2023Proposal updated