<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=301810" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cbeams">@cbeams</a> Thanks for the feedback!</p>
<blockquote>
<ol>
<li>I doubt traders...</li>
</ol>
</blockquote>
<p>Yes good point. I think it will depend on the granularity of the price data. If it is a 4 decimal price it will be highly unlikely that this ever will happen. It just makes all easier as we don't need to support a refund mode. But of course it would be possible as well but might have some negative consequences. E.g. the traders need to make 2 issuance transactions. One with full payment to him and one with split refund payout. Those cost btc fees... But maybe there is a way to work with not published transactions as well and that the issuance tx will be only broadcasted in case of a win (or slipt refund) scenario.</p>
<blockquote>
<ol start="2">
<li>In the case of an oracle...</li>
</ol>
</blockquote>
<p>Good idea. Probably we will need some more buffer for avoiding issues with reorgs. Theoretically the result could be included in a block which gets later re-orged and then the alternative chain might contain another tx with another result. With 10 blocks break between price publishing and cntract result execution we avoid those problems.</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/proposals/issues/45#issuecomment-428633973">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtuX4rcRenyuqo5ULlj2B6v2_2gLCks5ujhwwgaJpZM4XT-Hz">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtolhTA53giYqHdj4plAO5FW_YVJ1ks5ujhwwgaJpZM4XT-Hz.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/proposals","title":"bisq-network/proposals","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/proposals"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ManfredKarrer in #45: @cbeams Thanks for the feedback!\r\n\r\n\u003e 1. I doubt traders...\r\n\r\nYes good point. I think it will depend on the granularity of the price data. If it is a 4 decimal price it will be highly unlikely that this ever will happen. It just makes all easier as we don't need to support a refund mode. But of course it would be possible as well but might have some negative consequences. E.g. the traders need to make 2 issuance transactions. One with full payment to him and one with split refund payout. Those cost btc fees... But maybe there is a way to work with not published transactions as well and that the issuance tx will be only broadcasted in case of a win (or slipt refund) scenario.\r\n\r\n\u003e 2.  In the case of an oracle...\r\n\r\nGood idea. Probably we will need some more buffer for avoiding issues with reorgs. Theoretically the result could be included in a block which gets later re-orged and then the alternative chain might contain another tx with another result. With 10 blocks break between price publishing and cntract result execution we avoid those problems.\r\n"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/proposals/issues/45#issuecomment-428633973"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/proposals/issues/45#issuecomment-428633973",
"url": "https://github.com/bisq-network/proposals/issues/45#issuecomment-428633973",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [bisq-network/proposals] Decentralized binary option trading (#45)",
"sections": [
{
"text": "",
"activityTitle": "**Manfred Karrer**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@ManfredKarrer",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"bisq-network/proposals\",\n\"issueId\": 45,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"bisq-network/proposals\",\n\"issueId\": 45\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/bisq-network/proposals/issues/45#issuecomment-428633973"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 391111155\n}"
}
],
"themeColor": "26292E"
}
]</script>