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
Fee tx hex makes up a huge amount of the database size. Once the fee tx is broadcast and has 6 confirmations, keeping the hex in the database is unnecessary so long as we keep the hash.
I propose a database migration to clear out any old fee tx hex which are no longer required, and a change to background.go which will ensure that any new fee tx hex are removed once they are confirmed.
The text was updated successfully, but these errors were encountered:
Fee tx hex makes up a huge amount of the database size. Once the fee tx is broadcast and has 6 confirmations, keeping the hex in the database is unnecessary so long as we keep the hash.
I propose a database migration to clear out any old fee tx hex which are no longer required, and a change to background.go which will ensure that any new fee tx hex are removed once they are confirmed.
The text was updated successfully, but these errors were encountered: