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
IDs in the CTOKEN table should be constant. The only time they change is if an asset is added/removed from Compound, in which case we could just restart the code. This means that the user table code can just store a map of cTokenAddresses -> cTokenIDs and reuse it when populating the user table with accounts. This should cut down on CPU usage since there are thousands of accounts, and we'd be using one less database call for each one.
The text was updated successfully, but these errors were encountered:
IDs in the
CTOKEN
table should be constant. The only time they change is if an asset is added/removed from Compound, in which case we could just restart the code. This means that the user table code can just store a map of cTokenAddresses -> cTokenIDs and reuse it when populating the user table with accounts. This should cut down on CPU usage since there are thousands of accounts, and we'd be using one less database call for each one.The text was updated successfully, but these errors were encountered: