@cbeams on leave 05.19–06.02

[cbeams]

This memo is written mainly for team leads, but several other contributors are @mentioned along the way and contributors in general may be interested in its content.

@bisq-network/team-leads, I'm going to take the next two weeks away from the project as completely as possible. This is on short notice and probably not the best timing, but it's important. Nothing bad has happened and my health is OK, but for a number of reasons I've become ineffective in my work and I need to take a proper break.

Priorities while I'm away

Please help keep the ball rolling on the key efforts listed below; see your inline @mentions.

Victim repayment

1. Finish reviewing and testing the filter-based repayment PR at [WIP] Add list to filter to set btc fee receiver addresses bisq#4150
2. Ship it in v1.3.5
3. Once it is live in production, ensure that repayments are working as expected using @jmacxx's repayment tracking HTML report
4. Let the victims know that repayments have begun (I have Keybase DM's open with each of them, this is something I can come back and do quickly).

@sqrrm, can you own this? I know you've already done at least some review work, and you'd be on point to do the release in any case. This is not so urgent that it should force an early release, but it would be good to get in production as soon we can responsibly do so.

Trade protocol security audit

Of the several initial security team efforts mentioned in #75, I believe the trade protocol security audit is the most important.

• @stejbac and @sqrrm should write up an audit methodology / plan for a start, and that should be circulated for review to make sure we have the best ideas about how to do it.
• others can be recruited to help execute that plan. I know @cd2357 is interested. Perhaps @devinbileck can be of help too.

Support anything Oscar needs in his SegWit design project

@sqrrm and I have green-lit 4k of budget for @oscarguindzberg to spend 40 hours designing the upgrade to BitcoinJ 0.15 and getting SegWit support into Bisq. There shouldn't be a lot of hand-holding necessary here, but anything he needs to succeed should get addressed swiftly. See bisq-network/projects#34.

Note to @dmos62: this work is (or can become) closely related to your proposal to introduce an abstraction layer between Bisq and BitcoinJ. You're invited to track this effort and participate in any way you and Oscar see fit.

Backfilling the Refund Agent / Arbitrator role

I'm in ongoing communication with the current refund agent about this. There is still no candidate for his replacement. He says he will continue with the role for now, i.e. he won't revoke his key and leave us high and dry, but if he gets too busy, he may start telling traders that they have to request reimbursement through the DAO on their own.

@m52go, could you write up a wiki article instructing traders how to request reimbursement through the DAO, and in turn how to coordinate trading the BSQ they receive with @burningman2 / @burningman3 for BTC? And could you then share the link to that document with @RefundAgent so he has it if it becomes necessary?

See also my note below about a proposal I'm going to create for improving refund agent / arbitrator incentives.

Team lead meetings

Please hold these meetings if you see fit during the regular Thursday time slot, and I'd recommend continuing with the simple prioritization exercise we did in bisq-network/teamleads#1. While @ripcurlx is away it would only be @m52go, @wiz and @sqrrm meeting, but still, if you find it valuable, please don't skip it just because I'm not there.

What I'll handle before I go offline

• My reviews for Cycle 13 compensation requests
• Green-light @oscarguindzberg's segwit design project
• Submit proposal to improve incentives for the refund agent / arbitrator role
• Review @ghubstan's outstanding API PRs
• Queue up further API work for @ghubstan
• Review @m52go and @jmacxx's compensation request automation work at Make compensation requests programattically parsable projects#32 (comment)

I plan to wrap these things up no later than Monday and to begin my break on Tuesday the 19th. If you see anything missing from the above that you think I should handle before going offline, please let me know immediately.

How to reach me

I plan to remain logged out of Keybase and I will disable GitHub email notifications for the duration of my leave. If something comes up that needs my immediate attention, please send me an email directly or get me via Signal.

---

Please give a 👍 below if you've read this and agree to what's been asked of you via @mention. If not, please comment to that effect or otherwise let me know by EOD Monday. Thanks.

[cbeams]

Closing as complete, i.e. that I've checked all my boxes above. Cheers all, see you in a couple weeks!