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.

Here is the output for 2 consecutive script 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 .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

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 .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

Quote from: emski on December 12, 2014, 02:27:36 pm

Quote from: Riverhead on December 12, 2014, 02:24:43 pm

riverhead-del-server-1 and backbone.riverhead are on the main chain I think now. 77.7% particiption

What about bm.payroll.riverhead ?
Isn't that somewhat important ?

That is in progress (just waiting on sync). It's on a VPS far far away so things are a bit slower. I had already mostly upgraded teh other two last night but fell asleep at the keys around 2am.

Also, missed blocks for bm.payroll.riverhead comes out of my pocket not his . BM will not suffer any wage loss due to this issue.

That is strange...
Are the deal parameters public (the deal between you and BM for the delegate) ?

Quote from: emski on December 12, 2014, 01:59:05 pm

One issue I see is yPool requires more than 100 confirmations before you can withdraw your funds.
All the PTS BM paid for returning the donated PTS are in their possession ATM and I doubt they will be released until the snapshot.

Oh, the high transaction fees. That's not great... do you know offhand how many blocks it's been since BM returned the funds?

Sent from my SCH-S720C using Tapatalk 2

less than 60

EDIT: Actually 50 confirmations are needed for the last block of these transactions.

Actually I've updated the script to work with 0.4.25.
You can safely update now.

We have seen 0.4.24 and 0.4.25 forked before the predefined block.
Am I correct that this could be identified before release with (simple) testing ?
What procedures were followed prior 0.4.25 release ?

Main questions:
Why we have forking 0.4.24 and 0.4.25 before block 1249400 ?
Wasn't this relatively easy to prevent ?

0.4.25 and 0.4.24 clients report different missed blocks.
And it seems the blockchain is different for my 2 instances.
I'll investigate further.

Yes. Even that the updgrade should've been scheduled for the future the upgrade caused forks between 0.4.24 and 0.4.25.
When I've upgraded I got on a different chain.