Support SEP-53 wallet signatures in dashboard auth#42
Merged
Conversation
Verify now accepts both SEP-53 format (hex-encoded signature over
SHA256("Stellar Signed Message:\n" + nonce)) and raw format (base64
over nonce bytes). Tries SEP-53 first, falls back to raw for
backwards compatibility with E2E tests.
This enables Stellar wallet login via signMessage (Freighter, LOBSTR,
xBull, etc.) without requiring operators to enter their secret key.
Tests verify both hex-encoded SEP-53 signatures (valid + wrong key) alongside existing raw base64 signature tests.
73d0a55 to
c36afdf
Compare
This file contains hidden or 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
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.
Summary
SHA256("Stellar Signed Message:\n" + nonce)Context
Enables Stellar wallet login via
signMessage(Freighter, LOBSTR, xBull, WalletConnect) in the provider-console, replacing the secret key input.Test plan