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

Mock Signature Verificaiton #2251

Merged
merged 2 commits into from
Jan 17, 2025
Merged

Conversation

badgersrus
Copy link
Contributor

Why this change is needed

https://github.com/ten-protocol/ten-internal/issues/4437

What changes were made as part of this PR

  • new mock signature verification and check for in memory DB to set it

PR checks pre-merging

Please indicate below by ticking the checkbox that you have read and performed the required
PR checks

  • PR checks reviewed and performed

@@ -600,3 +601,10 @@ func exportCrossChainData(ctx context.Context, storage storage.Storage, fromSeqN
} // todo: check fromSeqNo
return bundle, nil
}

func getSignatureValidator(useInMemDB bool, storage storage.Storage) (components.SequencerSignatureVerifier, error) {
if useInMemDB {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hopefully we have some checks in place that would barf for this but if we're in proper, SGX, attesting mode we definitely shouldn't be able to set that flag to true. In prod we'll lock it down with the enclave.json

Copy link
Collaborator

@BedrockSquirrel BedrockSquirrel left a comment

Choose a reason for hiding this comment

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

LGTM

@badgersrus badgersrus merged commit 976559e into main Jan 17, 2025
2 checks passed
@badgersrus badgersrus deleted the will/mock-signature-verification branch January 17, 2025 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants