<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=34919942" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/HarryMacfinned">@HarryMacfinned</a> you make the build, then it creates assert files for which you then create a pull request <a href="https://github.com/bitcoin-core/gitian.sigs/tree/master/0.18.0rc2-linux/KanoczTomas">https://github.com/bitcoin-core/gitian.sigs/tree/master/0.18.0rc2-linux/KanoczTomas</a> - the output that I committed. When you download the binary from bitcoin.org the hash has to be the same as in the assert file. You can go to the repository and  check who built the binary, so you can make sure it is the same and other people independently built it. <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=1449498" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ManfredKarrer">@ManfredKarrer</a> the docker build is a run and leave running thing (it takes several hours to build) than uploading it to the repo. But I understand you will not have time. I will certainly do it for every release. <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=34919942" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/HarryMacfinned">@HarryMacfinned</a> I will create a document with steps how to do a docker build, as the official one has some parts not working and docker is not explicitly documented there.</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/roles/issues/66#issuecomment-478520748">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtu8ZHmGmxrruoyhpe9o7onFR-mBTks5vcdw5gaJpZM4RYmQm">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtnSs0AmH49N44QwO3XSTmdiEWBPhks5vcdw5gaJpZM4RYmQm.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/roles","title":"bisq-network/roles","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/roles"}},"updates":{"snippets":[{"icon":"PERSON","message":"@KanoczTomas in #66: @HarryMacfinned you make the build, then it creates assert files for which you then create a pull request https://github.com/bitcoin-core/gitian.sigs/tree/master/0.18.0rc2-linux/KanoczTomas - the output that I committed. When you download the binary from bitcoin.org the hash has to be the same as in the assert file. You can go to the repository and  check who built the binary, so you can make sure it is the same and other people independently built it. @ManfredKarrer the docker build is a run and leave running thing (it takes several hours to build) than uploading it to the repo. But I understand you will not have time. I will certainly do it for every release. @HarryMacfinned I will create a document with steps how to do a docker build, as the official one has some parts not working and docker is not explicitly documented there. "}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/roles/issues/66#issuecomment-478520748"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/roles/issues/66#issuecomment-478520748",
"url": "https://github.com/bisq-network/roles/issues/66#issuecomment-478520748",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>