Fee Reimbursement Agent

[cbeams]

Docs: https://bisq.wiki/Fee_Reimbursement_Agent
Team: @bisq-network/fee-reimbursement-agents

[cbeams]

2018.07 report

Nothing to report.

BSQ requested: 25

/cc bisq-network/compensation#101

[cbeams]

2018.08 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#114

[cbeams]

2018.09 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#139

[cbeams]

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

[cbeams]

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

[KanoczTomas]

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

[cbeams]

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.

[KanoczTomas]

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]

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

[KanoczTomas]

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]

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]

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

[wiz]

@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]

@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).

[leo816]

Cycle 46

• Made the Fee Reimbursement for 11 trades (0.00164571 ) 50 USD
  Batch Reimbursement support#1389 (comment)

4 other issues are pending due to information missing

[leo816]

Cycle 49

• Made the Fee Reimbursement for 16 trades (0.00517012 ) 155 USD
  Batch Reimbursement support#1435 (comment)

4 other issues are pending due to information missing

[leo816]

Cycle 50

• Made the Fee Reimbursement for 10 trades (0.0018) 55 USD
  Batch Reimbursement support#1435 (comment)

• Handled this stranded case that had been stuck for a while: Fee reimbursement for trade f73fnbm  support#1442

• 5 other issues are pending due to information missing

[leo816]

Cycle 51

• Made the Fee Reimbursement for 10 trades 115 USD
  Batch Reimbursement support#1476 (comment)

• closed a few cases that had no update since february

• 2 other issues are pending due to information missing

[leo816]

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]

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]

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]

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]

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]

Cycle 58

• Made the Fee Reimbursement for 12 trades #1595 amounting a total of 0.00497 BTC

bisq-network/support#1614 (comment)

• This cycle had less amount of false positives but still quite a few of those spotted by Dara (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]

Cycle 59

Fee reimbursements remain constant, trades and mediation also steady at the same rate:

• Made the Fee Reimbursement for 11 trades #1623

bisq-network/support#1623 (comment)

• This cycle had more false positives, most of which already spotted out by Dara (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]

Cycle 61

• Made the Fee Reimbursement for 20 issues (one issue including several tickets which is why there are 23 outputs)

The total reimbursement amount was: 0.00875208 BTC (455 USD)

bisq-network/support#1663 (comment)

[darawhelan]

@leo816 completed his last cycle as a refund agent on cycle 61 comment

Myself and @luis3672 have agreed to share the role.

I will monitor and respond to users on the support repository

@luis3672 will process the refunds and make a report:

Fees for the role will be $150 for myself and $150 for @luis3672.

I suggest that we both include the $150 in our cycle report.

I think it also makes sense for the amount reimbursed by @luis3672 to include a reimbursement cost percentage (similar to the refund agent).

The reimbursement cost percentage can be worked out as follows (100 / 30 day average BSQ price in sats) x 100

For example if the Fee Reimbursement Agent where to refund 0.03 BTC in cycle 66 why should request:

reimbursement cost percentage = ((100/2636)x100)
reimbursement cost percentage = 3.79

reimbursement cost value = (0.03 BTC / 100) x reimbursement cost percentage = 0.001137

Total reimbursed amount to be reimbursement amount + reimbursement cost value = 0.03 BTC + 0.001137 BTC = 0.031137 BTC

[luis3672]

Cycle 66

Support Issue	Amount refunded (BTC)	Address
#1626	0.0009686	bc1q66pz4y9wdezwskfhe5mssv7eqypzd0lc6459kn
#1628	0.00026076	bc1qqnnvqqad0wukj07xdd7vd3h2mfrtsegkqxthk7
#1665	0.00075595	bc1q86fkc742x5276h9h4s0kq4f4u0y7q77yakt33w
#1668	0.00166134	bc1ql0lxe2q4essa4nwy0rj4u76dv3gdlnuknsyr7z
#1669	0.0022105	bc1ql0lxe2q4essa4nwy0rj4u76dv3gdlnuknsyr7z
#1670	0.0003226	1H7Qewa6MV7kym3aMaak6DDqFoRJNSRZu6
#1674	0.0000354	bc1qv0jd0ppllpvns6yl2dekepsk9qed362d4g02mh
#1675	0.00004194	bc1q3wc2yvpckzw028w47ejzgyu6paa9vr3gycpn82
#1676	0.00019905	bc1q3wc2yvpckzw028w47ejzgyu6paa9vr3gycpn82
#1677	0.00013618	bc1q3wc2yvpckzw028w47ejzgyu6paa9vr3gycpn82
#1680	0.00003459	bc1qv08fcazau5vrz4jjgscruqk8w77uku7ca2uz79
#1681	0.00010035	bc1qhazrgwjl7vh6d4qujc6t7xpnj6vdvq0hdn8pn3
#1682	0.00002486	bc1qhazrgwjl7vh6d4qujc6t7xpnj6vdvq0hdn8pn3
#1683	0.00020385	bc1qhazrgwjl7vh6d4qujc6t7xpnj6vdvq0hdn8pn3
#1684	0.0001084	bc1qkem8wl3mretd9nurnkdepuurlrmxz5xurfkkv2
#1685	0.00002812	bc1qt5qsa9quhk9l3qvxs7dgt9tqdku6yxcafpmvxq
#1687	0.00002812	bc1qt5qsa9quhk9l3qvxs7dgt9tqdku6yxcafpmvxq
#1688	0.0000276	bc1qt5qsa9quhk9l3qvxs7dgt9tqdku6yxcafpmvxq
#1698	0.000193	bc1q6kny7j3zwh5a4rsxdm509akprc2ykevlq5hwwx
#1699	0.00013344	bc1q6kny7j3zwh5a4rsxdm509akprc2ykevlq5hwwx
#1700	0.00034366	btc address missing
#1701	0.00013344	bc1qqsvh2wm9r4vlf7pe6fw528v8sxe9phj79nw5yt
#1702	0.00013344	bc1qqsvh2wm9r4vlf7pe6fw528v8sxe9phj79nw5yt
#1703	0.00013344	bc1qqsvh2wm9r4vlf7pe6fw528v8sxe9phj79nw5yt
#1707	0.00003601	bc1qxqfmn77fntj3ryj294c7kva02074euhxvx3qtw
#1709	0.0004836	bc1qd09n3er0702vhd6q6gk9y0tywphm3j0hdf3yq3
#1712	0.0001156	bc1qtgvpmvl2swqegz7gjtdgmh2aa2ctkf92ky6g7c
#1713	0.00006750	bc1qlt3fxx9dq4tr4hnzjvtwnhexzuaywxrf9xx8d6
#1717	0.00020130	bc1q79hfn4kysdm8ysjtd5wcr4td22q08ap4cwll02
#1718	0.00031187	bc1qvu58uxwxdmqngfv3pyshpmq2d7qv2e3x6tlnjh
#1722	0.00097415	bc1q95vhslxs2r92r58506wtn3grgljm75nh0eykuc
#1723	0.00079986	bc1q95vhslxs2r92r58506wtn3grgljm75nh0eykuc
#1724	0.00050955	bc1q0uyuv9z6gz4usn348zrv4hq4mmf7ayqeg7qmwm
TOTAL	0.01137441	Payout tx

---

Reimbursement cost percentage = ((100/2603)x100)
Reimbursement cost percentage = 3.84

Reimbursement Cost Value = (0.01137441 BTC / 100) x reimbursement cost percentage = 0.000436777344

Reimbursement + Reimbursement Cost Value = 0.01137441 BTC + 0.000436777344 BTC = 0.0118111873 BTC (1190 USD)