Jake Pospischil

Optional gRPC Metadata params for NestJS service client methods

2

The `addGrpcMetadata` flag for NestJS mode is a really nice feature, but it seems like the behaviour should be different wrt the generated `Controller` vs `Client` interfaces. i.e. imo it...

outputPartialMethods (or equivalent) not available in nestJS mode

1

Hi, I am working on a NestJS gRPC microservice application and am currently using this package to generate TypeScript bindings for my service controllers and clients. So far I have...

Add endpoint for current slot and/or epoch

3

There is currently no way to query the current slot or epoch - only the previous justified, current justified, and finalized epoch. It's possible to calculate this manually after querying...

Trustless validator pools during phases 0 & 1

4

After the phase 2 rollout, validator deposits can be made with withdrawal credentials representing the address of a smart contract on a shard. However, during phases 0 & 1, the...

The eth2 provider URL in `config.yml` does not specify a protocol, since the clients use different protos to communicate (e.g. http for lighthouse, gRPC for Prysm). The Lighthouse, Nimbus and...

Currently, the process for using an external eth1 client with RP involves configuring RP and selecting "Geth", which is confusing when there is a "custom" option present. Process and/or docs...