• © Goverland Inc. 2026
  • v1.0.5
  • Privacy Policy
  • Terms of Use
YamYamby0xbdac5657eDd13F47C3DD924eAa36Cf1Ec49672ccfeddas.eth

YIP: Force YAMv2 Mitigation to YAMv3 to Keep Community Consensus United

Voting ended about 5 years agoSucceeded

This is repost of @DaddyPig's post because of snapshot error.

=== Basic Summary/Abstract ===

https://forum.yam.finance/t/force-yamv2-mitigation-to-yamv3-to-keep-community-consensus-united/772

My proposal has positive poll. I try again. YAMv2 and YAMv3 are separated from each other, they are confusing. People buy V2 by mistake and lose money. This is not good for Yam. It is better we stop V2 and only focus V3.

This proposal is to bring users YAMv2 into YAMv3 so we have consensus. Consensus is important for future of Yam. We give Yamv2 time and let everyone know that we want to bring V2 into V3.

=== Motivation === Make Yam Community Consensus United Again!

=== Risks === The very little risk for yam community, the benefit is we could keep the YAM consensus a ONE, not two.

=== Specifications === YAMv2 to mitigate to YAMv3, team should specify a final date.

Off-Chain Vote

Specify V2 Migration Date
348.47K 92.4%
Do not end V2 Migration
28.73K 7.6%
Download mobile app to vote

Timeline

Dec 15, 2020Proposal created
Dec 15, 2020Proposal vote started
Dec 18, 2020Proposal vote ended
Apr 28, 2024Proposal updated