Feature: gRPC server and client #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Depends on #3. |
odesenfans
force-pushed
the
od/grpc-server
branch
2 times, most recently
from
cae7bc5 to
969bb29
Compare
Implemented a gRPC server to call the Stone prover from a remote client. This server provides a single endpoint at the moment, `Prove`, which returns the proof. The protocol uses server-side streaming to communicate the proof to the client once it is computed. This server is still limited, the following points need to be discussed: * Efficiency: the protocol passes JSON data (public input, prover config and parameters) as raw strings. These strings are then deserialized on server-side to validate them, but end up being serialized again for use by the prover process. This is clearly inefficient. * Even if the client process cancels the request, the prover will keep on running until the proof is generated.
odesenfans
force-pushed
the
od/grpc-server
branch
from
969bb29 to
e435346
Compare
This was
linked to
issues
Nov 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implemented a gRPC server to call the Stone prover from a remote client.
This server provides a single endpoint at the moment,
Prove, whichreturns the proof. The protocol uses server-side streaming to
communicate the proof to the client once it is computed.
This server is still limited, the following points need to be discussed:
Efficiency: the protocol passes JSON data (public input, prover config
and parameters) as raw strings. These strings are then deserialized on
server-side to validate them, but end up being serialized again for
use by the prover process. This is clearly inefficient.
Even if the client process cancels the request, the prover will keep
on running until the proof is generated.