Looks fine so far.

The fonts thing is not dramatic, you will just fall back to another fonts.

The version tag thing, I also get, but I never had problems with the bot not running. So I guess we can rule out that.

When the bot is running, I will show
run bots
every now and then. But apparently for some reasons your but is not running. I guess you have to wait for alt (the creator) for an answer or further debugging advice.

Quote from: mostar on May 21, 2017, 09:23:15 AM
I'm trying to you the site (vs the app)
Enable bot is selected.
I set my Spread , Order Balance and press execute but nothing happen!
Am I missing something?

First thing to do is to open the javascript console to check for any log messages. Post the log along with your problem, that helps a lot to isolate the problem.
Search for web console <your browser>  if you don't know how to open the console.

Quote from: alt on May 10, 2017, 11:44:02 AM
got it, I will provide all these native data, and give the choice to users.

Quote from: 8ejM on May 09, 2017, 02:18:23 PM
A guess you mean the ticker feed on top of the poloniex api page (https://poloniex.com/support/api/). And you take the "last" trade value, right? What about

Code Select Expand

("lowestAsk" + "highestBid")/2 . This could get a little better prices.

Great, thanks a lot!
+5%

Quote from: Bhuz on May 10, 2017, 12:08:20 PM

Quote from: 8ejM on May 10, 2017, 11:31:23 AM
Hi,
...

Hi and welcome!

First, this is completely Off Topic, you should had opened a new Topic and post your concerns there, not hijack this thread...
...

Sorry for OT, I will take more care posting.
I think I started the post with "There is a problem with parts of the jobs the witnesses do, and if more money can solve it, it should" and that went a little to far with my post. Will come back when I'm more familiar with everything.

Hi,

I new to Bitshares, so I may fully informed about everything.  I started buying BTS a few days ago, mainly because of bitUSD. I read through the white papers and were especially excited about the pegged assets. I went on an bought a bunch of BTS. Some days later I wanted to buy some bitUSD and bitCNY. I was and still am very confused about market prices below settlement price since I red in the white paper that pegged assets are expected to be traded at at least the price of the underlying asset.
My excitement for bts took a hit, since it didn't seem to behave as outlined in the white paper and it seemed that a lot more market knowledge was needed to buy at a reasonable price and don't get cheated.
Then I learned about the page where pricefeeds where shown and was shocked that feeds are not updated in manners of seconds but minutes, hours, days and even weeks. I saw forced settlements and witnessed a change in settlement price just a minute later. This made me very suspicious.
Then a learned about complaints about witnesses that don't update the price feed and are still official sources of price data.

At the end I stopped trading and will wait till I gathered enough information about the market. I simply don't really trust the data at the moment.

Why am I telling you all this? Because I think its a typical example for someone new to bts. And some will just leave when they feel that something is weird. It is very important that problems like proper price feeds are fixed. When the cryptomarket sees a correction people will give BTS as a possibility for cashing out in fiat a try. If by then these problems are not fixed. We will loose a huge amount of potential users, that never will come back.

If the problem can be solved by throwing more money at it, take both hands a throw as lot money as needed.

A more modular approach might also be a way to achieve better results. I don't know about all tasks of a witness. But would price feed data a task of its own, one could easily drop everybody with poor data quality from the list. Removing bad quality data sources is something a algorithm can do well, you would not have to start voting campaigns on the forum for that. 

Quote from: alt on May 09, 2017, 10:07:51 AM
yes, for OPEN.DASH, simple  use last ticker data from poloniex.
I  have no idea, why it change such more.

Quote from: 8ejM on May 08, 2017, 02:26:13 PM
PS: The price feed is simple last trade ticker data, right? I'm asking, because I see 8% changes up and down:

Code Select Expand

cancel order --- OPEN.DASH USD
because of price: 99.10707803964283 change to 107.90515943227852 ----
new order OPEN.DASH USD  amount: 7.142857142857142 price: 107.90515943227852
cancel order --- OPEN.DASH OPEN.BTC
because of price: 0.06632999839798 change to 0.07240041489940716 ----

The price goes down a few seconds again.

Maybe it would be better than to exclude mini trades from the feed, so that only trades >$100 are taken into account.

A guess you mean the ticker feed on top of the poloniex api page (https://poloniex.com/support/api/). And you take the "last" trade value, right? What about ("lowestAsk" + "highestBid")/2 . This could get a little better prices.

Quote from: alt on May 09, 2017, 10:03:36 AM
these is the logic, if the client can't get the newest block  in time, it will pause the bot,

Quote from: 8ejM on May 08, 2017, 01:32:08 PM
Hi alt,

thank you for your work, I think one can't overestimate the value the rise in liquidity brought to bitshares by your software.
I see that it's pretty work-in-progress. And want to make a few wishes, if I may:

* An oversight of all available markets with informations about the used price feed.
I was trading DASH the other day, low liquidity there still, and was a bit worried about the price feed quality. Sometimes the prices changed but my bots didn't react. Other bots seemed not to follow the same feed, and some actions observed with others bots didn't seem to make sense. Maybe everything is alright, but I'm lacking these informations about the price feed to throw real money at such a market.

PS: I saw you writing, that Dash price feed is the poloniex data.

* Safeguard against bad or broken connections:
The main reason I halted trading for now is that I assume my connection to be poor. I don't know if I get all feeds on time and sometimes the websocket connection is lost which leaves open orders unattended. It would be nice if the client would be able to recognize delayed data (maybe a timestamp in the feed data) and missed data (if that can be the possible in websocket, maybe a index number in the feed data). Any of these events, plus the worst case a broken websocket connection, could set the client in emergency mode, making him desperately try to reconnect and cancel all orders immediately.

Does "pause the bot" mean that he will cancel all open orders? That would be awesome.

Quote from: alt on May 09, 2017, 09:57:38 AM
seems the price change much after you halt your computer.
but bots can't update your order when your browser is not acitve, because all code is running in the client side.
so when you open btsbots.com again, the bots update the old orders.

Quote from: 8ejM on May 09, 2017, 06:10:52 AM
Also the bot seems to refer to the price of the last session under some circumstances:

Code Select Expand


run bots
new order OPEN.DASH BTS  amount: 7.500000000000001 price: 2628.9024795702967
new order OPEN.DASH USD  amount: 7.499999999999999 price: 124.16536069244391
run bots
cancel order --- OPEN.DASH BTS
because of price: 2628.9024786666664 change to 1985.2493480088676 ----
new order OPEN.DASH BTS  amount: 7.5 price: 1985.2493480088676
cancel order ---- OPEN.DASH USD
because of price: 124.1653601655538 change to 93.76506100000002 -----
new order OPEN.DASH USD  amount: 7.5 price: 93.76506100000002


See the price drop from 2629 to 1985 and 124 to 94 just after starting the bot. Bad thing is, orders were given before correction occurs. Nothing happend this time but this could result in huge losses.

Debug info:
Computer was turned off after last session, restarted and reconnected after about 12h, ip should also be a new one.

Hi Alt,

no, I know,  so I normally cancel all orders from my wallet after stopping all bots and closing the connection (I reckon closing the tab also closes the active websocket connection). So there were no old orders.
The log I was providing is the log of a just freshly started bot (after complete shutdown of the computer and 12h). The bot gave these orders just after start up and canceled them just after that, when he got a new price. But presumable the old price was saved from the former session and used until new price feeds went in and corrected the situation. Just guessing.

But I can assure you that there were no open orders from the last session when I started the bot. I know from my own experience that users sometimes are confident that a setup was like this or that and rule out any user error. But I'm 100% confident there were no old orders simply because there were no 15 DASH on that account in the last session.

Thanks for looking into this.

Also the bot seems to refer to the price of the last session under some circumstances:


run bots
new order OPEN.DASH BTS  amount: 7.500000000000001 price: 2628.9024795702967
new order OPEN.DASH USD  amount: 7.499999999999999 price: 124.16536069244391
run bots
cancel order --- OPEN.DASH BTS
because of price: 2628.9024786666664 change to 1985.2493480088676 ----
new order OPEN.DASH BTS  amount: 7.5 price: 1985.2493480088676
cancel order ---- OPEN.DASH USD
because of price: 124.1653601655538 change to 93.76506100000002 -----
new order OPEN.DASH USD  amount: 7.5 price: 93.76506100000002


See the price drop from 2629 to 1985 and 124 to 94 just after starting the bot. Bad thing is, orders were given before correction occurs. Nothing happend this time but this could result in huge losses.

Debug info:
Computer was turned off after last session, restarted and reconnected after about 12h, ip should also be a new one.

PS: The price feed is simple last trade ticker data, right? I'm asking, because I see 8% changes up and down:

cancel order --- OPEN.DASH USD
because of price: 99.10707803964283 change to 107.90515943227852 ----
new order OPEN.DASH USD  amount: 7.142857142857142 price: 107.90515943227852
cancel order --- OPEN.DASH OPEN.BTC
because of price: 0.06632999839798 change to 0.07240041489940716 ----

The price goes down a few seconds again.

Maybe it would be better than to exclude mini trades from the feed, so that only trades >$100 are taken into account.

Hi alt,

thank you for your work, I think one can't overestimate the value the rise in liquidity brought to bitshares by your software.
I see that it's pretty work-in-progress. And want to make a few wishes, if I may:

* An oversight of all available markets with informations about the used price feed.
I was trading DASH the other day, low liquidity there still, and was a bit worried about the price feed quality. Sometimes the prices changed but my bots didn't react. Other bots seemed not to follow the same feed, and some actions observed with others bots didn't seem to make sense. Maybe everything is alright, but I'm lacking these informations about the price feed to throw real money at such a market.

PS: I saw you writing, that Dash price feed is the poloniex data.

* Safeguard against bad or broken connections:
The main reason I halted trading for now is that I assume my connection to be poor. I don't know if I get all feeds on time and sometimes the websocket connection is lost which leaves open orders unattended. It would be nice if the client would be able to recognize delayed data (maybe a timestamp in the feed data) and missed data (if that can be the possible in websocket, maybe a index number in the feed data). Any of these events, plus the worst case a broken websocket connection, could set the client in emergency mode, making him desperately try to reconnect and cancel all orders immediately.

Hi,

I'm quite new to bitshares and still not very familiar with everything.

But I just saw this thread on reddit

https://www.reddit.com/r/btc/comments/69318u/save_the_chain_enclosed_1_mb_transaction_with_273/

where someone created a >1MB transaction and asked others to append dependent transactions (including one of the outputs of the transaction) to donate for bigger blocks.

Someone else

https://www.reddit.com/r/btc/comments/69318u/save_the_chain_enclosed_1_mb_transaction_with_273/dh3z4ml/
(same thread)

called for a future market on the inclusion of this block (which would be a hard fork to bigger blocks event) to be established to let the market raise its voice about the issue.

I was just wondering if it would be possible inside the bitshare environment to create such a token, that is tied to an output of a bigger block dependent transaction. That would be the asked for future market token.

If we could get this working, bitshares would get a lot of attention is guess.

Just an idea that just came to my mind. I think for making it work it has to be implemented fast.

The problem I see at the moment that an output of an transaction that is not included in the blockchain is worthless, since the input can still be spent.