<p></p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/freimair/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/freimair">@freimair</a> it would go a long way if the network could at least check that they saw the make-offer transaction on their mempools (this could be delegated to the seed nodes). But at the moment even that doesn't happen. So no for offers with unbroadcast make-offer transactions.</p>
<p>As for broadcast but unconfirmed make-offer transactions. This limit may not make sense for the maker?! They are responsible for 1 of the 3 transactions relevant to this issue. If they make 10 offers with all broadcast but unconfirmed transactions and 10 different traders take the offers before they've been confirmed would this issue affect the maker?<br>
<a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/devinbileck/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/devinbileck">@devinbileck</a> description only described the taker's side.</p>
<p>I don't know which transaction of the following the maker keeps track of:</p>
<ol>
<li>make-offer tx</li>
<li>take-offer tx</li>
<li>multisig deposit</li>
</ol>
<p>Assuming from the issue this PR is trying to address, the taker carries transactions 2 and 3.</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/pull/4053#issuecomment-598166457">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNWY2REQMH5GZOSEVJLRHDKX7ANCNFSM4LGK3OOA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNWKKQEARNI6A2FN3SLRHDKX7A5CNFSM4LGK3OOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOTUXOI.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/pull/4053#issuecomment-598166457",
"url": "https://github.com/bisq-network/bisq/pull/4053#issuecomment-598166457",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>