The quote
functions currently hardcode the _payInLzToken
parameter to false
. This hardcoding limits the protocol's ability to adopt the ZRO token as a future fee payment method, which may be crucial considering the potential launch of ZRO in the upcoming year. According to the LayerZero integration checklist, _payInZRO
must not be hardcoded and should be passed as a parameter instead. Making _payInZRO
an input parameter will allow flexibility for future fee payments using ZRO.
By hardcoding _payInLzToken
to false
, the protocol restricts its ability to adapt to future changes in fee payment methods, specifically the adoption of the ZRO token. This limitation can lead to integration issues and restrict the protocol's flexibility in handling fees.
Pass the _payInZRO
field as an input parameter to the quote
functions to allow flexibility in future fee payments using ZRO. This change will ensure that the protocol can seamlessly accommodate ZRO as a fee payment method when it is launched.
Update the quote
functions to include _payInZRO
as an input parameter:
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.