opened
y0sher
username_0
# Overview / Motivation

We have seen a case (quite a rare one), where a node started in a time where it fails to recognize the first tick and, starts counting in an off-by-one offset. ex: other miners send around layer 1 blocks and the affected miner get layer 1 tick on layer 2.

# The Task

Check the timer code to make sure we don't miss ticks and calculate right whenever we start.

# Implementation Notes
`timesync`

# Contribution Guidelines
Important: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who haven't introduced themselves on our Gitter [dev channel](https://gitter.im/spacemesh-os/Lobby)

1. Introduce yourself on go-spacemesh [dev chat channel](https://gitter.im/spacemesh-os/Lobby) - ask our team any question you may have about this task
2. Fork branch `develop` to your own repo and work in your repo
3. You must document all methods, enums and types with [godoc comments](https://blog.golang.org/godoc-documenting-go-code)
4. You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature
5. When ready for code review, submit a PR from your repo back to branch `develop`
6. Attach relevant issue to PR
Miner misses first tick when starting and continues with 1 offset
issue
closed
antonlerner
username_1
issue