The project is designed to unlock tokens based on time. And it will also be deployed on L2. In L2, time is not completely determined, and time offsets of several hours may affect users with shorter lock times.
For example, in Arbitrum, there is a description of time offset.
If user A reaches an agreement with user B, A pays B after 5 hours of locking. When the real time reaches 5 hours later, due to the time characteristics of L2, the time on the chain may not reach 5 hours later. At this point A cancels the payment, but B may have completed his work and B suffers a loss. The same situation may also allow B to receive payment in advance due to time characteristics. causing losses to A.
L2’s time characteristics may cause users to lose assets
manual
It is recommended to limit the shortest lock time to prevent losses caused by normal L2 time offset.
https://docs.codehawks.com/hawks-auditors/how-to-determine-a-finding-validity
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.