Cal Bera
Cal Bera
+1 to Rez's comment. Some things we should try fixing: - currently broken -- if I try changing just 1 test to run on `mainnet` (and keep the others on...
waiting on https://github.com/berachain/contracts/pull/4
Thank you for submitting! Not something we can test fully right now!
no longer needed
@nidhi-singh02 @itsdevbear It may be worth to just introduce e2e tests (& the minimally necessary type fixes) on 1 PR. And isolating all other refactoring/structural changes to node-api to another...
@nidhi-singh02 as discussed in DMs, lets shrink the diff removing anything not absolutely necessary for the test framework and address the remaining comments.
Marking status as "In Review". Implementation is complete. Testing in various conditions is in progress (@fridrik01)
> Consider opening a route on beacon api for validator index merkle witness generation as backend code is already there. > > https://github.com/berachain/beacon-kit/blob/main/node-api/handlers/proof/routes.go > > ``` > bkit/v1/proof/validator_index/:index > ```...
> https://github.com/berachain/beacon-kit/blob/main/consensus-types/types/state.go And yeah, as pointed out, the BeaconState schema does not match Eth2's fully identically, as a full equivalency is not needed for Berachain.
> We have made a working solution here: https://github.com/infrared-dao/bera-proofs > > To answer, we were after merkle proof for a validator leaf (i.e. merkle of validator fields) to either state...