[bisq-network/bisq] Deposit tx not broadcasted (#4911)

Oscar Guindzberg notifications at github.com
Mon Dec 7 23:13:14 CET 2020


<!--
   SUPPORT REQUESTS: This is for reporting bugs in the Bisq app.
   If you have a support request, please join #support on Bisq's
   Keybase team at https://keybase.io/team/Bisq
-->

### Description

Some users are reporting the trade deposit tx is not broadcasted.
We don't have enough data to reproduce the bug yet. I create this issue as a placeholder, so anyone that can provide info on this subject can post it here.

<!-- brief description of the bug -->

#### Version

1.5.0
<!-- commit id or version number -->

### Steps to reproduce

We don't know yet
<!--if you can reliably reproduce the bug, list the steps here  -->

### Expected behaviour

<!--description of the expected behavior -->

After trade is taken, deposit tx is marked as pending in bisq and block explorers.

### Actual behaviour

<!-- explain what happened instead of the expected behaviour -->

I got reports of deposit tx not being broadcasted. But I don't know exactly how they verify that.
We have reports of bisq showing no deposit tx when viewing the trade (maybe this is a different issue).


### Screenshots

<!--Screenshots if gui related, drag and drop to add to the issue -->

#### Device or machine

<!-- device/machine used, operating system -->



#### Additional info

<!-- Additional information useful for debugging (e.g. logs) -->

We first need to be able to reproduce the bug in order to fix it.

Things that would help us:
- Define how the user knows the tx is not broadcasted.
- Concrete examples: trade id, maker and taker fee txids, deposit tx id
- bisq logs at the time the trade was taken (if you have logs for taker and maker even better)
- if using a local bitcoin core node, the logs of bitcoin core at the time the trade was taken
- does the tx gets broadcasted if bisq is restarted? (bitcoinj broadcasts known unconfirmed txs when it starts) 
- is this just a deposit tx problem? have you experienced this with any other type of tx?
- usernames that experienced this, so we can contact them to ask questions

This is probably not related to https://github.com/bisq-network/bisq/issues/4870 but I post the link just in case.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/4911
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201207/d2a1a936/attachment.htm>


More information about the bisq-github mailing list