Include chain-id in signature payload #457
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
When registering a data-proxy we now require the signed payload to include the chain-id for the intended network. This prevents replay attacks between different environments. Closes: #455
gluax
approved these changes
Jan 6, 2025
hacheigriega
approved these changes
Jan 7, 2025
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.
Motivation
When registering a data-proxy we now require the signed payload to include the chain-id for the intended network. This prevents replay attacks between different environments.
Explanation of Changes
Also updated the invalid signature error to more clearly specify it's the data proxy signature that's invalid, not the TX signature.
Testing
Updated the test vectors by running
bun run start register <ADDRESS> <AMOUNT> -n mainnetin the SEDA data proxy PR: sedaprotocol/seda-data-proxy#38Related PRs and Issues
Closes: #455