This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

But 0.00126 BTC deducted from wallet. Have tried deleting and resyncing SPV but no luck.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

I've made an offer to sell BTC for Euro - can see it under My Portfolio tab, but not in the actual market for BTC-EUR or in the Offer Book for Euro (BTC/EUR).

And in History, I see an old BTC/GBP offer that I had cancelled showing as 'Available' under Status.

Bisq is fully synced.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

@PacoTiger commented on Sun Jan 07 2018

After installation, I was trying to restore a bisq wallet by seed. I think after that, the program doesn´t open. Happy because my wallet has been empty before this issue.

@PacoTiger commented on Sun Jan 07 2018

attached log file
bisq.log

@mrosseel commented on Sun Jan 07 2018

Which version was your old wallet? If it comes from a too old bisq version,
wallet seeds are not compatible.

On Jan 7, 2018 04:29, "Paco Padilla" [email protected] wrote:

attached log file
bisq.log https://github.com/bisq-network/exchange/files/1609463/bisq.log

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
bisq-network/bisq#1157 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZb3qUJhJYrmPiW2TEF4IhlH8CpmnDfks5tIDoegaJpZM4RVhe7
.

@PacoTiger commented on Mon Jan 08 2018

I don´t remenber, but was in december. Anyway i will be happy only if the program would open to trade!

@doffing81 commented on Mon Jan 15 2018

I believe my unconfirmed transaction has disappeared from the mempool as later transactions with smaller sat/byte fees are now being confirmed. My transaction is from Bisq to an exchange. What are my options here? Am I able to get the private key? I know Bisq uses HD wallets, but not exactly sure what standard, for which I could probably extract them and create a new transaction. Bisq says I have 0 funds, so I can't even fill in the "Withdraw from address" field. I'm coming up on two weeks waiting for this transaction, so I'd like to figure out a way to get it confirmed. Suggestions?

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

@eespn commented on Thu Jan 04 2018

Hi, I am having this problem frequently, this is the forth time, I do not understand why you do not take a commission only after confirming the buy, I have already another ticket opened via email for the previous 3 cases.

I receive a message that there has been an error and a link to open a ticket in GitHUb or to open the log, now the only I can do is cancel, once I do that I get charged either way, it tells me that I have already funded the offer, that if I cancel the funds will be moved to the wallet again, but it didn't happen with the whole amount the last three times... so I have no hopes this time,

If I try t cancel and try to buy again it will not let me, the "Review: Take offer to buy Bitcoin" button is not functional any longer

This time, since it is the fourth time, I closed the tab without hitting cancel, hoping it will not charge me the deposit, and it worked (had to re-start Bisq for my balance to update), BUT still, a mysterious amount was withdrawn "0.00205640", which is no small amount, it is over 30 USD

As you can see from the image above, from the wallet an amount of 0.00205640 was withdraw, I can't understand why , can't make sense of it

Please assist to get this amount back, unfortunately have three additional cases before even worst than this one....,

Thanks!

@ManfredKarrer commented on Thu Jan 04 2018

Can you send me the log file (account/backup -> button)? My email is manfred at bitsquare dot io.

Please contact @cbeams regarding the lost fee payments.

@eespn commented on Thu Jan 04 2018

Thanks, I will be sending you the log soon after with code Ticket 1148 EESPN

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

This epic tracked the our first batch reimbursement transaction, which was required to pay back traders who lost the trading and mining fees due to transaction broadcast timeout errors documented in bisq-network/bisq#1167 and related issues.

UPDATE: This batch of reimbursements was paid out on January 17th in batch transaction 9aa7f26d5b39301a0add1b627bb8e8cd961fb8d16c9777a3342ad160c6cf1ebf. See #1 (comment) and subsequent comments below for further details.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

#33 was the most recent issue in this repository, and per my tweet at https://twitter.com/cbeams/status/952902701779750912, it just suddenly went 404. I'm creating this issue now to see if the next issue ID is 34 (my prediction) or if it's 33, i.e. that the previous issue 33 has been utterly 'forgotten'.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

@emma19900907 commented on Tue Jan 09 2018

Posted an offer and kept getting a timeout error as others have posted, but no funds were withdrawn from my wallet. Was preparing to post here when suddenly got the notice that the offers had been posted successfully. All 4 that I attempted. Cancelling them incurs a fee. None had gone through, then they all succeeded at once. Wonder how this can be resolved. Attached a picture for reference, thanks.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

This issue has been created per the process detailed in #35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/bisq#1193 and under investigation at bisq-network/bisq#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

There seems like a lot of info here for tagging transactions as Bisq Network transactions.

How Bisq keeps data private

...

Bisq has no central servers or databases to record data

Data is encrypted such that trade details are readable only by counterparties

(emphasis added)

That's all, and I don't mean to be a bother...

Background

This epic, like #1, captures a set of fee reimbursements, to be paid out in a batch transaction.

At time of writing, there are two types of reimbursement cases we're dealing with:

1. A few remaining "timeout" reimbursements that needed more info and couldn't make it into the batch tx that closed #1.
2. A number of "tx broadcast failure" cases, where trades had to be cancelled because of missing maker/taker/deposit transactions. See bisq-network/bisq#1193 and bisq-network/bisq#1195 for details.

Reimbursements will be staged in support-35.csv in the root of this repository, similar to the way support-1.csv was used in #1.

Reimbursement Process

For any remaining timeout cases (like those processed in batch reimbursement #1), @cbeams to follow the same process as was followed in #1, this time adding entries to support-35.csv in the root of this repository.

For transaction broadcast failure cases, @cbeams and @keo-bisq to follow the steps below, as originally written up in bisq-network/bisq#1195 (comment):

1. @cbeams / @keo-bisq to log the ID of each affected trade immediately upon arrival in their arbitration queues with a comment in bisq-network/bisq#1193;
2. @cbeams / @keo-bisq to create a new issue in bisq-network/support to track reimbursing whichever transaction(s) did successfully get broadcast for that trade:
   a. add a comment with a screenshot of the Maker/Taker/Deposit section of the trade details and copy and paste the text values of the Maker/Taker/Deposit transaction IDs. See #37 (comment) for an example of how this should be done.
3. Send arbitration chat messages to both buyer and seller explaining what happened and what to expect next. Here is a copy-and-paste template, but BE SURE TO REPLACE THE FIXME TEXT BELOW IN THE GITHUB ISSUE URL, EMAIL ADDRESS AND PGP KEY URL:

ATTENTION: This trade will be closed shortly, in favor of handling the reimbursement process via the GitHub issue at https://github.com/bisq-network/support/issues/FIXME

WHAT YOU NEED TO DO NOW:

1. Subscribe for updates on the GitHub issue. There are instructions how to do this in the description of the issue. If you had a transaction get successfully broadcasted to the Bitcoin network as part of this trade, you will be reimbursed for your Bisq trading fee and for your Bitcoin mining fee. The reimbursement will be paid to the address originally used as input to the transaction.

2. Delete and resync your SPV file. This can be done at Settings->Network info->Resync SPV chain, and it will ensure that any failed transactions related to this trade no longer affect your available balance.

FURTHER QUESTIONS?

If you have any further questions, you have two choices:

1. Ask them on the GitHub issue linked above. Just keep privacy implications in mind if you do.
2. Ask me via email to FIXME. If you prefer to encrypt, my PGP key is available at https://FIXME

You can also ask any follow-up questions here before I close the issue. But I will close it soon!

4. Close the arbitration ticket, using "BTC seller gets trade amount payout". Note that this will have no effect, but you have to provide some value here in order to close the ticket, so we may as well be consistent in our approach and this is the safest option to choose anyway.
5. Assign the GitHub issue to @cbeams (if it is not already).
6. @cbeams to stage each transaction for reimbursement in support-35.csv and comment on the GitHub issue accordingly.
7. Repeat steps 1–6 until @ManfredKarrer has a fix for the issue and has shipped a new release
8. Announce the release and wait a few days for everyone to upgrade and for any in-flight trades suffering from this problem to make their way into arbitration.
9. Craft and send a batch transaction that reimburses all staged transactions from step (6).
10. Close all the GitHub issues created in step (2) with a comment linking to the batch reimbursement transaction in step (9).