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

[Gandalf86]

Instead of hard-coding the coin listings in the source code, would there maybe be a way to evolve Bisq into a federated protocol where users register their trading pair on the network themselves? That way it would save you guys time having to merge pull requests, and would scale infinitely. I would imagine it like a distributed database (DHT, blockchain, ...) where people associate an ID with the metadata for trading their crypto token and publish it in the network. To trade, other users can do a distributed search to fetch the metadata and do trades with other users. The ID would be freed and removed from the database when there have been no active orders (or trades) for a certain period of time. Coin developers would have to take care for themselves that the associated data is correct and functional, and provide the correct market ID to their users.

A listing fee comes with serious problems for small community projects like the one I am active in, called Wisp. We selected Bisq as our only exchange to be listed on in the future, because it is the only exchange that matches with our vision of decentralization and trustlessness. We are not listed on any other exchange, and we have hardly the funds for paying our own developers, let alone having one "spare" BTC to spend on a Bisq listing. We are all working on it in our spare time. Without being listed on any exchange, there is no way to attract users into the project and build up volume over a period of months.

Such a project depends on being able to join an open network to trade with other users, which I think is what Bisq was originally about. If Bisq was to introduce development fees, I am sure it would be cloned on the long term to build a second network without fees, because some projects simply depend on this possibility.

-- 
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-416150157
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180827/cd04a932/attachment-0001.html>