-
Notifications
You must be signed in to change notification settings - Fork 842
Implement ACP-118 Aggregator #3394
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
Conversation
2e59a5d to
e7648e5
Compare
368ad1a to
2a47036
Compare
19d8f83 to
3af3bc9
Compare
6e6e88f to
cf4ecba
Compare
b4d7b35 to
60761f8
Compare
Signed-off-by: Joshua Kim <20001595+joshua-kim@users.noreply.github.com>
Signed-off-by: Joshua Kim <20001595+joshua-kim@users.noreply.github.com>
Signed-off-by: Joshua Kim <20001595+joshua-kim@users.noreply.github.com>
Signed-off-by: Joshua Kim <20001595+joshua-kim@users.noreply.github.com>
cam-schultz
left a comment
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.
LGTM. This seems like it would really simplify the p2p integration in signature-aggregator. by leveraging the existing p2p.Client. We re-implement a lot of the response handling and routing logic.
Signed-off-by: Joshua Kim <20001595+joshua-kim@users.noreply.github.com>
|
This PR has become stale because it has been open for 30 days with no activity. Adding the |
Signed-off-by: Joshua Kim <20001595+joshua-kim@users.noreply.github.com> Co-authored-by: Stephen Buttolph <stephen@avalabs.org> Co-authored-by: aaronbuchwald <aaron.buchwald56@gmail.com>
Why this should be merged
Implements
p2pclient + server logic for signature request handling as described inacp-118(ref).How this works
Client:
How this was tested