[bisq-network/compensation] For Cycle 33 (Issue #1007)

cbeams notifications at github.com
Tue Feb 22 22:09:47 CET 2022


Thanks, @Emzy. It's a good point that ops doesn't have budget for this per se. Nor does any other team, though, as this is sort of an undefined area.

I've gone ahead and submitted this compensation request to the DAO anyway, with txid `9d7d24ded9923a020e1cfc5affc152434384bd5a3f52aca4897ea0bb23bff034`.

My argument would be that others should vote for it with the proviso that we publish something like @ripcurl suggests above that makes it clear that compensation for disclosures is subject to DAO voting like any other kind of compensation. I'm not sure about budgeting, but in this case it seems like it should be assigned to ops, since it was ops-managed infrastructure in question.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/compensation/issues/1007#issuecomment-1048214041
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/compensation/issues/1007/1048214041 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220222/cdf3011a/attachment-0001.htm>


More information about the bisq-github mailing list