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
Add contributions you have delivered and roles you have performed here as new rows in the table below. Role line-items should include an asterisk (*) in the team column.
Title
Team
USD
Link
Notes
Optimise/simplify some stream filtering for the REST API
Provide links to work you're involved with that is still in progress. This section is optional (the linter ignores it), and is for your own benefit in keeping track of what you're doing and keeping other contributors up to date with the same.
I have implemented and tested a solution for recovering the redirect tx in the event of data loss, for the v5 trade protocol, which hides the critical data (peer signature for the redirect tx) in signature nonces on-chain. This allows the redirect tx to always be recoverable from the seed phrase alone, at least in the event that the peer publishes the warning tx, by restoring the trade wallet on a fresh Bisq installation. I've also done a little more work on the paths where the warning, redirect & claim txs are published.
The text was updated successfully, but these errors were encountered:
Summary
75
Contributions delivered
Contributions in progress
The text was updated successfully, but these errors were encountered: