-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fee reimbursement for trade IY6TIN4 #1665
Comments
Please reimburse fees. Thanks. |
Payout will be included in the next batch |
On this trade you lost: Total: 0.00075595 BTC |
@luis3672 please can you refund in cycle 66 |
Thanks so much.
I have a question for you.
Why are the offers sent by notifications not visible, for example the offer
attached and screen shot of what I can see. This happens all the time and
was not the case last year.
…On Thu, 2 Jan 2025, 22:59 Dara Whelan, ***@***.***> wrote:
On this trade you lost:
*Total: 0.00075595 BTC*
—
Reply to this email directly, view it on GitHub
<#1665 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BESVFUX6EP4WHKIKB4OOD5T2IWZCRAVCNFSM6AAAAABMUAOD5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRYGQZTENBZG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sorry I am not understanding the question. What do you mean by "offers sent by notifications not visible"? |
.....its actually quite simple. The buy (BTC with fiat) offers (BTC/EURO)
sent to by "Notification" via the mobile app, are not visible in the bisq
client when checked in real time/immediately. The bisq client on
Ubuntu/Mint is fully synced, peers are all green, there are no DAO errors,
mutiple reboots does not fix it either).
…On Mon, Jan 6, 2025 at 6:47 PM Dara Whelan ***@***.***> wrote:
Sorry I am not understanding the question. What do you mean by "offers
sent by notifications not visible"?
—
Reply to this email directly, view it on GitHub
<#1665 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BESVFUXKPPMQAKXEGZOWWMD2JK6UFAVCNFSM6AAAAABMUAOD5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTGYYDONRUGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
...can in point. 2 screenshots, showing 8 Wise offers, but only 2 offers
available to purchase. Why?
On Thu, Jan 9, 2025 at 9:25 AM Dr. G.A. Kirkman ***@***.***>
wrote:
… .....its actually quite simple. The buy (BTC with fiat) offers (BTC/EURO)
sent to by "Notification" via the mobile app, are not visible in the bisq
client when checked in real time/immediately. The bisq client on
Ubuntu/Mint is fully synced, peers are all green, there are no DAO errors,
mutiple reboots does not fix it either).
On Mon, Jan 6, 2025 at 6:47 PM Dara Whelan ***@***.***>
wrote:
> Sorry I am not understanding the question. What do you mean by "offers
> sent by notifications not visible"?
>
> —
> Reply to this email directly, view it on GitHub
> <#1665 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BESVFUXKPPMQAKXEGZOWWMD2JK6UFAVCNFSM6AAAAABMUAOD5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTGYYDONRUGQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SCREENSHOT HERE
![Screenshot from 2024-08-16 14-29-47](https://private-user-images.githubusercontent.com/153440978/358587682-92b26632-dbcd-41fd-8c77-25fa32026ff0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNTI4MTUsIm5iZiI6MTczOTI1MjUxNSwicGF0aCI6Ii8xNTM0NDA5NzgvMzU4NTg3NjgyLTkyYjI2NjMyLWRiY2QtNDFmZC04Yzc3LTI1ZmEzMjAyNmZmMC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMVQwNTQxNTVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04OWRkYmFmYTVhOTUxMjJlYTg4NmVjZDFlNGI5OGMwZGY3MzZjN2JlNmQxZTgwNDRjN2E2N2EyMmFhYTE5NzdhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.r_BxwcwK8XvzRudC-L80pL9jNm35V-Qh2PdQga_QVbk)
Maker: 36ab42860e4cd93a79b137ce8b44e342a45a26c25e10c19c35c03d34584e10d6
Taker: f15bfce7f4345d1e1576d005eaecb406cac80cc54d2a7625ce76928f36a9e4df
Deposit: N/A
BTC mining fees lost: Taker: 0.00075595 BTC
Trade fees lost, please state if BSQ or BTC: not known
Bisq version: 1.9.17
BTC address for reimbursement: bc1q86fkc742x5276h9h4s0kq4f4u0y7q77yakt33w
Other notes:
An error occurred at task: BuyerVerifiesPreparedDelayedPayoutTx
Exception message: TxIds of buyersPreparedDelayedPayoutTx and sellersPreparedDelayedPayoutTx must be the same.
The text was updated successfully, but these errors were encountered: