Voting for default data feed providers

[JordanLee]

Dead data feeds are indeed a serious issue for this kind of hard coding of the providers.

True. We will have the software check that a data feed gives a response before assigning it as a default data feed.

There are some other options as well that I will look at to mitigate the issue. Some may make sense for later releases.

@crypto_coiner just wanted to make sure you aware that voting for default data feeds begins in a little over a day if you wish to advance a motion to be considered as a default data provider. Looks like we already have motions from Cybnate, cryptog and masterOfDisaster.

[crypto_coiner]

Thanks for the reminding, yes.

[Sentinelrv]

Also, I will be going on vacation soon and won’t have access to my laptop to add anymore data feed motions. If anybody else is going to join in, please do so soon so I can add you in before I leave. I’m hoping @Nagalim decides to join in as well.

[Eleven]

Hi, @Cybnate, @Cryptog, @crypto_coiner, @masterOfDisaster, is it convenient to provide your motion hash for default data feed provider, data feed url, signature url and signature address. I need collect these informations for the default feed install. Also anyone who want to be the default data feed provider could post their information here. How many candidates for the default data feed providers will be better, so far we have four? Right?

[Nagalim]

I’m working on getting a feed going as well. I should have a definitive answer for myself by tomorrow.

[Dhume]

I was wondering, would it also be possible to get a “default” data feed that is an average of the other “default” data feeds. So say 3 out of the 4 vote in favor of a proposal this datafeed would then also vote for the proposal. Say 1 out of 4 vote in favor of the proposal the “average” data feed would then also abstain voting in favor of the proposal. This would be a nice option for shareholders who are unsure which datafeed to pick but still want automated voting as they would in essence vote in conjuncture with the majority of the data feeds thus guaranteeing only supporting motions for which there is good consensus among feed providers.

It would also help with giving the feed providers more voting power without that power going to a single feed/provider.

[masterOfDisaster]

Hi @Eleven,

here’s the link with data about my data feed:

masterOfDisaster’s B&C datafeed - BETA

Charter masterOfDisaster's B&C datafeed - BETA This is a shameless copy of @Cybnate's data feed with some alterations... Here is the information to subscribe to my experimental datafeed. Please take note of the disclaimer at the bottom before subscribing. The URL needs to be added to the standard B&C client. Source of the data feed & adding it to the client Prefer to copy and paste just once? Try this. Open the debug window of your client and paste all the text in the quote below into it …

Here’s my application as data feed provider:

[Voting] masterOfDisaster's Motion to Apply as Default Datafeed Provider for B&C

This motion represents the candidacy of masterOfDisaster's B&C datafeed to become a default data feed provider for B&C. Voting for this motion will increase the probability that masterOfDisaster's B&C datafeed will be chosen as a default data feed provider upon a specific installation of B&C Exchange version 5. More information about why you should vote for this can be found here: https://discuss.nubits.com/t/voting-for-default-data-feed-providers/3802 To support this motion please add the f…

I can post all requested information here, but I thought linking the source should be preferred.

[Eleven]

Cool, the link is better. Thank you:slight_smile:

[cryptog]

My applicatio is here: [Voting] Cryptog's Motion to Apply as Default Datafeed Provider for B&C

[crypto_coiner]

here: Crypto_Coiner’s B&C Exchange data feeds

[Mark]

The influence of any default data feed provider is not strongly related to the number of installations but to the amount of shares behind these installations. This is a gamble.

Frequency voting seems more fair but let we first try default data feeds.

[Sentinelrv]

Frequency voting seems more fair but let we first try default data feeds.

I see this as more of a temporary measure that needs to be taken. Default data feeds don’t require as much development time, so they’re being implemented as a short-term solution. Frequency voting will take a lot more development time, but it would eventually replace default feeds as the more long-term solution against apathetic voters. At least that’s how I see it.

[Nagalim]

we can combine default data feeds with frequency voting. The original concept of the default for freq voting was to just vote the way the network is voting (call this the ‘absent’ data feed). We could also have default weights for different data feeds in addition to the absent one. So like 20% cryptog, 20% cybnate, 20% crypto_coiner, 20% masterOfDistaster, 20% absent vote. And this would be a random stochastic process every time someone mints a block with the default feed, so it would not be dependent upon how many shares different installations have.

[Cybnate]

@eleven The thread with my B&C feed details is here: Cybnate's B&C datafeed - BETA

[Eleven]

got it. Thanks

[Eleven]

Could you please provide your motion hash ? I did not find in the link page.

[crypto_coiner]

Crypto_Coiner’s Motion to Apply as Default Datafeed Provider: motion hash
0462d8f55b7e59957e2e0c2d77913749383a9bb8

[Nagalim]

Nagalim's B&C datafeed - BETA
67c7b0d207e64923121f4fca8420cffe57b87ed6

[Eleven]

so far I got the statical information.
getdatafeedproviders
{
“providersamount” : 4,
“totalblocks” : 3985,
“providers” : [
{
“provider” : “crypto_coiner”,
“url” : “https://raw.githubusercontent.com/cryptocoiner/bcex_data_feed2/master/crypto_coiner_bcex_data_feed.json”,
“url” : “https://raw.githubusercontent.com/cryptocoiner/bcex_data_feed2/master/crypto_coiner_bcex_data_feed.json.signature”,
“url” : “8GDKT2yJ4XfQzPyixtcBSWaoUAnpgwNFrP”,
“blocks” : 59,
“percentage” : 3.70835952
},
{
“provider” : “cryptog”,
“url” : “https://raw.githubusercontent.com/cryptog/bcexchange_data_feed/master/cryptog_bcexchange_data_feed.json”,
“url” : “https://raw.githubusercontent.com/cryptog/bcexchange_data_feed/master/cryptog_bcexchange_data_feed.json.signature”,
“url” : “8Pii9Ectrm3hGPiu1wr7nMqxabUeSpdrqY”,
“blocks” : 467,
“percentage” : 29.35260842
},
{
“provider” : “cybnate”,
“url” : “https://raw.githubusercontent.com/Cybnate/BKS-datafeed/master/Cybnate-main.json”,
“url” : “https://raw.githubusercontent.com/Cybnate/BKS-datafeed/master/Cybnate-sig.txt”,
“url” : “8U4ptdMup2MQ1uwVNNYqYv4btzmFyAuDju”,
“blocks” : 455,
“percentage” : 28.59836581
},
{
“provider” : “masterofDisaster”,
“url” : “https://raw.githubusercontent.com/Lamz0rNewb/BCExchange-datafeed/master/masterOfDisaster.json”,
“url” : “https://raw.githubusercontent.com/Lamz0rNewb/BCExchange-datafeed/master/masterOfDisaster.json.txt”,
“url” : “8LKJw8fnrtvgX1BegUeU5inwbQ6dvjMDoU”,
“blocks” : 610,
“percentage” : 38.34066625
}
]
}
sorry @Nagalim, when i did that, I don’t know your data feed, later i can add it .

[Eleven]

the percentage is one in the four providers. the total blocks is the amount after April 25, 00:00:00.