Read on Twitter
Glad @oli_vdb brought this up $YFII didn’t fall into this “bug” from the very beginning so better to clarify here
Since it’s a contract design by @jin_asac, that’s why other clones simply fork the code without reading through the logic didn’t realize
Here is how
https://twitter.com/oli_vdb/status/1290370855709573122
Since it’s a contract design by @jin_asac, that’s why other clones simply fork the code without reading through the logic didn’t realize
Here is how
https://twitter.com/oli_vdb/status/1290370855709573122
When it comes to staking contract the contract needs to be initialized before the set time
Clones didn’t notice this logic and let the contract start staking right away which causes the issue
In $YFII case, initialization was done before the staking start time as below
1/
Clones didn’t notice this logic and let the contract start staking right away which causes the issue
In $YFII case, initialization was done before the staking start time as below
1/
The initialization call for contract which staking starts on UTC+8 7/27 0:00 was done before the start time (etherscan log on the left)
Another initialization was also done before the staking started on UTC+8 7/28 0:00
Most devs for the case or $YFII are not active on CT, will try my best to bridge the gap here
please throw your findings, thinkings onto forum, telegram, discourse and wechat where community memebers are active and where most first hand info served
please throw your findings, thinkings onto forum, telegram, discourse and wechat where community memebers are active and where most first hand info served
