I recommend every delegate to set bter_trust_level to 0.0 in the config file

Quote from: xeroc on January 06, 2015, 07:13:59 PM

Quote from: emski on January 06, 2015, 02:13:51 PM
I've pushed an update fixing Poloniex's asset name change.

same here ... i should open up my own thread for updates :) and not misuse yours 8)

Given the fact both scripts are mostly identical it is not a big deal (:

Quote from: emski on January 06, 2015, 02:13:51 PM
I've pushed an update fixing Poloniex's asset name change.

same here ... i should open up my own thread for updates :) and not misuse yours 8)

I've pushed an update fixing Poloniex's asset name change.

Added to my slate. Thanks!

https://bitsharestalk.org/index.php?topic=9857.0

Quote from: emski on December 13, 2014, 09:03:49 AM

Quote from: clayop on December 13, 2014, 02:27:33 AM
Can you add KRW to your script? There is a growing interest in BitKRW and I want to introduce Korean community how to use it. (Plus encouraging Korean exchanges to add BitKRW)

Done!

I didn't realise how much feed it already got. Also I see a lot of new markets were enabled recently. I'm updating my feeds so that I publish feed for each active market (and KRW as it currently has 49 feeds).

Thanks Emski!!! (are you running delegate? if so please let me know your delegate)

Quote from: clayop on December 13, 2014, 02:27:33 AM
Can you add KRW to your script? There is a growing interest in BitKRW and I want to introduce Korean community how to use it. (Plus encouraging Korean exchanges to add BitKRW)

Done!

I didn't realise how much feed it already got. Also I see a lot of new markets were enabled recently. I'm updating my feeds so that I publish feed for each active market (and KRW as it currently has 49 feeds).

Can you add KRW to your script? There is a growing interest in BitKRW and I want to introduce Korean community how to use it. (Plus encouraging Korean exchanges to add BitKRW)

I've tested the script on v0.4.26 and it is working as designed.

Quote from: toast on December 12, 2014, 04:58:51 PM
I was talking about how it was updating every single block. You're just wasting your own money if most delegates do it much less often.

It updates according to configuration. I intentionally configured it like that. If the price changes more than specified threshold it updates the feed no matter what. You can always specify different thresholds.

EDIT: Furthermore the script runs at more than 3 minutes intervals. It cannot update the feed in less than 3 minutes (at least on my side). What you observed in that transaction spam wasn't produced by single delegate. A lot of these messages were delegate version updates and public data fields.

I believe the script is performing as designed. If you dont like it we can discuss that.

I was talking about how it was updating every single block. You're just wasting your own money if most delegates do it much less often.

Quote from: emski on December 12, 2014, 04:04:15 PM
I'll stop it for some brief investigation.

I think it's simply due to all the missed blocks and the general state of the network, transactions end up as pending so to the script it appears as if there hasn't been any recent updates.

I'll stop it for some brief investigation.

Quote from: toast on December 12, 2014, 03:52:30 PM
Is this script spamming feed updates right now?

http://bitsharesblocks.com/blocks/block?id=1248105

On my end it is publishing feed due to market changes.

2 consequtive runs:

New Feed differs for EUR : Old:0.0144859928 ; New:0.0138386806 ; Diff:0.0006473123 ; Max allowed Diff:-0.0000289720 +0.0001448599 ; Force updating!
New Feed differs for BTC : Old:0.0000512105 ; New:0.0000490656 ; Diff:0.0000021449 ; Max allowed Diff:-0.0000001024 +0.0000005121 ; Force updating!
New Feed differs for GOLD : Old:0.0000147824 ; New:0.0000140996 ; Diff:0.0000006828 ; Max allowed Diff:-0.0000000296 +0.0000001478 ; Force updating!
New Feed differs for USD : Old:0.0180345335 ; New:0.0172444977 ; Diff:0.0007900359 ; Max allowed Diff:-0.0000360691 +0.0001803453 ; Force updating!
New Feed differs for CNY : Old:0.1116319582 ; New:0.1066865365 ; Diff:0.0049454217 ; Max allowed Diff:-0.0002232639 +0.0011163196 ; Force updating!


Loading data: рyahoo, BTC38, BTer, Poloniex, bittrex -- done. Calculating btsx feeds prices and checking publish rules.
============================================================================================================================================================================================================================
EUR|new: 0.0138385BTSX (e:0.0124887/0.0138792) (bc:0.0143143)  |  change: -0.0006%  |  change (to med.): -0.0476%  |  exchange (median): +0.2938%  |  exchange (range): -30.4115% to +0.8562%  |  last update: 0:00:45.946552 ago
BTC|new: 0.0000491BTSX (e:0.0000463/0.0000493) (bc:0.0000502)  |  change: +0.0000%  |  change (to med.): -0.0001%  |  exchange (median): +0.5070%  |  exchange (range): -30.5407% to +1.0706%  |  last update: 0:00:45.946819 ago
GOLD|new: 0.0000141BTSX (e:0.0000127/0.0000141) (bc:0.0000146)  |  change: -0.0000%  |  change (to med.): -0.0000%  |  exchange (median): +0.2939%  |  exchange (range): -31.9129% to +0.8563%  |  last update: 0:00:45.947105 ago
USD|new: 0.0172445BTSX (e:0.0155624/0.0172952) (bc:0.0178263)  |  change: -0.0005%  |  change (to med.): -0.0582%  |  exchange (median): +0.2938%  |  exchange (range): -30.4126% to +0.8562%  |  last update: 0:00:45.947383 ago
CNY|new: 0.1066865BTSX (e:0.0962801/0.1070000) (bc:0.1102914)  |  change: -0.0029%  |  change (to med.): -0.3605%  |  exchange (median): +0.2938%  |  exchange (range): -30.4126% to +0.8562%  |  last update: 0:00:45.947652 ago
no update required