-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgraded Q -> 2 from #57 [1716796622913] #597
Comments
@jatinj615, please review. Full text of the issue here. |
Hey @alcueca I believe this is invalid The
function _recoverBridgeFee() internal {
uint256 feeCollected = bridgeFeeCollected;
bridgeFeeCollected = 0;
// transfer collected fee to bridgeSweeper
uint256 balanceBefore = address(this).balance;
IWeth(address(depositToken)).withdraw(feeCollected); // <--- depositToken is always WETH
feeCollected = address(this).balance - balanceBefore;
(bool success, ) = payable(msg.sender).call{ value: feeCollected }("");
if (!success) revert TransferFailed();
emit SweeperBridgeFeeCollected(msg.sender, feeCollected);
} Therefore the warden's claim that this function will revert if the In
|
From document link, it mentioned that 'The xRenzoDeposit contract mints $ezETH tokens in response to wETH or LST deposits'. So deposit token can be other token address to be able to interact with LSTs. |
On L2s, only WETH and ETH deposits are supported. For the L2s where ETH is not native. For ex - BSC, the contract just sends the collected WETH to sweeper instead of WETH::withdraw. |
This auto-generated issue was withdrawn by alcueca |
alcueca marked the issue as grade-b |
Downgrading to QA, and the sponsor should be clearer in the intention of the code. |
Judge has assessed an item in Issue #57 as 2 risk. The relevant finding follows:
3, Fee are not able to be claimed in xRenzoDeposit when aassset is not WETH
The text was updated successfully, but these errors were encountered: