Author Topic: more professional price feed?  (Read 27764 times)

0 Members and 1 Guest are viewing this topic.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4653
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
There are rumors that btc38 is hacked.
BitShares committee member: abit
BitShares witness: in.abit

Offline Bhuz

  • Committee member
  • Sr. Member
  • *
  • Posts: 467
    • View Profile
  • BitShares: bhuz
More info.. btc38 API server now returns no data. They upgraded?

This seems to be the issue atm, I have btc38 and yunbi as sources for the CNY market, but btc38 doesn't give any data.

Offline Bhuz

  • Committee member
  • Sr. Member
  • *
  • Posts: 467
    • View Profile
  • BitShares: bhuz
I don't know it's because of  a wrong configure file or a bug of the script.
but this is not the first time it happened. I can't remember how many times I have mentioned the witness.
include this forum and telegram.
nobody want to take responsibility  for this error, so I have to remove the witness every time this happen.
I can find some old post about this:
https://bitsharestalk.org/index.php/topic,20704.msg267158.html#msg267158
https://bitsharestalk.org/index.php/topic,21315.msg276995.html#msg276995

I get this type of reply every time:
many witness publish a wrong price

Since you seem to be an authority on the subject, could you please enlighten us witnesses what the right price is?

I can publish a price of 0.0245 CNY/BTS all week if you think that's better.

The issue here is probably due to chinese exchanges not responding to our requests. This fact obviously limits the number of exhanges that the script can evaluate for deriving the price of the asset.
Only Chinese exchanges give this kind of issue to me... Ideas to fix those are welcome :)

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4653
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
More info.. btc38 API server now returns no data. They upgraded?

//Update: btc38 announced that due to server issues they're currently shutdown all markets, will probably resume at 0:00 Beijing time.
« Last Edit: December 21, 2016, 10:01:56 am by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4653
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
I don't know it's because of  a wrong configure file or a bug of the script.
but this is not the first time it happened. I can't remember how many times I have mentioned the witness.
include this forum and telegram.
nobody want to take responsibility  for this error, so I have to remove the witness every time this happen.
I can find some old post about this:
https://bitsharestalk.org/index.php/topic,20704.msg267158.html#msg267158
https://bitsharestalk.org/index.php/topic,21315.msg276995.html#msg276995

I get this type of reply every time:
many witness publish a wrong price

Since you seem to be an authority on the subject, could you please enlighten us witnesses what the right price is?

I can publish a price of 0.0245 CNY/BTS all week if you think that's better.

I have the same settings as DataSecurityNode,

  "CNY" : {
                    "metric" : "weighted",
                    "sources" : ["btc38",
                                 "yunbi",
                                 "huobi",
                                 "btcchina",
                                 "okcoin",
                                 ]
                },


Should we remove yunbi?
According to coinmarketcap  +80% of the volume is on btc38 and polo (BTS/BTC).

Actually with CNY you don't need huobi and btcc and okcoin anymore, if you don't have poloniex as a source, because yunbi and btc38 are both now not running BTS/BTC pair but only BTS/CNY pair.

So, the workaround would be something like these:
Code: [Select]
                   "CNY" : {
                       "metric" : "weighted",
                       "sources" : ["btc38",
                                    "yunbi",
                                   ]
                   },

feedSources["btc38"]    = feedsources.Btc38(allowFailure=False)

(Set btc38 as primary feed source and don't "allowFailure")

Or
Code: [Select]
                   "CNY" : {
                       "metric" : "weighted",
                       "sources" : ["btc38",
                                    "yunbi",
                                    "huobi",
                                    "btcchina",
                                    "okcoin",
                                    "poloniex",
                                    "bittrex",
                                   ]
                   },
(btc38 + poloniex + bittrex weighted)

@xeroc please advise.

//Edit: added bittrex
« Last Edit: December 21, 2016, 09:14:56 am by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline ElMato

  • Sr. Member
  • ****
  • Posts: 288
    • View Profile
I don't know it's because of  a wrong configure file or a bug of the script.
but this is not the first time it happened. I can't remember how many times I have mentioned the witness.
include this forum and telegram.
nobody want to take responsibility  for this error, so I have to remove the witness every time this happen.
I can find some old post about this:
https://bitsharestalk.org/index.php/topic,20704.msg267158.html#msg267158
https://bitsharestalk.org/index.php/topic,21315.msg276995.html#msg276995

I get this type of reply every time:
many witness publish a wrong price

Since you seem to be an authority on the subject, could you please enlighten us witnesses what the right price is?

I can publish a price of 0.0245 CNY/BTS all week if you think that's better.

I have the same settings as DataSecurityNode,

  "CNY" : {
                    "metric" : "weighted",
                    "sources" : ["btc38",
                                 "yunbi",
                                 "huobi",
                                 "btcchina",
                                 "okcoin",
                                 ]
                },


Should we remove yunbi?
According to coinmarketcap  +80% of the volume is on btc38 and polo (BTS/BTC).




Offline sasashui

  • Sr. Member
  • ****
  • Posts: 205
  • BTS ID : sasashui
    • View Profile
  • BitShares: sasashui
I don't know it's because of  a wrong configure file or a bug of the script.
but this is not the first time it happened. I can't remember how many times I have mentioned the witness.
include this forum and telegram.
nobody want to take responsibility  for this error, so I have to remove the witness every time this happen.
I can find some old post about this:
https://bitsharestalk.org/index.php/topic,20704.msg267158.html#msg267158
https://bitsharestalk.org/index.php/topic,21315.msg276995.html#msg276995

I get this type of reply every time:
many witness publish a wrong price

Since you seem to be an authority on the subject, could you please enlighten us witnesses what the right price is?

I can publish a price of 0.0245 CNY/BTS all week if you think that's better.

+5%

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
I don't know it's because of  a wrong configure file or a bug of the script.
but this is not the first time it happened. I can't remember how many times I have mentioned the witness.
include this forum and telegram.
nobody want to take responsibility  for this error, so I have to remove the witness every time this happen.
I can find some old post about this:
https://bitsharestalk.org/index.php/topic,20704.msg267158.html#msg267158
https://bitsharestalk.org/index.php/topic,21315.msg276995.html#msg276995

I get this type of reply every time:
many witness publish a wrong price

Since you seem to be an authority on the subject, could you please enlighten us witnesses what the right price is?

I can publish a price of 0.0245 CNY/BTS all week if you think that's better.
« Last Edit: December 21, 2016, 03:12:06 am by alt »

Offline BunkerChainLabs-DataSecurityNode

this happened  many times, the price wrong more then 10%.
every time I point this out, the answer is why you think your price is correct and mine is wrong?
so I just cancel my vote for these witness.

thanks bitcrab, I will remove these witness this time:
spectral delegate-clayop bhuz bue delegate.ihashfury spartako fox elmato datasecuritynode

                "CNY" : {
                    "metric" : "weighted",
                    "sources" : ["btc38",
                                 "yunbi",
                                 "huobi",
                                 "btcchina",
                                 "okcoin",
                                 ]

All of these are enabled on datasecuritynode.. problem is only one of them is responding at the moment. I think the others will chime in soon enough on this matter when they see the same I did.

This is the first time *I* have seen where only one was responding like this. I appreciate the attention given to explaining things, but the conclusions made in assuming that witnesses have chosen to "just get" one source is outright presumptuous and false.

@alt  I never had your vote before so not sure why you are saying now you are removing your vote for datasecuritynode. I think this seems a bit over the top... not to mention all those witnesses are long time trusted ones. This whole thread of single source feed accusations is really what is the disappointing result from this test.

How about a simple note at the end asking witnesses to check their feeds instead? Here instead we find false accusations and others claiming to vote them out. Not to mention the thread title is insulting as well. Again, not helpful. Appreciate all you guys do, but this could have been handled better.

Oh, there is a telegram witness channel that could have been used too.. instead of the public display.. you have access to it and could have directly contacted the witnesses in question. Instead a public post to bring about less public confidence? Really? Could have been handled better.

+-+-+-+-+-+-+-+-+-+-+
www.Peerplays.com | Decentralized Gaming Built with Graphene - Now with BookiePro and Sweeps!
+-+-+-+-+-+-+-+-+-+-+

Offline mea123

  • Full Member
  • ***
  • Posts: 82
    • View Profile
  • BitShares: mea123


I am not an expert, nor do I understand a lot about what you talking about,
but I know one thing, I trade for more than 7 years Forex and more than 20 years Stocks.
if you cant trust the system, because one dont get the right price, people will look for one they think they can trust...I hope I did understand the point right
if you provide an exchange you better get it right, and the exchange on OL is far from good, let stand from perfect
I am an Obits and more investor and as an investor I like seeing thing work, if they don't I have to move on and believe me most people don't like OL exchange, that's why they dont become
account-holders to begin with, the exchange has to change for much better and more reliable

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
this happened  many times, the price wrong more then 10%.
every time I point this out, the answer is why you think your price is correct and mine is wrong?
so I just cancel my vote for these witness.

thanks bitcrab, I will remove these witness this time:
spectral delegate-clayop bhuz bue delegate.ihashfury spartako fox elmato datasecuritynode
« Last Edit: December 20, 2016, 09:15:17 am by alt »

Offline yvv

  • Hero Member
  • *****
  • Posts: 1186
    • View Profile
Who is the witness who publish inaccurate price? Let's vote him down.


Offline bitcrab

  • Committee member
  • Hero Member
  • *
  • Posts: 1926
    • View Profile
  • BitShares: bitcrab
  • GitHub: bitcrab
whether force settlement or margin call happen or not, the feed price should reflect the market price exactly enough, the price info should be collected from multi main exchanges, should not depend on a single exchange, especially when the exchange has very low depth.

and also, instead of directly adapting the last price,  can we develop some advanced algorithm that can reflect the market status more exactly to generate the feed price? as I know alt customized some algorithm in his price feed script, which behaves well, maybe the alogithm can be referenced.   
« Last Edit: December 20, 2016, 07:33:42 am by bitcrab »
Email:bitcrab@qq.com

Offline Chronos

This could be good reason to have forced settlement offset from 100%. It protects shorts against unfair price fees during forced settlement.

Offline bitcrab

  • Committee member
  • Hero Member
  • *
  • Posts: 1926
    • View Profile
  • BitShares: bitcrab
  • GitHub: bitcrab
just did a little test, as yunbi has very low market depth, I bought 1.1BTS at price 0.0289CNY. before that the BTS price of all CNY market is about 0.0283.


then what happened is, a lot of witness began to feed 0.0289 as bitCNY price, and then about half an hour later, the settlement price changed from below 0.0284 to 0.0289.


if our witnesses just get price from yunbi and publish as feed price, then it will be dangerous, yunbi has very low market depth, it will be possible for some people to manipulate the price and make benefit without big difficulty.

hope witnesses can update their feed script to do more professional price feed.
« Last Edit: December 20, 2016, 11:11:01 am by bitcrab »
Email:bitcrab@qq.com