Skip to content

Conversation

@sternhenri
Copy link
Contributor

@sternhenri sternhenri commented Aug 22, 2019

Three big changes:

  • Diagrams added
  • Precision of what to do if multiple blocks in a TipSet have losing tickets
  • spec'd ticket comparison steps.

### Selecting between TipSets with equal weight

When selecting between TipSets of equal weight, a miner chooses the one with the smallest min ticket (by bytewise comparison).
When selecting between TipSets of equal weight, a miner chooses the one with the smallest min ticket.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My reading of the above discussion is that tickets are comparable against tickets but I don't know how to compare ticket arrays with each other. Comparing ticket arrays is the thing we really want for 1) tie breaking, 2) consistent message application order. It is the thing we should include in the spec.

Right now I'm imagining we just take the first ticket of the array and compare.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reading above I'm actually guessing its the final ticket, not the first. But let's make sure to make that clear.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood. Yes! Thanks

Copy link
Contributor

@dignifiedquire dignifiedquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

@sternhenri
Copy link
Contributor Author

outdated

@sternhenri sternhenri closed this Nov 5, 2019
@sternhenri sternhenri deleted the patch/ticket-in-nulls branch November 29, 2019 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants