Incentivising Liquidity

[theredpill]

I keep saying it and will say it again.

We need relative orders that allow orders to be placed in relation to the feed price and then move with it.

If you had a script that did that, but you had to pay a transaction fee when the price drifted by some value from the original, would you use it?

It can be implemented using your own server (I'd make a worker to write the tool and split it with xeroc for using his library). But without a hardfork and some serious coding, it isn't immediately implementable on the chain.

I'm against this because put a lot of trust in the publishing feeds and risk on the system since witness could easily manipulate the feed and run with a lot of money. Also this can easily be work around using third part tools or bots.

I'm actually talking about making a third party tool or bot to do what jonny's asking since you can't do it on the chain.

That's a fair concern about relying on someone else's data. You could use your own feed so it doesn't rely on anyone else.

Yes I see now, I get confused by the hardfork part. About paying fee when price drifted, this gonna be solved by proposal #1 of BM. (except for anti-spam fee)

[btstip]

Hey rgcrypto, here are the results of your tips...

• theredpill: has been credited 1 FISTBUMP
• theredpill: has been credited 1 HIGHFIVE
• theredpill: has been credited 50 BTS

Curious about BtsTip? Visit us at http://sharebits.io and start tipping BTS on https://bitsharestalk.org/ today!

Source: https://bitsharestalk.org/index.php/topic,20394.msg263306/topicseen.html#msg263306

Created by hybridd

[rgcrypto]

Now it is time for take the ass off the chair and make the world we wish to see.

#sharebits "theredpill" 1 FISTBUMP
#sharebits "theredpill" 1 HIGHFIVE
#sharebits "theredpill" 50 BTS

[maqifrnswa]

I keep saying it and will say it again.

We need relative orders that allow orders to be placed in relation to the feed price and then move with it.

If you had a script that did that, but you had to pay a transaction fee when the price drifted by some value from the original, would you use it?

It can be implemented using your own server (I'd make a worker to write the tool and split it with xeroc for using his library). But without a hardfork and some serious coding, it isn't immediately implementable on the chain.

I'm against this because put a lot of trust in the publishing feeds and risk on the system since witness could easily manipulate the feed and run with a lot of money. Also this can easily be work around using third part tools or bots.

I'm actually talking about making a third party tool or bot to do what jonny's asking since you can't do it on the chain.

That's a fair concern about relying on someone else's data. You could use your own feed so it doesn't rely on anyone else.

[theredpill]

Really? Do you have a list?

I think metaexchange, but anyway we just start BTS 2.0, the system is in its infancy now, there's lots of tools coming out soon. I for instance am building something. Now it is time for take the ass off the chair and make the world we wish to see.

[tonyk]

I keep saying it and will say it again.

We need relative orders that allow orders to be placed in relation to the feed price and then move with it.

If you had a script that did that, but you had to pay a transaction fee when the price drifted by some value from the original, would you use it?

It can be implemented using your own server (I'd make a worker to write the tool and split it with xeroc for using his library). But without a hardfork and some serious coding, it isn't immediately implementable on the chain.

I'm against this because put a lot of trust in the publishing feeds and risk on the system since witness could easily manipulate the feed and run with a lot of money. Also this can easily be work around using third part tools or bots.

Really? Do you have a list?

[theredpill]

I keep saying it and will say it again.

We need relative orders that allow orders to be placed in relation to the feed price and then move with it.

If you had a script that did that, but you had to pay a transaction fee when the price drifted by some value from the original, would you use it?

It can be implemented using your own server (I'd make a worker to write the tool and split it with xeroc for using his library). But without a hardfork and some serious coding, it isn't immediately implementable on the chain.

I'm against this because put a lot of trust in the publishing feeds and risk on the system since witness could easily manipulate the feed and run with a lot of money. Also this can easily be work around using third part tools or bots.

[maqifrnswa]

I keep saying it and will say it again.

We need relative orders that allow orders to be placed in relation to the feed price and then move with it.

If you had a script that did that, but you had to pay a transaction fee when the price drifted by some value from the original, would you use it?

It can be implemented using your own server (I'd make a worker to write the tool and split it with xeroc for using his library). But without a hardfork and some serious coding, it isn't immediately implementable on the chain.

[clayop]

I think the first step is to not charge nothing (except anti-spam prevention) for operations that locks up money in the system, like borrow, vesting or making our order book.

Reducing call order update fee was discussed among committee members, and bitcrab did a survey IIRC.

And... ?

I remember there are many support for reducing the fee. I will input committee about this again.

[Helikopterben]

I'm thinking give the incentive only to the short-seller-maker to reduce the premium and compensate for the added risk inherent with the short side in bitshares.

Clever idea, but how do you identify whether a maker is also a short seller? Any short position may be unrelated to a given trade.

Good point.  Maybe require the account to have 100% of the asset collateralized to qualify for the rebate.  In other words, if you put an order on the books to sell $1, then you need to have at least $1 in debt to qualify. Obviously this wouldnt be perfect because users would only need debt relative to their ask size but i'm sure there may be other ways to do this.

[theredpill]

I think the first step is to not charge nothing (except anti-spam prevention) for operations that locks up money in the system, like borrow, vesting or making our order book.

Reducing call order update fee was discussed among committee members, and bitcrab did a survey IIRC.

And... ?

[clayop]

I think the first step is to not charge nothing (except anti-spam prevention) for operations that locks up money in the system, like borrow, vesting or making our order book.

Reducing call order update fee was discussed among committee members, and bitcrab did a survey IIRC.

[theredpill]

I think the first step is to not charge nothing (except anti-spam prevention) for operations that locks up money in the system, like borrow, vesting or making our order book.

[theredpill]

http://www.investopedia.com/articles/active-trading/042414/what-makertaker-fees-mean-you.asp

The maker-taker plan harks back to 1997, when Island Electronic Communications Network creator Joshua Levine designed a pricing model aimed to give providers an incentive to trade in markets with narrow spreads. Under this scenario, makers would receive a $0.002/share rebate and takers would pay a $0.003/share fee, and the exchange would keep the $0.001/share difference. By the mid-2000s, rebate capture strategies had emerged as a staple of market incentive features, with payments ranging from 20 to 30 cents for every 100 shares traded.

I'm thinking give the incentive only to the short-seller-maker to reduce the premium and compensate for the added risk inherent with the short side in bitshares.

Meanwhile we keep charging 40 BTS for borrow and update collateral... That's odd.

[clayop]

Great idea... and if we ever come to have easy-to-use market maker bots built into the wallet, this could allow massive crowd-sourced liquidity.

I support this. Users can define reference feed price, relative or absolute price, tolerance, maximum iteration, and then create MM bot (or relative order).