You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supporting Hyperdrive instances that don't support base deposits and withdrawals is trickier with Momo than with vaults like Everlong. With Everlong, we can just make the asset the base or vault shares token; however, for Momo, the long and short targets may not (and most likely do not) use the same vault shares tokens. This creates an unfortunate situation where Hyperdrive may be responsible for managing a heterogenous mixture of, say, ETH, stETH, and RETH.
This feature should add support in such a way that more complicated cases are supported, and it should also think ahead for integrations where it may not always be possible to convert from base to vault shares without making a swap (RETH comes to mind).
The text was updated successfully, but these errors were encountered:
Supporting Hyperdrive instances that don't support base deposits and withdrawals is trickier with Momo than with vaults like Everlong. With Everlong, we can just make the
asset
the base or vault shares token; however, for Momo, the long and short targets may not (and most likely do not) use the same vault shares tokens. This creates an unfortunate situation where Hyperdrive may be responsible for managing a heterogenous mixture of, say, ETH, stETH, and RETH.This feature should add support in such a way that more complicated cases are supported, and it should also think ahead for integrations where it may not always be possible to convert from base to vault shares without making a swap (RETH comes to mind).
The text was updated successfully, but these errors were encountered: