For Cycle 34

[w0000000t]

Summary

Specify the total amount of BSQ you are requesting, along with the USD total and BSQ/USD rate (don't include the brackets!):

• BSQ requested: [577.24]
• USD requested: [710]
• BSQ rate: [1.23] USD per BSQ
• Previous compensation request (if applicable): # For Cycle 33 #1002

Contributions delivered

Add contributions you have delivered and roles you have performed here as new rows in the table below. Role line-items should include an asterisk (*) in the team column.

Title	Team	USD	Link	Notes
L1 support agent	support	600	bisq-network/roles#64 (comment)	mainly active on matrix telegram and forum, some activity on reddit; 600usd as per bisq-network/proposals#368
Contributor opsec heads up	support	20	https://bisq.wiki/Contributor_privacy_and_opsec	as prompted by one devcall meeting
"send fiat to bisq?" wiki article	support	5	https://bisq.wiki/How_do_I_send_fiat_to_Bisq	after getting this question so many times
testing 1.8.3	dev	85	https://pastebin.com/KsyDyq0a	able verify more PRs this time

Contributions in progress

In case it is of interest, I can further improve this script and implement a web page on Tor where support agents can login to add their own reports, and have stats be compiled automatically at the end of the cycle

[ripcurlx]

As dev team lead I approve this compensation request for dev. It would be great if you could approve/reject your own test scenarios on bisq.ontestpad as well, so it is easier for me to see how detail which parts have been tested in one glance.

[w0000000t]

It would be great if you could approve/reject your own test scenarios on bisq.ontestpad as well, so it is easier for me to see how detail which parts have been tested in one glance.

can absolutely do @ripcurlx , yet can you please explain what you mean, as I didn't quite understand? On testpad, I make sure to tag the tested sections, and in every one of them also attach screenshots of the tested feature + link to PR, example:

The link to the pastebin wall of text is to have a better ordered resume of what I actually did, that's what I personally feel would be clearer for me at a glance, and my personal "flight sheet" when I do testing, so I thought I would include it :)

[ripcurlx]

@w0000000t I didn't know that you already did this 👍 I think for test cases that are a pass you don't need to add extra information (of course appreciated), but for fail ones it is good to link the Github issue in the bug tracking field (screenshots will be there anyway I guess). Before I release and/or I start my release testing I review an overview which is similar to this report screen: https://bisq.ontestpad.com/project/1/folder/f153/report/?auth=b91656669a12abf05a9583ff8dbcb213 to see which sections need extra test coverage from my side and who tested what. So when one or two trusted contributors test certain sections I assume that this was tested properly (I normally have tested most of the code changes anyways during a PR review myself).

[w0000000t]

@ripcurlx I guess I like to make myself accountable, since I'm requesting a compensation, and I attach screenshots to show that I actually did the testing, instead of simply clicking on boxes saying that I did ;) As of now I feel like doing this little extra work, I understand now though how you check "at a glance", and I'll keep doing the pastebin thing for my own convenience and link it in CR if that's okay with you, since my testing is reported on testpad for your checking I believe 👍

[leo816]

My Team Lead review is complete and I approve this request. Please submit your DAO proposal and paste the transaction ID here as a comment when complete, thanks.

[w0000000t]

96cb71a5f2034da95219a0ba3cd389a1167bbfb1417db13f59b9efb496fac53b

[ghost]

Issuance by Team:

team	amount BSQ	amount USD
support	508.13	625.00
dev	69.11	85.00

Total Issuance: 577.24 BSQ (equivalent to: 710.00 USD)

[MwithM]

Closed as accepted.