<p></p>
<p>If I download & verify a new bisq version manually, my current understanding is that I need 3 files:</p>
<ul>
<li>The signing key (once downloaded, the key can be used until he is revoked)</li>
<li>The new bisq release</li>
<li>The .asc signature file of the release, to verify its integrity and as proof that the release has been done by the signing key</li>
</ul>
<p>The automatic bisq updater generates a multitude of other files which type I recon but I'm pretty unsure why they are needed additionally (see picture). Can someone explain to me why there are more than 2 or 3 files? Are they really necessary? It is confusing (at least for me) and clutters the download folder. Maybe it is even possible to remove all files after updating automatically so that no files "remain" in the download folder?!</p>
<p><a target="_blank" rel="noopener noreferrer" href="https://user-images.githubusercontent.com/72392544/120218989-0ef0a900-c22a-11eb-9040-bf48c14dbc65.png"><img src="https://user-images.githubusercontent.com/72392544/120218989-0ef0a900-c22a-11eb-9040-bf48c14dbc65.png" alt="Download_folder" style="max-width:100%;"></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/discussions/5545">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNXBGCZKLMLN6TICO3TTQOYTVANCNFSM453E4AFQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNXW3ZCIITFQ2VD2C6TTQOYTVA5CNFSM453E4AF2YY3PNVWWK3TUL52HS4DFVJCGS43DOVZXG2LPN2VGG33NNVSW45C7NFSM4ABTXPTA.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/discussions/5545",
"url": "https://github.com/bisq-network/bisq/discussions/5545",
"name": "View Discussion"
},
"description": "View this Discussion on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>