Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fee Reimbursement Agent #76

Open
cbeams opened this issue Jul 1, 2018 · 55 comments
Open

Fee Reimbursement Agent #76

cbeams opened this issue Jul 1, 2018 · 55 comments
Assignees
@leo816
Labels
team:support https://bisq.wiki/Support_Team

Comments

@cbeams
Copy link
Member

cbeams commented Jul 1, 2018 •
edited

Docs: https://bisq.wiki/Fee_Reimbursement_Agent
Team: @bisq-network/fee-reimbursement-agents
@cbeams cbeams self-assigned this Jul 1, 2018
@cbeams
Copy link
Member Author

cbeams commented Jul 31, 2018

2018.07 report

Nothing to report.

BSQ requested: 25

/cc bisq-network/compensation#101

@cbeams cbeams mentioned this issue Jul 31, 2018
Closed
@cbeams
Copy link
Member Author

cbeams commented Aug 31, 2018

2018.08 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#114

@cbeams cbeams mentioned this issue Aug 31, 2018
Closed
@cbeams
Copy link
Member Author

cbeams commented Sep 30, 2018

2018.09 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#139

@cbeams cbeams mentioned this issue Sep 30, 2018
Closed
@cbeams
Copy link
Member Author

cbeams commented Oct 31, 2018

2018.10 report

@KanoczTomas stepped up this month to help process a months-long backlog of reimbursement requests, and as mentioned in his compensation request at bisq-network/compensation#152, he offered to take on a dedicated role for doing this kind of work. So I'll transition primary ownership of this role to him over the next month.

Tomas, I'd suggest reading https://docs.bisq.network/roles.html#maintainer. I'll grant you write access to this repository so you can properly handle the issues, e.g. assigning and labeling them, etc. Otherwise, there's not much to be done other than handling incoming reimbursement requests. I think it's an open question whether this repository should handle anything else, e.g. other support issues. We have the forum for that, and more technical support requests often end up in the main bisq-network/bisq repository, which isn't necessarily a bad thing. In any case, as maintainer, you'll be free to work with the main repo maintainers and suggest what you think makes sense.

Also please read https://docs.bisq.network/roles.html#reporting and follow the instructions there starting with next month's compensation request cycle.

It's a good idea to read the whole roles doc, actually, so you've got full context.

In any case, if that all goes smoothly, I'll fully hand over primary ownership of this to you next month. Please let me know what you need in the meantime, thanks!

BSQ Requested: 25

/cc bisq-network/compensation#160

This was referenced Oct 31, 2018
Closed
Closed
@cbeams
Copy link
Member Author

cbeams commented Nov 30, 2018

2018.11 report

@KanoczTomas continued to manage the support repository this month, and is now putting together the next batch reimbursement at bisq-network/support#147.

@KanoczTomas, I'd like to make you the primary owner of this role, which would mean doing what you're already doing, plus posting a report like this one here each month. Are you OK with that?

BSQ requested: 25

/cc bisq-network/compensation#179

@cbeams cbeams mentioned this issue Nov 30, 2018
Closed
@KanoczTomas
Copy link
Member

@cbeams ok, I am fine with it. I am taking the role and will write the report for december when the time comes.

@cbeams
Copy link
Member Author

cbeams commented Dec 6, 2018

Per #1 (comment), I'll be away for the next ~2 months. @KanoczTomas has already agreed to take on ownership of this role, and I'm un-assigning myself from it now.

@cbeams cbeams removed their assignment Dec 6, 2018
@KanoczTomas
Copy link
Member

2018.12 report

There were 17 reimbursements opened for month december which were compensated by #173

BSQ Requested: 25

/cc bisq-network/compensation#201

@ManfredKarrer
Copy link
Member

Thanks a lot @KanoczTomas! Very appreciated that you took over responsibility for that task!

@KanoczTomas KanoczTomas mentioned this issue Jan 28, 2019
Closed
@KanoczTomas
Copy link
Member

2019.01 report

There are 8 issues with reimbursements opened for month January which will be compensated by #195. There are 60 transactions in this batch totaling 0.09307566 BTC.

BSQ Requested: 25

/cc bisq-network/compensation#201

@KanoczTomas
Copy link
Member

2019.02 report

There 3 staged issues and 2 waiting for input from user. They will be reimbursed with #200.

BSQ Requested: 25

/cc bisq-network/compensation#221

@KanoczTomas KanoczTomas mentioned this issue Feb 28, 2019
Closed
@KanoczTomas
Copy link
Member

2019.03 report

Processed 12 reimbursement requests in this batch totalling 0,013346 BTC. Reimbursed via #200

BSQ Requested: 600

*note I had a feedback to raise my requested amount as previous requests were undervalued by myself. 600 is a compensation for last requests as well.

/cc bisq-network/compensation#237

@KanoczTomas KanoczTomas mentioned this issue Mar 31, 2019
Closed
@wiz
Copy link
Member

wiz commented Mar 17, 2020

@KanoczTomas are you still performing this role? there are many issues in the support repository piling up and it seems you haven't filed a monthly report for the Support Maintainer role in a year...

@cbeams
Copy link
Member Author

cbeams commented Mar 23, 2020

@KanoczTomas will do a call to hand off this role to @leo816. Scheduled for 2020-03-27. Afterward, @leo816 will assume this role (and we'll probably rename the role as well).

@cbeams cbeams added the team:support https://bisq.wiki/Support_Team label Apr 15, 2020
@cbeams cbeams changed the title Support Maintainer Fee Reimbursement Agent Apr 15, 2020
@leo816
Copy link

leo816 commented Oct 8, 2022

Cycle 40

There are currently 3 fee reimbursement requests pending due to missing information.

@leo816 leo816 mentioned this issue Oct 8, 2022
Closed
@leo816
Copy link

leo816 commented Nov 9, 2022

Cycle 41

There are currently 2 fee reimbursement requests pending due to missing information.

@leo816 leo816 mentioned this issue Nov 9, 2022
Closed
@leo816
Copy link

leo816 commented Dec 22, 2022 •
edited

Cycle 42

There is currently 1 fee reimbursement requests pending due to missing information.

@leo816 leo816 mentioned this issue Dec 22, 2022
Closed
@leo816
Copy link

leo816 commented Jan 11, 2023

Cycle 43

There is currently 15 fee reimbursement requests pending due to missing information.
This cycle the number has spiked due to the bugs regarding the new trade protocol, as such I've had to review +150 issues individually one by one and make 70 payouts. Usually I don't ask for a lot of reimbursement even though the risks of this role are evident in terms of volatility in price and privacy but this cycle this has taken a lot of my time so I will increase my compensation.

@leo816
Copy link

leo816 commented Feb 14, 2023

Cycle 44

15 other issues that have been waiting for information were taken down

@leo816 leo816 mentioned this issue Feb 14, 2023
Closed
@leo816
Copy link

leo816 commented Mar 17, 2023

Cycle 45

4 other issues are pending due to information missing

@leo816 leo816 mentioned this issue Mar 17, 2023
Closed
@leo816 leo816 mentioned this issue Apr 12, 2023
Closed
@leo816
Copy link

leo816 commented Apr 13, 2023

Cycle 46

4 other issues are pending due to information missing

@leo816 leo816 mentioned this issue May 17, 2023
Closed
@leo816 leo816 mentioned this issue Jun 21, 2023
Closed
@leo816
Copy link

leo816 commented Jun 23, 2023

Cycle 49

4 other issues are pending due to information missing

@leo816 leo816 mentioned this issue Jul 23, 2023
Closed
@leo816
Copy link

leo816 commented Aug 24, 2023

Cycle 50

@leo816 leo816 mentioned this issue Aug 24, 2023
Closed
@leo816
Copy link

leo816 commented Sep 25, 2023 •
edited

Cycle 51

@leo816
Copy link

leo816 commented Nov 23, 2023

Cycle 52 & 53

  • Made the Fee Reimbursement for 18 trades #1515
    Batch Reimbursement support#1515

  • closed a few cases that had no update or were requesting for reimbursement without the having paid fee on the first place

  • 1 other issues is pending due to information missing

TOTAL: 0.00382575 BTC

@leo816 leo816 mentioned this issue Nov 23, 2023
Closed
@leo816
Copy link

leo816 commented Dec 29, 2023

Cycle 54

  • Made the Fee Reimbursement for 8 trades #1531

bisq-network/support#1531 (comment)

  • closed issues that were made wrongly by users who had not lost their deposit but rather just needed to SPV Resync (failed trades)

  • 1 other issues is pending due to information missing

@leo816 leo816 mentioned this issue Dec 29, 2023
Closed
@leo816
Copy link

leo816 commented Jan 29, 2024

Cycle 55

  • Made the Fee Reimbursement for 9 trades #1557

bisq-network/support#1557

  • This cycle we also had a lot of false positives and those issues were all closed (users who had not lost their deposit but rather just needed to SPV Resync)

  • There were two issues pending, one of them was not elligible for reimbursement, the remaining is from a trade from 2018. I've tried several times to contact the arbitrator but there was no luck (the user even offered 25% of the trade amount as bounty)

@leo816 leo816 mentioned this issue Jan 29, 2024
Closed
@leo816
Copy link

leo816 commented Feb 29, 2024 •
edited

Cycle 56

  • Made the Fee Reimbursement for 13 trades #1583 amounting a total of 0.00487892 BTC

bisq-network/support#1583

  • This cycle we also had a lot of false positives and those issues were all closed (users who had not lost their deposit but thought they had due to the error message)

  • There is still one issue pending, it's still from a trade from 2018. I've tried several times to contact the arbitrator but there was no luck (the user even offered 25% of the trade amount as bounty)

@leo816 leo816 mentioned this issue Feb 29, 2024
Closed
@leo816
Copy link

leo816 commented Mar 30, 2024

Cycle 57

  • Made the Fee Reimbursement for 17 trades #1595 amounting a total of 0.00699733 BTC

bisq-network/support#1583

  • This cycle we also had a lot of false positives and those issues were all closed (users who had not lost their deposit but thought they had due to the error message)

  • The same issue as reported on the last cycle, there is still one issue pending, it's still from a trade from 2018. I've tried several times to contact the arbitrator but there was no luck (the user even offered 25% of the trade amount as bounty)

@leo816 leo816 mentioned this issue Mar 30, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@leo816 leo816

Labels
team:support https://bisq.wiki/Support_Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@wiz @cbeams @ManfredKarrer @KanoczTomas @leo816