An improper exceptional condition check in the `obtain tips()` function within `ChainSync` causes the system to discard valid one-hash FindBlocks responses. This leads to a false report of close-to-tip status. When peers return only the next block hash, it results in a zero-length sync sample, causing the '/ready' endpoint to return a 200 OK status even though the node is still behind the tip.