Conversation
…reator contract size
gzeoneth
left a comment
There was a problem hiding this comment.
still think the fee toggle just add complexity without good usecase
| address masterVaultRoles, | ||
| address masterVaultBeaconProxyFactory |
There was a problem hiding this comment.
breaks CREATE2-like deterministic deployment behavior as these new param are not part of _getL1Salt and _getL2Salt; we should consider to deploy these contract in the factory instead of taking untrusted input
| * @title Layer 1 Gateway contract for bridging standard ERC20s with YBB enabled | ||
| * @notice Escrows funds into MasterVaults for yield bearing bridging. | ||
| */ | ||
| contract L1YbbERC20Gateway is L1ERC20Gateway { |
There was a problem hiding this comment.
L2 token created with underlying token decimals, but MV share have +6 decimals and L2 token represent MV share instead of underlying so we need to adjust somewhere
| /// - Set the rebalance cooldown | ||
| bytes32 public constant GENERAL_MANAGER_ROLE = keccak256("GENERAL_MANAGER_ROLE"); | ||
| /// @notice The fee manager can: | ||
| /// - Toggle performance fees on/off |
There was a problem hiding this comment.
Consider to take this away from FEE_MANAGER_ROLE because the current implementation allow reseting the high water mark by toggling the fee off and on. If the fee manager can temporally manipulate sub-vault price it can drain the vault too.
| .mulDiv(1e18, totalSupply(), MathUpgradeable.Rounding.Up) | ||
| ); | ||
| } else { | ||
| _distributePerformanceFee(); |
There was a problem hiding this comment.
this can revert (if subvault.withdraw revert), preventing disabling fee when subvault have withdrawal paused
|
|
||
| __ReentrancyGuard_init(); | ||
| __Pausable_init(); | ||
| __MasterVaultRoles_init(); |
There was a problem hiding this comment.
local roles are not initialized and no one have local default admin role to grant roles
| * @title Layer 1 Gateway contract for bridging Custom ERC20s with YBB enabled | ||
| * @notice Escrows funds into MasterVaults for yield bearing bridging. | ||
| */ | ||
| contract L1YbbCustomGateway is L1CustomGateway { |
There was a problem hiding this comment.
Lack fee token (Orbit) variant, same for the L1YbbERC20Gateway
| uint256 totalAssetsUp = _totalAssetsLessProfit(MathUpgradeable.Rounding.Up); | ||
| uint256 totalAssetsDown = _totalAssetsLessProfit(MathUpgradeable.Rounding.Down); | ||
| uint256 idleTargetUp = | ||
| totalAssetsUp.mulDiv(1e18 - targetAllocationWad, 1e18, MathUpgradeable.Rounding.Up); | ||
| uint256 idleTargetDown = | ||
| totalAssetsDown.mulDiv(1e18 - targetAllocationWad, 1e18, MathUpgradeable.Rounding.Down); | ||
| uint256 idleBalance = asset.balanceOf(address(this)); |
There was a problem hiding this comment.
inconsistent use of _totalAssetsLessProfit and asset.balanceOf(address(this))
There was a problem hiding this comment.
can you explain more what you mean? i'm not sure i follow
There was a problem hiding this comment.
we're changing rebalancing to include profit assets too fwiw
There was a problem hiding this comment.
| if (idleAssets < assets) { | ||
| uint256 assetsToWithdraw = assets - idleAssets; | ||
| // slither-disable-next-line unused-return | ||
| subVault.withdraw(assetsToWithdraw, address(this), address(this)); |
There was a problem hiding this comment.
also lack subvault slippage check tho idk what is a good fix
There was a problem hiding this comment.
one of the assumption we have here is subvault should be erc4626 compliant, which require subvault.withdraw() to transfer exactly the requested assets a nd if a subVault misbehaves safeTransfer method on the next line would revert anyway
| /// @notice Set the target allocation of assets to keep in the subvault | ||
| /// @dev Target allocation must be between 0 and 1e18 (100%). | ||
| /// @param _targetAllocationWad The target allocation in wad (1e18 = 100%) | ||
| function setTargetAllocationWad(uint64 _targetAllocationWad) |
| onlyGateway | ||
| returns (uint256 shares) | ||
| { | ||
| shares = _convertToSharesRoundDown(assets); |
There was a problem hiding this comment.
imo we should implement an optional slippage check in the gateways
we could pass it by repurposing extraData which would leave the existing function signature unchanged. we could also introduce a new function which is probably a bit better
godzillaba
left a comment
There was a problem hiding this comment.
still reviewing just wanted to leave early comments
| MasterVaultRoles _rolesRegistry = new MasterVaultRoles(); | ||
| _rolesRegistry.initialize(_admin); | ||
| rolesRegistry = _rolesRegistry; |
There was a problem hiding this comment.
the roles registry should be behind a Transparent proxy
| l1Deployment.standardGateway = ybbResult.standardGateway; | ||
| l1Deployment.customGateway = ybbResult.customGateway; | ||
| } else { | ||
| // Delegate standard gateway deployment to library |
There was a problem hiding this comment.
i feel like we might be able to rework this external lib to make this diff easier to verify.
i wonder if we could simply copy paste all the existing code into a single external library function instead of breaking it up?
There was a problem hiding this comment.
like copy-paste all createTokenBridge method into the ext lib? it was a challenging task to move some of this logic out of this contract while trying to reduce the diff. first I tried to have only ybb related stuff to be in the ext lib but then I ran into stack too deep issues. so I decided to move the deployment logic into that library
| function _setMasterVaultFactory(address _masterVaultFactory) internal { | ||
| require(_masterVaultFactory != address(0), "BAD_MASTER_VAULT_FACTORY"); | ||
| masterVaultFactory = _masterVaultFactory; | ||
| } |
There was a problem hiding this comment.
bit of a nit, but even though it's a sortof convention in this codebase idk if an address(0) check is very useful
if we keep it though i think it should inlined in the initializer
| uint256 prevBalance = IERC20(_l1Token).balanceOf(address(this)); | ||
| IERC20(_l1Token).safeTransferFrom(_from, address(this), _amount); | ||
| uint256 postBalance = IERC20(_l1Token).balanceOf(address(this)); | ||
| amountReceived = postBalance - prevBalance; | ||
|
|
||
| address masterVault = IMasterVaultFactory(masterVaultFactory).getVault(_l1Token); | ||
| IERC20(_l1Token).safeIncreaseAllowance(masterVault, amountReceived); | ||
| amountReceived = IMasterVault(masterVault).deposit(amountReceived); | ||
| require(amountReceived > 0, "ZERO_SHARES"); |
There was a problem hiding this comment.
this code is copy pasted a few times, it's probably better to separate this out into a lib or inherited contract or something
| onlyGateway | ||
| returns (uint256 shares) | ||
| { | ||
| shares = _convertToSharesRoundDown(assets); |
There was a problem hiding this comment.
imo we should implement an optional slippage check in the gateways
we could pass it by repurposing extraData which would leave the existing function signature unchanged. we could also introduce a new function which is probably a bit better
| if (idleAssets < assets) { | ||
| uint256 assetsToWithdraw = assets - idleAssets; | ||
| // slither-disable-next-line unused-return | ||
| subVault.withdraw(assetsToWithdraw, address(this), address(this)); |
There was a problem hiding this comment.
yeah imo this is okay, could use some documentation though
| // L1 logic contracts shared by all token bridges | ||
| L1Templates public l1Templates; | ||
|
|
||
| YbbL1Templates public ybbL1Templates; |
There was a problem hiding this comment.
let's move this to the end so we don't shift the storage layout
| /** | ||
| * @notice Set addresses of YBB L1 logic contracts (standard, custom, fee-token-based, and vault templates). | ||
| */ | ||
| function setYbbTemplates(YbbL1Templates calldata _ybbL1Templates) external onlyOwner { |
There was a problem hiding this comment.
i think this should be part of the main setTemplates so it isn't forgotten about
This reverts commit 9654a8f.
a full feat branch for yield bearing bridge, this PR replace #126 & #118