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
Instead of storing the PSBTs in DB and querying/updating them, we should only store the signatures and create the PSBTs on the fly. If i recall correctly, it was among other things meant as an optimization to query the presigned transactions.
I think it was premature, and in addition to a big cleanup (both in code and storage) it would prevent races when updating the in-DB psbt. See for instance this monstrosity which is moreover currently buggy (fixed in #366):
Instead of storing the PSBTs in DB and querying/updating them, we should only store the signatures and create the PSBTs on the fly. If i recall correctly, it was among other things meant as an optimization to query the presigned transactions.
I think it was premature, and in addition to a big cleanup (both in code and storage) it would prevent races when updating the in-DB psbt. See for instance this monstrosity which is moreover currently buggy (fixed in #366):
revaultd/src/database/actions.rs
Lines 660 to 737 in 3ab3c6a
Another instance where we need to handle possible races when merging the in-DB psbts:
revaultd/src/commands/mod.rs
Lines 556 to 600 in 3ab3c6a
The text was updated successfully, but these errors were encountered: