-
Notifications
You must be signed in to change notification settings - Fork 16
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
For January 2018 #35
Comments
This was referenced Jan 31, 2018
Closed
This request is staged for voting at https://docs.google.com/spreadsheets/d/1xlXDswj3251BPCOcII-UyWlX7o7jMkfYBE-IZ5te5Ck/edit#gid=1018906710 |
Closing as complete. See bisq-network/dao#39 (comment). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Basic information
Details
This month, a new Support Staff role was created (bisq-network/roles#64), which I created and took on in order to service reimbursements for failed trades due to the transaction timeout and broadcast failure bugs introduced in Bisq v0.6.2 and now fixed in v0.6.3 and v0.6.4. This work was critical to get right, as these were our first real incidents where funds were being lost, and these issues affected dozens of users. All reimbursements are now complete, with plenty of positive feedback from affected users, and we now have a solid system and procedures in place should something like this happen again. For the extra value this work represents to Bisq, I've increased my usual 14,000 BSQ request to 18,000 this month. I intend to reduce it back to the normal level next month.
The following are roles I am responsible for, with links to my monthly report about each.
(Links to be added when my monthly reports are complete)
The text was updated successfully, but these errors were encountered: