-
Notifications
You must be signed in to change notification settings - Fork 260
feat: add grpc socket and flattn tx batches to allow for lower allocations #3297
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,13 +1,13 @@ | ||||||
| # gRPC Single Sequencer App | ||||||
|
|
||||||
| This application runs a Evolve node with a single sequencer that connects to a remote execution client via gRPC. It allows you to use any execution layer that implements the Evolve execution gRPC interface. | ||||||
| This application runs a Evolve node with a single sequencer that connects to an execution client via gRPC. It allows you to use any execution layer that implements the Evolve execution gRPC interface. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix article in intro sentence. Use “an Evolve node” instead of “a Evolve node” for grammatical correctness. ✏️ Proposed doc fix-This application runs a Evolve node with a single sequencer that connects to an execution client via gRPC. It allows you to use any execution layer that implements the Evolve execution gRPC interface.
+This application runs an Evolve node with a single sequencer that connects to an execution client via gRPC. It allows you to use any execution layer that implements the Evolve execution gRPC interface.📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||
|
|
||||||
| ## Overview | ||||||
|
|
||||||
| The gRPC single sequencer app provides: | ||||||
|
|
||||||
| - A Evolve consensus node with single sequencer | ||||||
| - Connection to remote execution clients via gRPC | ||||||
| - Connection to execution clients via TCP or Unix domain socket gRPC | ||||||
| - Full data availability layer integration | ||||||
| - P2P networking capabilities | ||||||
|
|
||||||
|
|
@@ -58,11 +58,20 @@ Start the Evolve node with: | |||||
| --da.auth-token your-da-token | ||||||
| ``` | ||||||
|
|
||||||
| For a same-machine executor, use a Unix domain socket endpoint: | ||||||
|
|
||||||
| ```bash | ||||||
| ./evgrpc start \ | ||||||
| --root-dir ~/.evgrpc \ | ||||||
| --grpc-executor-url unix:///tmp/evolve-executor.sock \ | ||||||
| --da.address http://localhost:7980 | ||||||
| ``` | ||||||
|
|
||||||
| ## Command-Line Flags | ||||||
|
|
||||||
| ### gRPC-specific Flags | ||||||
|
|
||||||
| - `--grpc-executor-url`: URL of the gRPC execution service (default: `http://localhost:50051`) | ||||||
| - `--grpc-executor-url`: URL of the gRPC execution service, either `http://host:port` or `unix:///path/to/socket` (default: `http://localhost:50051`) | ||||||
|
|
||||||
| ### Common Evolve Flags | ||||||
|
|
||||||
|
|
||||||
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.
Missing PR name.