mirror of
https://github.com/bisq-network/bisq.git
synced 2024-11-19 01:41:11 +01:00
de131c83b5
The uid is not perfect like a cryptographic hash but it can be considered safe enough to not have collusion. The list got filled with duplicates, so should have been a hashSet anyway. We cannot use the hash as that is not available at the remove method. We might refactor that in future to get rid of that problematic uid as key but will require a but more refactoring in the client code as well, as we do not pass around the outer envelope data but only the decrypted data. - Add protectedStorageEntry from persisted mailbox messages to P2PDataStorage at startup. This ensures that we add those keys to excludedKeys and that helps to reduce load for seed nodes at initial data response. - Refactoring at removeFromMapAndDataStore: - Add trace logs - Add more comments |
||
---|---|---|
.. | ||
src |