Skip to content
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

"Tie breaker rule": implement a method to decide between chains with the same weight #2981

Closed
irenegia opened this issue Aug 11, 2020 · 4 comments
Assignees
Labels
area/chain Area: Chain impact/consensus Impact: Consensus P1 P1: Must be resolved
Milestone

Comments

@irenegia
Copy link

irenegia commented Aug 11, 2020

Background
Two (or more) forks may have the same exact weight and in this case we need a rule to decide which one to extend.

Proposal
Implement the following rule already described in the spec link:

When selecting between Tipsets of equal weight, a miner chooses the one with the smallest final ticket.

In the case where two Tipsets of equal weight have the same min ticket, the miner will compare the next smallest ticket (and select the Tipset with the next smaller ticket). This continues until one Tipset is selected.

Note: we should use the ticket used as election proof (VRF(drand)) for this (updated spec).

CC @sa8 @Kubuxu

@daviddias daviddias added the P1 P1: Must be resolved label Aug 26, 2020
@nicola
Copy link

nicola commented Oct 27, 2020

I propose that @sa8 writes this as an FIP in the FIP repo (https://github.com/filecoin-project/fips)

@sa8
Copy link

sa8 commented Oct 27, 2020

@jennijuju jennijuju added area/chain Area: Chain and removed area/chain/misc labels Feb 11, 2021
@nicola
Copy link

nicola commented Feb 11, 2021

This was written up here: filecoin-project/FIPs#22

@jennijuju
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/chain Area: Chain impact/consensus Impact: Consensus P1 P1: Must be resolved
Projects
None yet
Development

No branches or pull requests

7 participants