feed price should expired over 1 hour

Started by alt, December 04, 2015, 11:32:19 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

roadscape

Thanks for clearing it up.. makes sense.. for now, I've put in the following settings, and the script runs twice per hour.

maxAgeFeedInSeconds = 24*60*60
change_min = 0.5
http://cryptofresh.com  |  witness: roadscape

xeroc

Quote from: Xeldal on December 06, 2015, 10:10:59 PM
So long as your feed doesn't expire, the time in-between publishing is inconsequential. 

Publishing every minute,  every hour, every 4 hours, 8 hours, or 24 hours makes no difference, if the the actual price has not changed.

Your script should be checking the price often but only publishing if its changed some fraction of a percent from your last published price.

If the feed expires after 24 hours, at a minimum you should obviously publish at least every 24 hours.  More often only when the price has changed.

So then:

maxAgeFeedInSeconds          = 23*59*50  # A feed should be at most 1hour old
change_min                                = 0.5    # Percentage of price change to force an update


Xeldal

#22
So long as your feed doesn't expire, the time in-between publishing is inconsequential. 

Publishing every minute,  every hour, every 4 hours, 8 hours, or 24 hours makes no difference, if the the actual price has not changed.

Your script should be checking the price often but only publishing if its changed some fraction of a percent from your last published price.

If the feed expires after 24 hours, at a minimum you should obviously publish at least every 24 hours.  More often only when the price has changed.

xeroc

I think we may have misunderstood BM earlier.

It is required for settlements that there is at least one feed per 24h .. but for margin calls and 'fair price' we need it more accurate.

However I cant tell you a 'good number'. I. Bts1 I ran the script every 9minutes and had a max age of 15minutes for my feeds

roadscape

Quote from: xeroc on December 05, 2015, 11:03:25 AM
bm and i highly recommend to publish prices more often than just once per hour .. if you want to spare money you can increase the maxage in the script but still run it frequently to catch up with price movements

Did the recommendation change? I thought it was stated before that 24 hours was sufficient and it also helped prevent market manipulation.. just want to make sure I understand
http://cryptofresh.com  |  witness: roadscape

xeroc

Price feeds EXPIRE after 24h .. this setting can be adjusted by the committee for each asset individually ..

bm and i highly recommend to publish prices more often than just once per hour .. if you want to spare money you can increase the maxage in the script but still run it frequently to catch up with price movements

roadscape

I was under the impression that in 2.0 price feeds only need to be updated once per day.
I also thought that a lagging feed had security benefits.. is that not the case?

Also, someone mentioned that BTC38 was blocking them due to rate limiting.. IMO this is a good reason for easing up on feed frequency. (When you don't have permission to scrape someone's site it's best to be conservative... for more than 1 reason)
http://cryptofresh.com  |  witness: roadscape

abit

Quote from: alt on December 04, 2015, 11:32:19 AM
now we have 17 witness, about 11 witness published price at 0.02, but the mdedian price is still 0.0216,
because there are almost 13 wintess don't update price over 1 hour
some of them are voted out, so they can't publish price any more
so you'd better use the price published in 1 hour, or exclude the unactive witness's price

Technically it can be done with a committee proposal. Here are options in bitasset_data:

    "options": {
      "feed_lifetime_sec": 86400,
      "minimum_feeds": 7,
      "force_settlement_delay_sec": 86400,
      "force_settlement_offset_percent": 0,
      "maximum_force_settlement_volume": 200,
      "short_backing_asset": "1.3.0",
      "extensions": [

      ]
    },

It seems that current setting is 24 hours.
BitShares committee member: abit
BitShares witness: in.abit

btstip

Hey 38PTSWarrior, here are the results of your tips...
Curious about ShareBits? Visit us at http://sharebits.io and start tipping BTS on https://bitsharestalk.org/ today!
Created by hybridd

38PTSWarrior

Responsive and proactive!
#sharebits "taoljj" 1 CHATEAUX

btstip

Hey 38PTSWarrior, here are the results of your tips...
Curious about ShareBits? Visit us at http://sharebits.io and start tipping BTS on https://bitsharestalk.org/ today!
Created by hybridd

38PTSWarrior

Responsive and proactive!

#sharebits "taojle" 1 CHATEAUX

taoljj

Updated.

Quote from: clayop on December 04, 2015, 02:52:31 PM
Quote from: taoljj on December 04, 2015, 02:11:26 PM
Quote from: xeroc on December 04, 2015, 12:42:14 PM
I also encourage all witnesses to run the script often .. something between every 5 to 10 minutes (depending in the threshold limits of the exchanges)
For those not knowing: The price feed will only be published if it is of by 0.5% compared to YOUR last price or if the price is too old (15min)


delegate.taolje witness runs  feeds script every 5 minutes.

I'm sorry to update late.

Vote for delegate.taolje for witness!Thanks

Please check your script config (especially Change Max). Yours is 12 hours old now.
BTS      Witness: delegate.taoljj

maqifrnswa

sorry about that, just turned it on for the first time last night (see other post) and the cron job didn't run while I was asleep. fixed now
maintains an Ubuntu PPA: [url="https://launchpad.net/~showard314/+archive/ubuntu/bitshares"]https://launchpad.net/~showard314/+archive/ubuntu/bitshares[/url] [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

clayop

Quote from: taoljj on December 04, 2015, 02:11:26 PM
Quote from: xeroc on December 04, 2015, 12:42:14 PM
I also encourage all witnesses to run the script often .. something between every 5 to 10 minutes (depending in the threshold limits of the exchanges)
For those not knowing: The price feed will only be published if it is of by 0.5% compared to YOUR last price or if the price is too old (15min)


delegate.taolje witness runs  feeds script every 5 minutes.

I'm sorry to update late.

Vote for delegate.taolje for witness!Thanks

Please check your script config (especially Change Max). Yours is 12 hours old now.
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

tonyk

#9
Quote from: taoljj on December 04, 2015, 02:11:26 PM
Quote from: xeroc on December 04, 2015, 12:42:14 PM
I also encourage all witnesses to run the script often .. something between every 5 to 10 minutes (depending in the threshold limits of the exchanges)
For those not knowing: The price feed will only be published if it is of by 0.5% compared to YOUR last price or if the price is too old (15min)


delegate.taolje witness runs  feeds script every 5 minutes.

If you have updated, it seems like a good idea to publish feed every 3-4 hours (for 0.02 BTS fee,) even if you are not active witness.

I'm sorry to update late.

Vote for delegate.taolje for witness!Thanks

5 mins and apparently the old script...your feed is way off for CNY, even if you check every 10 sec.
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

taoljj

#8
Quote from: xeroc on December 04, 2015, 12:42:14 PM
I also encourage all witnesses to run the script often .. something between every 5 to 10 minutes (depending in the threshold limits of the exchanges)
For those not knowing: The price feed will only be published if it is of by 0.5% compared to YOUR last price or if the price is too old (15min)


delegate.taolje witness runs  feeds script every 5 minutes.

I'm sorry to update late.

Vote for delegate.taolje for witness!Thanks
BTS      Witness: delegate.taoljj

BunkerChainLabs-DataSecurityNode

Quote from: xeroc on December 04, 2015, 12:42:14 PM
I also encourage all witnesses to run the script often .. something between every 5 to 10 minutes (depending in the threshold limits of the exchanges)
For those not knowing: The price feed will only be published if it is of by 0.5% compared to YOUR last price or if the price is too old (15min)

datasecuritynode witness runs their feeds every 9 minutes. If there is no update it is only because there was no change within the threshold.

Vote for datasecuritynode for witness!
+-+-+-+-+-+-+-+-+-+-+
[url="//www.peerplays.com"]www.Peerplays.com[/url] | Decentralized Gaming Built with Graphene - Now with BookiePro and Sweeps!
+-+-+-+-+-+-+-+-+-+-+

Bhuz

Quote from: hybridd on December 04, 2015, 01:03:25 PM
Question, sorry for off topic, was this script publicly published? I'm interested in having a look at it for learning/educational purposes.

https://github.com/xeroc/python-graphenelib/tree/master/scripts/pricefeeds

hybridd

Quote from: xeroc on December 04, 2015, 12:42:14 PM
I also encourage all witnesses to run the script often .. something between every 5 to 10 minutes (depending in the threshold limits of the exchanges)
For those not knowing: The price feed will only be published if it is of by 0.5% compared to YOUR last price or if the price is too old (15min)

Question, sorry for off topic, was this script publicly published? I'm interested in having a look at it for learning/educational purposes.
[url="http://sharebits.io"]http://sharebits.io[/url] - #sharebits "person" amount asset - Start tipping on bitsharestalk today!
Developer @ Freebie

Moon

Quote from: xeroc on December 04, 2015, 12:42:14 PM
I also encourage all witnesses to run the script often .. something between every 5 to 10 minutes (depending in the threshold limits of the exchanges)
For those not knowing: The price feed will only be published if it is of by 0.5% compared to YOUR last price or if the price is too old (15min)


+5%

xeroc

I also encourage all witnesses to run the script often .. something between every 5 to 10 minutes (depending in the threshold limits of the exchanges)
For those not knowing: The price feed will only be published if it is of by 0.5% compared to YOUR last price or if the price is too old (15min)

bitcrab

agree.
the feed price is more important than before as the forced settlement feature is integrated in GUI. 

alt

#1
now we have 17 witness, about 11 witness published price at 0.02, but the mdedian price is still 0.0216,
because there are almost 13 wintess don't update price over 1 hour
some of them are voted out, so they can't publish price any more
so you'd better use the price published in 1 hour, or exclude the unactive witness's price


SETTLEMENT PRICE – CNY/BTS CER – CNY/BTS MCR MSSR PUBLISHER PUBLISHED
0.02298447 0.02553871 175% 109% delegate-clayop 1 minute ago
0.0216 0.02273684 175% 110% wackou 3 minutes ago
0.02231583 0.02209533 175% 100.1% delegate.baozi 12 minutes ago
0.02191138 0.02306465 175% 110% delegate.ihashfury 16 minutes ago
0.022 0.02315789 175% 110% mr.agsexplorer 23 minutes ago
0.02311899 0.0243358 175% 110% bitcube 24 minutes ago
0.022 0.02315789 175% 110% datasecuritynode 34 minutes ago
0.02298819 0.02419817 175% 110% spartako 39 minutes ago
0.02313387 0.0243546 175% 110% in.abit 1 hour ago
0.022 0.02315789 175% 110% harvey-xts 1 hour ago
0.02309527 0.02431086 175% 110% bhuz 1 hour ago
0.0223 0.02347368 175% 110% rnglab 1 hour ago
0.02145233 0.02258149 175% 110% xeldal 2 hours ago
0.02309677 0.02431246 175% 110% mindphlux.witness 2 hours ago
0.0209 0.022 175% 110% delegate-1.lafona 8 hours ago
0.0209 0.022 175% 110% bue 8 hours ago
0.0207955 0.02189061 175% 110% delegate.taolje 8 hours ago
0.02090001 0.02200069 175% 110% spectral 9 hours ago
0.02100204 0.02210759 175% 110% maqifrnswa 9 hours ago
0.02024 0.02130526 175% 110% verbaltech2 9 hours ago
0.02079986 0.02189469 175% 110% dele-puppy 11 hours ago
0.02006944 0.02112576 175% 110% fox 13 hours ago
0.02098738 0.02209231 175% 110% roadscape 15 hours ago
0.02050003 0.02157905 175% 110% cyrano 15 hours ago
0.02089508 0.02199482 175% 110% triox-delegate 16 hours ago