[bisq-network/proposals] Add bonus payment for seed nodes operators when node has 99.9% availibility (#102)

mrosseel notifications at github.com
Fri Jul 26 10:40:39 UTC 2019

>     * base compensation: operating costs + 50 BSQ?
>       * might prevent the use of cheap hosting providers
>       * but might need an upper limit though. Maybe insert common operating costs of DigitalOcean, Linode, ...?

sounds good, it does not prevent the use of cheap hosting providers but also doesn't encourage it. People will just choose the best tool for the job. Upper limit probably around 70/100 BSQ

>     * setup 400 BSQ (so people do a decent job)

Not so sure, not doing a good job during setup will impact availability, which is a monthly bounty so setup fee is not so important. I propose not to pay this.

>     * bonus on 95% availability: 150 BSQ (to be discussed on how we evaluate that)

this is 36 hours of outage (if I calculated correctly). Should this get a bounty?
>     * bonus on 99% availability: 350 BSQ (to be discussed on how we evaluate that)

This is 7 hours of outage. Probably ok to give a bounty. 

In short I'm fine with this, of course what if your seednode is down due to bugs, tor errors, ... - measuring will be the hard part. You can easily measure if you're better than needed, but if worse than needed you might need to give some proof in your componsation request that the downtime was due to bisq and not you or your hosting situation.

In the long run my opinion is that seednodes should not be precious porcelain servers that need 99% uptime, too easy to disrupt the network. Ideally they are just the longest running bisq instances. If they are down, clients connect to the next one. The BSQ changes with full nodes/blocknotify didn't bring this dream any closer of course, but IMHO it should be a long term goal, so we shouldn't get too attached to our bonuses ;)

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190726/95b771ff/attachment.html>

More information about the bisq-github mailing list