<p></p>
<p>The persistence subsystem in Bisq is tricky and I would like to get <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/chimp1984/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/chimp1984">@chimp1984</a>'s opinion about this topic.  Would be great if he could write a quick dev spec, sharing opinions on how it would best be tackled.</p>
<p>One thing that sprang to mind is that if the user changes his onion address, there will have to be coordination with the encryption mechanism so that user is not permanently locked out of his own data.  Currently all database is clear & unencrypted on user's own drive except for Mailbox/ProtectedStorage.</p>
<p>When spec'd I would be interested in tackling an implementation possibly in collab with <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/BtcContributor/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/BtcContributor">@BtcContributor</a>.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/5396#issuecomment-814548739">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNUUR6T7VXPKPR3TXRDTHO5ENANCNFSM42NNRC6A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNQYKZO27HGIE2XZIMTTHO5ENA5CNFSM42NNRC6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGCGQOAY.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/5396#issuecomment-814548739",
"url": "https://github.com/bisq-network/bisq/issues/5396#issuecomment-814548739",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>