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 updateAccountsViaBalanceChecker method in the account tracker, and therefore the eth_call to the SINGLE_CALL_BALANCES_ADDRESSES, is happening even if the associated privacy setting ("Batch account balance requests") is toggled off.
This exists on 11.16.14, and probably earlier, although I have not yet determined how much earlier.
The text was updated successfully, but these errors were encountered:
danjm
added
Sev1-high
High severity; partial loss of service with severe impact upon users, with no workaround.
and removed
release-blocker
This bug is blocking the next release
regression-beta-12.0.0
Regression bug that was found in beta in release 12.0.0
labels
Jul 22, 2024
Gudahtt
added
Sev3-low
Low severity; minimal to no impact upon users
and removed
Sev1-high
High severity; partial loss of service with severe impact upon users, with no workaround.
INVALID-ISSUE-TEMPLATE
Issue's body doesn't match any issue template.
labels
Aug 15, 2024
Downgrading to sev3 because the balance update contract is still only being called with a single account at a time.
We can still update this to check the single account's balance directly, rather than through the contract. Maybe saving Infura some money and improving performance a little bit. But the problem shouldn't have any significant user impact or privacy impact.
The
updateAccountsViaBalanceChecker
method in the account tracker, and therefore theeth_call
to theSINGLE_CALL_BALANCES_ADDRESSES
, is happening even if the associated privacy setting ("Batch account balance requests") is toggled off.This exists on 11.16.14, and probably earlier, although I have not yet determined how much earlier.
The text was updated successfully, but these errors were encountered: