-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback on latest fee change #4
Comments
This is a head-play, but I want to show how you can constructively tackle the situation. In the following tables we show the old fee set in 2016, the new fee with the currently pending proposal and the factor of the increase compared to the old fee and a suggestion incorporating current feedback Reduce end user charge
Increase business charge
Roll out smoothlyUpdate over a period of 3 months, with one update each month, scale linearly. |
While we agree that Gateways should burden the majority of the blockchain's costs, I think that the proposed asset_issue fee is too high. Would suggest a USD value of 0.065 which is an increase of 3.61x of the Old fee (2016) and an increase of 1.3x of the New fee #2. I think the other fees, especially the asset create fees are reasonable and fine. |
limit_order_cancel pricing is the greatest issue dex faces Why?
I propose that effective bootstrapping of a market requires absolutely no less than 100k annual operations.
This gives liquidity provider option to move one order every 5 minutes. Anything less than this... it becomes challenging to provide dynamic liquidity in fast paced crypto markets. I would like to note here... in CEX markets... the algorithms which I experienced building for client to promote their wares over past 8 years or so would keep 10 orders on each side of book and move and randomize their size independently every minute to give the "sense" that there many market participants urgently seeking to jockey for best position.
This is what creates those happy dancing orderbooks you always see in CEX land... it is not individuals doing this... I can assure you it is liquidity providers using algo to pose as individuals to keep these books alive; all day every day. So lets rewind... these numbers are not easy to grok:
so lets speak in annual fee on 100k operations. previously we were $10 per 100k cancel ops the "new fee #2" $100 per 100k cancel ops So right here... I see that a choice to bootstrap a low volume market - mind you there is a degree to which this is "speculative activism" not "profit motive" now base flat fee cost to provider is between $100 and $1000; and this is not happy dancing CEX style orderbooks... it is 5 minute updates of 1 order. "Happy Dancing" orderbooks would cost up to $10k just for cancellation and up to $100k if all orders filled. So happy dancing is immediately out of the question. so these are my concerns and I stop here with regard to "what fee should be"; do as you will... keep in mind if you like to see happy dancing books in low cap markets it must be cost effectiveNo FUD, no complaints about existing fees without providing a solution. I agree and I do not wish to FUD anything; I seek solutions outside of the current fee structure paradigm, hopefully this discussion is in place and not out of context of this "issue"
So minimum amount_to_sell Bitshares is 1 BTS precision = 5 but minimum amount_to_sell OPEN.BTC is: OPEN.BTC precision = 8 In this way the backend can automatically reject orders for "spam size" amounts. This same utility will be found at ANY centralized exchange to prevent spam. Bitshares DEX woefully neglects this principle. just because the "precision" of OPEN.BTC is 0.00000001 does NOT mean we should have the option to place order sizes of 1 satoshi, and pay the same fee, and cause the same chain bloat, as a serious market participant.
Conclusion is we can find technical ways to use market forces - aside from increasing flat fees - to encourage users to place only orders that matter: stage 1) stage 2) stage 3) It is time to realize the dream. |
@litepresence fantastic contribution thankyou. |
In light of recent discussion I want to create an issue to actually collect constructive feedback. This discussion must take place in the USD denominated fee realm and assume regular update to keep the peg.
No FUD, no complaints about existing fees without providing a solution.
The text was updated successfully, but these errors were encountered: