[bisq-network/proposals] Listing fee policy - step 1 (general) (#35)

The Blur Network notifications at github.com
Sat Aug 18 20:30:33 UTC 2018


If I may, I would like to weigh in on only the portion of this debate that affects Blur Network and the other currently proposed PRs that are in Limbo, currently. 

Specifically with reference to applying a retroactive 1BTC fee, in the manner @cbeams has suggested: 

>Retroactively apply this policy to all current open asset listing PRs. i.e. add a comment to each PR letting the submitter know that if they get their fee paid before Aug X, their asset will make it into v0.7.2. And that if not, it can make the next release.

This seems terribly biased in favor of certain assets -- namely, Conceal $CCX.  I would ask, in fairness, if a 1 BTC fee is to be applied retroactively... That those parties required to pay the fee, should include all assets who have submitted PRs since the last release 0.7.1.  

The specification of "open PRs" is troublesome. Especially if one looks at the fact that the only non-paying party would include CCX.   How would this apply to BLUR, as an asset?  A simple unwillingness to merge the final PR, when 2/3 PRs have been merged for listing of BLUR (see: bisq-network/bisq-desktop/pull/1617 and bisq-network/bisq-core/pull/142) seems a poor reason to be required to pay such a fee. 

@ManfredKarrer noted that conventions were followed, and the only PR remaining is bisq-network/bisq-assets/pull/58.  Such practices will cause many projects, Blur included, to wonder why there is a single man acting as the gatekeeper on a Decentralized Exchange... that is now charging a 1 BTC fee in a way that so clearly favors a single party. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/35#issuecomment-414084506
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180818/d4622ca9/attachment.html>


More information about the bisq-github mailing list