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
Currently we use the tx_output table to re-calculate the address_balance table after a re-org or a voided transaction is detected
The problem with this approach is that the destroy authority action does not yield any tx_output, so when re-calculating we would never get the correct unlocked_authority for an address that was involved in a re-org, even if the transaction that destroyed an authority was voided
A potential solution would be to use the fullnode APIs to fetch the affected transactions and use that list of transactions to build a balance map to reduce from the existing balances instead of re-calculating the balance using the tx_output inside the wallet-service itself.
The text was updated successfully, but these errors were encountered:
Currently we use the
tx_output
table to re-calculate theaddress_balance
table after a re-org or a voided transaction is detectedThe problem with this approach is that the
destroy authority
action does not yield anytx_output
, so when re-calculating we would never get the correctunlocked_authority
for an address that was involved in a re-org, even if the transaction that destroyed an authority was voidedA potential solution would be to use the fullnode APIs to fetch the affected transactions and use that list of transactions to build a balance map to reduce from the existing balances instead of re-calculating the balance using the
tx_output
inside the wallet-service itself.The text was updated successfully, but these errors were encountered: