Why are pool clocks not on same time.
-
Block 344824
-
Why cant we all get on the same sheet of music? Lex and my pool are on different continents why are they very close on the same time?
This network is bottle necking somewhere and it isnt in Europe.
What are we going to do?
-
Ok this is also about the same time. So it seems not all ninja pools can tell time lol
-
I got the answer why dont we put all the servers on a vps and spread them around? Vps are cheaper in the US so why not. My vps provider also has DDOS protection and I am sure others do too.
There is no good reason why my wallet cant propagate across the US in a timely manner unless the network bogs down somewhere.
So tell me why biz didnt see our 4 min dl?
-
Seams the displayed time is implemented in different ways ... i guess ninja pool type is just a javascript timer, independent of client system clock, while uray pools maybe use system time to calculate elapsed round time. The diff to uray pool time is sometimes smaller, sometimes bigger. maybe also the time they received the new block info has influence ... however, that has no influence on wallets, it is just a display issue i guess.
About that block '344819', your deadline also never reached my wallets, i researched on observer, and only 3 out of 26 nodes seam to have notices that deadline (the data is highly inaccurate, only what the observer has seen) ... that indicates that it was not caused by the one who found a other block later, but there was a problem propagating the block/deadline ... it would have been interesting, to how much nodes your pool wallet was connected at the moment.
My guess:
Your 4 min deadline was committed very fast after new block 344819 started, not all other nodes may have noticed the new round at that time. So they may have ignored the propagated deadline at that time. Not sure how the wallet handles that exactly ...
I'm just testing a solo mining feature for jminer, to call 'submitNonce' 3-5 times if a promising deadline was found. Also call submitNonce on multiple wallets with different peers and all that timed after every other second. To ensure a good deadline really makes it to the network.
As i also had found best deadline multiple times, that did not win in the end. Maybe someone could include such a feature in uray pool code, too. As my results so far are promising ... never noticed such a case again until now.
-
no it wasnt fast the 4 min dl it came normally. No my clock is not client driven it is set by US and Canadian ntp servers. The question is why biz didnt see my dl.
0Tross pool Raffle BURST-ZUGP-QTVB-L657-75MFW
http://burstpool.ddns.net/ <<<< Is the place to mine!
Burst Bash held once a month!
https://anycoindirect.eu/en/buy/bitcoins?discref=0eb3cf47-d5ee-45de-a243-e1dde0ba0aa9 (payPal)
one_reply_to_this_post
-
Luxe which nodes did see my dl?
-
@tross said in Why are pool clocks not on same time.:
The question is why biz didnt see my dl.
I tied to explain that (my guess) ... not only biz, but a lot of other nodes did not see it.
@tross said in Why are pool clocks not on same time.:
Luxe which nodes did see my dl?
I could just see the numbers, 3 out of 26 ... sadly the node transition history disappears after 10 rounds on bottom of http://util.burst-team.us:8888/ I should add a longer history and add node urls to tooltip ... so we can research better in the future.
-
@luxe but who did?
-
https://www.cryptocompare.com/coins/guides/what-is-a-bitcoin-fork/
sorry mate, you lost fair and square.
-
@msgAnton There where several minutes in between, he found ~4min deadline, and a ~13min. deadline won.
-
@msgAnton no way our dl was 8 min before biz dl. problem is not all wallets get all the info.
-
@luxe I will look over my trusted peers but do know biz is on the list.
-
On further analysis. I think i am wrong about the fork. Seems like the other pools don't like your pool (All pun intended) by not accepting your block.
-
Nope, I suspect I was correct. 344818 was won by TCIG LLC, your pool says its won by Big_Rob. which means it was already on a fork before 344819. and when you tried to broadcast 344820, the rest of the world rejected it due to it being shorter then the longest chain. (data from my own local wallet.)
It seems to be alot more complicated then this because I don't have the records of the other pools.... I can't really check. only going off your screenshots here.
-
@msgAnton I wasnt forked.
-
@msgAnton I will try to make http://util.burst-team.us:8888 provide a deeper view in the block transition history, so we can research better in the future.
-
Sometimes it could be and isp or vps provider but not all the time.
0Tross pool Raffle BURST-ZUGP-QTVB-L657-75MFW
http://burstpool.ddns.net/ <<<< Is the place to mine!
Burst Bash held once a month!
https://anycoindirect.eu/en/buy/bitcoins?discref=0eb3cf47-d5ee-45de-a243-e1dde0ba0aa9 (payPal)
one_reply_to_this_post
-
@msgAnton Yes you are right, not only block time but also generationSignature needs to be compared.
-
@tross All my pools/wallets are ntp time synced. I believe that the displayed time on the Ninja pools is based off when the pool saw the start of a new block - so propagation delays with previous blocks getting to the pool wallets would account for the different times. Each of my pools goes off a separate wallet, and I've regularly seen several second differences between them.
As for a deadline not accepted, I've had it happen - for what ever reason the rest of the network rejects my DL, and will award the block to a miner with a longer DL. It's frustrating, but I don't have an explanation for it.
