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
{{ message }}
This repository has been archived by the owner on May 13, 2022. It is now read-only.
Often the tumbler ends without finishing. I think a useful feature would be to make it possible to resume the tumbler run.
The tumbler would save all the required information (transaction list, options, etc) to a file the user chooses, and it can be restarted by passing --resume on the CLI. After the tumbler's wallet is sync'd it can use the information it knows about transactions to tell where it is in the transaction list and carry on from there.
One problematic issue might be that this could be bad in a very-high-security environment. The transaction list file contains everything required to unmix the entire tumbler run, so a skilled technician will be able to recover that file and use it against the tumbler user.
But on the other hand, joinmarket fails in a very-high-security environment as does most privacy tech.
The text was updated successfully, but these errors were encountered:
This can't be done without changing blockchaininterface.
To know whether your wallet has already sent coins to a destination address, you must be able to query whether that address has outputs. Another way is to have blockchaininterface be able to give a list of wallet transactions.
Often the tumbler ends without finishing. I think a useful feature would be to make it possible to resume the tumbler run.
The tumbler would save all the required information (transaction list, options, etc) to a file the user chooses, and it can be restarted by passing --resume on the CLI. After the tumbler's wallet is sync'd it can use the information it knows about transactions to tell where it is in the transaction list and carry on from there.
One problematic issue might be that this could be bad in a very-high-security environment. The transaction list file contains everything required to unmix the entire tumbler run, so a skilled technician will be able to recover that file and use it against the tumbler user.
But on the other hand, joinmarket fails in a very-high-security environment as does most privacy tech.
The text was updated successfully, but these errors were encountered: