Skip to content
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

Signature Aggregator ACP-118 updates #422

Merged
merged 12 commits into from
Aug 21, 2024

Conversation

iansuvak
Copy link
Contributor

@iansuvak iansuvak commented Aug 9, 2024

This should pass the tests but not necessarily be merged into the PR until all of the required commits make it into default branches. Right now the main outstanding one would be the subnet-evm that references newer avalanchego commit that includes latest coreth changes.

The commits have been updated to reference default branches ones now.

Includes a bugfix on the validation logic.

I'm open to suggestions on cleaner prefix packing and to avoid copying into blsSignatureBuf if anyone has ideas.

iansuvak and others added 7 commits August 8, 2024 22:41
Co-authored-by: cam-schultz <78878559+cam-schultz@users.noreply.github.com>
Signed-off-by: Ian Suvak <ian.suvak@avalabs.org>
Co-authored-by: Geoff Stuart <geoff.vball@gmail.com>
Signed-off-by: Ian Suvak <ian.suvak@avalabs.org>
@iansuvak iansuvak changed the title Isuvak/sig agg acp 118 Signature Aggregator ACP-118 updates Aug 9, 2024
@iansuvak iansuvak requested a review from feuGeneA August 9, 2024 13:23
@@ -88,6 +88,9 @@ func (h *RelayerExternalHandler) HandleInbound(_ context.Context, inboundMessage
zap.Stringer("from", inboundMessage.NodeID()),
)
if inboundMessage.Op() == message.AppResponseOp || inboundMessage.Op() == message.AppErrorOp {
if inboundMessage.Op() == message.AppErrorOp {
h.log.Debug("Received AppError message", zap.Stringer("message", inboundMessage.Message()))
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is messy checking but I used this to see error codes received from validator nodes which we don't log anywhere right now

@meaghanfitzgerald meaghanfitzgerald added the Warp Signature API API service for serving arbitrary Warp signatures from any VM label Aug 9, 2024
Copy link
Contributor

@feuGeneA feuGeneA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Happy to see it working!

@iansuvak iansuvak mentioned this pull request Aug 19, 2024
@geoff-vball
Copy link
Contributor

geoff-vball commented Aug 19, 2024

I think you may have accidentally included an update to the teleporter submodule? The go.work.sum was added back

@iansuvak
Copy link
Contributor Author

I think you may have accidentally included an update to the teleporter submodule? The go.work.sum was added back

Thanks, I had teleporter updated to a branch commit that was not necessary so I downgraded it v1.0.4 which is what it is on main branch I believe https://github.com/ava-labs/awm-relayer/tree/main/tests/contracts/lib . I'm happy to bump to any version that we need but it wouldn't be related to this and the parent PR which shouldn't require changes to teleporter dependencies


return signature, true
blsSig := blsSignatureBuf{}
copy(blsSig[:], signature[:])
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have a check higher up that the length of signature is the expected length?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Possibly, we do call bls.SignatureFromBytes and bls.Verify on it's result so presumably those wouldn't work if it wasn't correct lenght but an explicit check wouldn't hurt

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in 811c97a

@iansuvak iansuvak merged commit 30a718d into signature-aggregation-api-acp-118 Aug 21, 2024
7 checks passed
@iansuvak iansuvak deleted the isuvak/sig-agg-acp-118 branch August 21, 2024 15:15
Copy link
Contributor

@bernard-avalabs bernard-avalabs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Warp Signature API API service for serving arbitrary Warp signatures from any VM
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

6 participants