Closed MikeHathaway closed 1 year ago
@prateek105 @EdNoepel I debated, but ultimately didn't add the remaining RPC calls in updatePool
as they are all different contracts, which would prevent usage in any multicall. I figured that there would be less maintenance overhead with leaving the other calls as is, as compared to the efficiency gains from aggregating the other contract calls.
Description of change
High level
poolDetailsMulticall
to thePoolInfoUtilsMulticall
contract. This enables us to reduce the number of RPC calls made toPoolInfoUtils
in the subgraph'supdatePool
method from 7 down to 1.poolBalanceDetails
to aggregate 2 pool calls, and 2 token contract calls.Multicall
inheritance toPoolInfoUtils
to simplify smart contract integrations.