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
The processors now take about 18 hours to complete, this is partially due to the fact we are indexing balance transfers on all networks, it was only Khala before. But I believe it is also down to how we index the balance, see #38
Indexing balance before that PR was a little inaccurate (only by tiny fractions of a token). There are 2 approaches here:
figure out every event on substrate that effects balance and make sure we capture them all -> it's possible it's just fee related (evm is accurate but that has the fees in the data, we only get the tip)
use polkadot API to query balance at block (what the linked PR did), this is slow but accurate. Tests need to confirm if some other events are effecting balance or if it is just fees. If it's the former then this approach is more accurate, but not 100% accurate
Currently we take approach 2 for the sake of more accurate data in the short term, but the effect on performance is significant, although this does need to be confirmed with a redeploy that skips the block querying.
The text was updated successfully, but these errors were encountered:
The processors now take about 18 hours to complete, this is partially due to the fact we are indexing balance transfers on all networks, it was only Khala before. But I believe it is also down to how we index the balance, see #38
Indexing balance before that PR was a little inaccurate (only by tiny fractions of a token). There are 2 approaches here:
Currently we take approach 2 for the sake of more accurate data in the short term, but the effect on performance is significant, although this does need to be confirmed with a redeploy that skips the block querying.
The text was updated successfully, but these errors were encountered: