-
Notifications
You must be signed in to change notification settings - Fork 37
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
Capella -> to Deneb update #18
Conversation
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.
lgtm
prove_validator.go
Outdated
@@ -15,7 +15,7 @@ type VerifyWithdrawalCredentialsCallParams struct { | |||
ValidatorFields [][]Bytes32 `json:"validatorFields"` | |||
} | |||
|
|||
func (epp *EigenPodProofs) ProveValidatorWithdrawalCredentials(oracleBlockHeader *phase0.BeaconBlockHeader, oracleBeaconState *capella.BeaconState, validatorIndices []uint64) (*VerifyWithdrawalCredentialsCallParams, error) { | |||
func (epp *EigenPodProofs) ProveValidatorWithdrawalCredentials(oracleBlockHeader *phase0.BeaconBlockHeader, oracleBeaconState *deneb.BeaconState, validatorIndices []uint64) (*VerifyWithdrawalCredentialsCallParams, error) { |
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.
No i mean everywhere. If its for deneb, name it deneb. if it's for fork1 name it fork1
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.
The other way (easier) is that you name them the same thing and just change argument types. let's not go halfway though
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.
hmm not sure about that, its a bit much. it makes more sense to me to have separate functions for where it matters. I don't mind having the same name and different types tho, although it might make it a little less explicit - tho I don't think go lang lets you delcare similarly named functions in the same package
@@ -39,7 +40,7 @@ func NewEigenPodProofs(chainID uint64, oracleStateCacheExpirySeconds int) (*Eige | |||
}, nil | |||
} | |||
|
|||
func (epp *EigenPodProofs) ComputeBeaconStateRoot(beaconState *capella.BeaconState) (phase0.Root, error) { | |||
func (epp *EigenPodProofs) ComputeBeaconStateRoot(beaconState *deneb.BeaconState) (phase0.Root, error) { |
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.
can we just define new functions on *deneb.BeaconState
? like
func (s *deneb.BeaconState) ComputeBeaconStateRoot() (phase0.Root, error) {
not sure if go allows it because its from another module
fullWithdrawalProof_Latest.json
Outdated
@@ -0,0 +1,162 @@ | |||
{ |
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.
pls move these out of the top level folder
Deneb cleanup
Upgrading proof gen from capella spec to deneb spec, with support for both capella and deneb spec proofs.
DO NOT MERGE