Consider simplifying the aggregation logic #388
Labels
enhancement
New feature or request
Warp Signature API
API service for serving arbitrary Warp signatures from any VM
Milestone
Context and scope
Current POC implementation of the signature aggregation was based on the existing logic in the relayer. We should consider simplifying and/or improving the logic while working through the other MVP issues. Particularly #382 as it will be modifying the code flow.
relayer/network_utils.go
based on feedback in Move relayer to subfolder #411Discussion and alternatives
Another existing implementation of the signature aggregation functionality that we can reference is in the subnet-evm repo.
Consider immediately unmarshalling signatures when received instead of in
aggregateSignatures
Open questions
The text was updated successfully, but these errors were encountered: