-
Notifications
You must be signed in to change notification settings - Fork 165
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
FIP-0086: Specify power table scaling & comm tree #983
Conversation
I've left the PowerTable directly in the struct for convenience. It also means we can reduce scope and punt the commitment tree specifics into the future. I've also: 1. Redefined the Tipset as a list of CIDs. 2. Clarified that the power table is a bare CBOR list (no wrapping structure).
This patch specifies the power table scaling discussed in our standups, scaling power between zero and 0xFFFF. I've also been careful to specify the correct inequalities and rounding. Honestly, all this would be better specified as pseudo-Python.
@@ -270,17 +270,16 @@ type Payload struct { | |||
} | |||
|
|||
type ECTipset struct { | |||
Epoch int | |||
Epoch uint64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
drive by
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved from an editorial perspective. Needs technical review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of typos; looks good otherwise. Also fixed the title.
This patch specifies the power table scaling discussed in our standups, scaling power between zero and 0xFFFF. I've also been careful to specify the correct inequalities and rounding.
(honestly, all this would be better specified as pseudo-python)