<blockquote>
<p>What are your values for AppOptionKeys.USE_DEV_PRIVILEGE_KEYS and AppOptionKeys.IGNORE_DEV_MSG_KEY? This is relevant for your Regtest message filtering.</p>
</blockquote>
<p>While testing on regtest, USE_DEV_PRIVILEGE_KEYS is true and IGNORE_DEV_MSG_KEY is false.</p>
<blockquote>
<p>Most likely its that users have the USE_DEV_PRIVILEGE_KEYS prog arg set. But then they cannot trade as well as the arbitrators are not valid.</p>
</blockquote>
<p>While running from the binary on mainnet, USE_DEV_PRIVILEGE_KEYS is false and still encounter this issue (I explicitly passed <code>--useDevPrivilegeKeys=false</code> to ensure).</p>
<p>I agree that it does not appear to be related to BitcoinJ, as running from source I get the update prompt. It appears to be specific to running from the binary.</p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=170962" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ripcurlx">@ripcurlx</a> has anything changed recently with how you generate the Windows binary?</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/2729#issuecomment-484240549">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtg8oOc2orXTCwl_MOGEmQwud7yo9ks5vh35wgaJpZM4czqCk">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtsq-3RNYdAw2v3EbZIXf4zxjoVwAks5vh35wgaJpZM4czqCk.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/bisq","title":"bisq-network/bisq","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/bisq"}},"updates":{"snippets":[{"icon":"PERSON","message":"@devinbileck in #2729: \u003e What are your values for AppOptionKeys.USE_DEV_PRIVILEGE_KEYS and AppOptionKeys.IGNORE_DEV_MSG_KEY? This is relevant for your Regtest message filtering.\r\n\r\nWhile testing on regtest, USE_DEV_PRIVILEGE_KEYS is true and IGNORE_DEV_MSG_KEY is false.\r\n\r\n\r\n\u003e Most likely its that users have the USE_DEV_PRIVILEGE_KEYS prog arg set. But then they cannot trade as well as the arbitrators are not valid.\r\n\r\nWhile running from the binary on mainnet, USE_DEV_PRIVILEGE_KEYS is false and still encounter this issue (I explicitly passed `--useDevPrivilegeKeys=false` to ensure).\r\n\r\n\r\nI agree that it does not appear to be related to BitcoinJ, as running from source I get the update prompt. It appears to be specific to running from the binary.\r\n\r\n@ripcurlx has anything changed recently with how you generate the Windows binary?"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/bisq/issues/2729#issuecomment-484240549"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/2729#issuecomment-484240549",
"url": "https://github.com/bisq-network/bisq/issues/2729#issuecomment-484240549",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>