pull down to refresh

When I combine my times with the ones posted here by BitMEXResearch, we get:

First SeenHeightMinerWinning/Losing
15:49:54941881AntPoollosing
15:51:47.084941882ViaBTClosing
15:50:08941881Foundrywinning
15:55:01.310941882Foundrywinning
15:55:03941883Foundry

And in case anyone is wondering about my timestamps, I am using NTP and my time is accurate within a few milliseconds.

I just took my node down this morning to apply some outstanding patches so I was poor on high quality inbound (still am) and I saw Foundry's 941881 first at 15:55:09, in a batch, all three of them at once. 5 minutes to see a header is a long time... ugh.

wondering about my timestamps

Was wondering more how you like knots? Do you get a lot of Timeout downloading block like that?

reply

I see you noticed the warning='Miner violated version bit protocol'.
I quite like the configurability of Knots.
The timeouts are actually very rare. This was my second one in March. In February I had only one.

reply
noticed

Yeah... that's very specific. I don't think anyone else hates BIP320 so much as to put the word violated in literally every UpdateTip message.

I quite like the configurability of Knots.

Yes. This is the big plus.

The timeouts are actually very rare.

Good. In this case there were 3 blocks worth to fetch, replacing blocks without too much fluff in it with a bunch that have max inscriptions, so I guess that can cause some trouble, which was why I was wondering whether that was special.

reply