Relevant link - https://github.com/Cyfrin/2024-07-templegold/blob/main/protocol/contracts/templegold/TempleTeleporter.sol#L43-L58
TempleTeleport don't have functionality to provide user a flexible approach to use ZRO
token as fees in future (that could be introduced soon as token is live already). Currently it's set to use native gas only, as ZRO
amount is hardcoded to 0.
Layerzero provides users a option to use either eth or zro
as fees for bridging. This is essential for future implementation when zero token is integrated by layerzero protocol with given V2 endpoints. Using layerzero token as fees, might be beneficial in future, than native eth.
However, if you check the highlighted line MessagingFee(msg.value, 0)
, it hardcode the ZRO token amount to 0. Means users won't be able to use zro token as fees in future, even if it's introduced by the layerzero.
It doesn't affect the protocol, although users may miss the opportunity to use ZRO token as fees in future.
Manual Review
Consider, having a input for ZRO token amount, so whenever it goes live users can use it.
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.