-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Head input chain offset #175
Comments
In pair with decision on #173 to wait for 2 epochs from the timestamp on the latest finalized epoch, the participant sets as proposal for the new f3 instance the following:
Then:
|
I think this is done: it is specified in the FIP so the decision is make. @Kubuxu do you need this issue open to track some implentation task? |
We don't have the head offset currently. Looking at the FIP pseudocode, it appears "delete the head always", as I'm assuming |
It's difficult to be precise with language here. I had interpreted the FIP's use of What exactly do you mean by the epoch of the chain head? Is it the epoch of the blocks currently being proposed? Or the epoch of the tipset to which the most recent possible block points? |
What you wrote makes sense.
I meant EC Chain head. |
Resolves #175 Signed-off-by: Jakub Sztandera <oss@kubuxu.com>
Resolves #175 Signed-off-by: Jakub Sztandera <oss@kubuxu.com>
When a participant starts an f3 instance, it needs to determine whether it wants its proposal to contain from baseChain up to the head input chain it locally keeps in EC, or some prefix of it (i.e. offset it by some epochs). Although this may delay latency on the head tipset, it helps reduce latency and reach agreement faster on the EC instance. This is closely related with #173.
The text was updated successfully, but these errors were encountered: