There's a strategy at 0x016919386387898E4Fa87c7c4D3324F75f178F12 currently used in the USDT 0.4.3 vault on Ethereum that reverts when its name function is called. Looking at the strategy's code I see:
That is, the strategy's name depends on the name of the strategy's idleYieldToken. Checking etherscan I see:
Note that idleYieldToken is set to the zero address which causes IdleTokenV4(idleYieldToken).name() to revert.
Side note.. instead of showing an error for name, it looks like etherscan shows the function's documentation from BaseStrategy.sol:
/**
* @notice This Strategy's name.
* @dev
* You can use this field to manage the "version" of this Strategy, e.g.
* `StrategySomethingOrOtherV1`. However, "API Version" is managed by
* `apiVersion()` function above.
* @return This Strategy's name.
*/
function name() external view virtual returns (string memory);
There's a strategy at 0x016919386387898E4Fa87c7c4D3324F75f178F12 currently used in the USDT 0.4.3 vault on Ethereum that reverts when its
name
function is called. Looking at the strategy's code I see:That is, the strategy's name depends on the name of the strategy's
idleYieldToken
. Checking etherscan I see:Note that idleYieldToken is set to the zero address which causes
IdleTokenV4(idleYieldToken).name()
to revert.Side note.. instead of showing an error for name, it looks like etherscan shows the function's documentation from BaseStrategy.sol:
I looked around yearn's github for guidance on how to handle this and reproduced what I found here in the subgraph: https://github.com/yearn/yearn-vaults-v2-subgraph/blob/main/src/utils/strategy/strategy.ts#L54