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
There is a lot of repeat logic to parse obligation states in both the SDK (https://github.com/solendprotocol/solend-sdk) and the liquidator. In some situations I have noticed meaningful divergence in the implementations.
One example. When parsing a deposit account the SDK introduces the notion of cTokenExchangeRate and uses this to adjust the supply. On the other hand the liquidator uses the getCollateralExchangeRate function which performs a calculation that is directionally the same but reads quite a bit differently.
I am somewhat skeptical that these implementations are exactly the same in all cases which raises some questions as to which one to follow when building logic that sits on top of Solend
There is a lot of repeat logic to parse obligation states in both the SDK (https://github.com/solendprotocol/solend-sdk) and the liquidator. In some situations I have noticed meaningful divergence in the implementations.
One example. When parsing a deposit account the SDK introduces the notion of
cTokenExchangeRateand uses this to adjust the supply. On the other hand the liquidator uses thegetCollateralExchangeRatefunction which performs a calculation that is directionally the same but reads quite a bit differently.I am somewhat skeptical that these implementations are exactly the same in all cases which raises some questions as to which one to follow when building logic that sits on top of Solend