ethereum-consensus
ethereum-consensus copied to clipboard
ralexstokes
one thing I have noticed while using the `Client` type is that failures are annoying to diagnose the API is strongly-typed and so if URL endpoints and message types are...
we should have a build step like this in the CI to ensure that things also build w/o default features https://github.com/ralexstokes/ssz-rs/blob/main/.github/workflows/ci.yml#L37 and it looks like `beacon-api-client` currently does not succeed!
take a keystore and make a "deposit_data.json" file like the [staking-cli](https://github.com/ethereum/staking-deposit-cli)
https://docs.rs/alloy-primitives/latest/alloy_primitives/struct.Bytes.html in order to unify behavior across types, encourage uniformity across the Rust/Ethereum ecosystem and reduce the amount of code we maintain, we should try to use the `Bytes` type...
mainly boils down to [`Context::try_from_file`](https://github.com/ralexstokes/ethereum-consensus/blob/bc7c35ebfbe7b218ab738ec24f7eb08f7bfbd12e/ethereum-consensus/src/state_transition/context.rs#L117)
There is a PR that tried to fix this, but it was not merged yet and I don't know if it is still current: #191 On the current main branch...
add something like this: https://docs.rs/zeroize/latest/zeroize/ and it is worth exploring any other approaches here so that using this library is safe for any users
Implement `alloc` crate Implement `hashbrown` crate Made use of [milagro](https://github.com/sigp/milagro_bls) crate for the BLS scheme. closes #166
