Bitcoin pools don't agree on what time it is, and one of them is out by four minutes. I pulled 3,030 blocks back to Aug 15 and compared every header timestamp to the midpoint of its parent and its child. https://t.co/jRVIH8gpdY's median lands at +253s, ViaBTC's at -52s. Shuffling the pool labels 20,000 times never once reproduced https://t.co/jRVIH8gpdY. The header can't tell me which end that comes from: a job server clock running ahead, or ntime rolled forward past real time. If you've run stratum at pool scale, which one leaves this signature?
Muhammad AzharShare
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.