YIP: Force YAMv2 Mitigation to YAMv3 to Keep Community Consensus United
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.
| Voter | Cast Power | Vote & Rationale |
|---|---|---|
 0x2dbF...BB99d4 | 64,352 | Specify V2 Migration Date |
 0x61db...ad8238 | 53,801 | Specify V2 Migration Date |
 0x653d...48aDa5 | 39,899 | Specify V2 Migration Date |
 0x1447...88e3BC | 37,002 | Specify V2 Migration Date |
 0x1Ec2...F1A460 | 30,814 | Specify V2 Migration Date |
VOTE POWER
Proposal Status
- Tue December 15 2020, 09:00 pmVoting Period Starts
- Fri December 18 2020, 09:00 pmEnd Voting Period
Current Results
1-Specify V2 Migration Date
348,468.558
2-Do not end V2 Migration
28,728.113