gRPC implementation in server-node and router
See original GitHub issueIssue Description
About Connext
At Connext, our goal is to build the cross-chain routing and micropayment layer of the decentralized web. Vector sits on top of Ethereum, evm-compatible L2 blockchains, and other turing-complete chains, and enables instant, near free transfers that can be routed across chains and over liquidity in any asset.
Task
The overall goal of this task is to create a gRPC-based communication layer on top of Vector server-node
s. Currently, the server nodes have an HTTP REST interface for communication. This is okay for user-node actions, but in a high-throughput microservice architecture, we need something more performant and flexible.
The Vector router
is a microservice that is designed to run in a stack with a server node. The router currently interacts with the server node through HTTP requests. We would like to enable bidirectional communication between the server node and the router, which will be easily enabled through gRPC.
Requirements
- Create gRPC server in
server-node
that implements the API that is defined by the endpoints here: https://github.com/connext/vector/blob/main/modules/server-node/src/index.ts - Create a gRPC client in
router
that can communicate with theserver-node
. - Create gRPC server in
router
which can push events back to theserver-node
. - Make sure protobuf specs have corresponding Typescript types (even better if they are automatically generated!).
- Follow the code style of Vector repo.
Bounty
A total of $200 DAI is allocated to this bounty.
Links:
- More about connext & vector: https://github.com/connext/vector
- Chat at Discord: https://discord.com/channels/454734546869551114
Issue Analytics
- State:
- Created 2 years ago
- Comments:36 (15 by maintainers)
@gitcoinbot Update coming soon
@sanchaymittal I have submitted. I am okay with ETH .
Thanks … I would be hanging with you team on discord