Skip to content

Support SEP-53 wallet signatures in dashboard auth#42

Merged
AquiGorka merged 2 commits intodevfrom
feat/86c8mw0jh-wallet-login
Mar 17, 2026
Merged

Support SEP-53 wallet signatures in dashboard auth#42
AquiGorka merged 2 commits intodevfrom
feat/86c8mw0jh-wallet-login

Conversation

@AquiGorka
Copy link

Summary

  • Dashboard auth verify now accepts both SEP-53 and raw signature formats
  • SEP-53: hex-encoded signature over SHA256("Stellar Signed Message:\n" + nonce)
  • Raw: base64 signature over nonce bytes (backwards compatible with E2E)
  • Tries SEP-53 first, falls back to raw
  • 2 new tests for SEP-53 format (valid + wrong key rejection)

Context

Enables Stellar wallet login via signMessage (Freighter, LOBSTR, xBull, WalletConnect) in the provider-console, replacing the secret key input.

Test plan

  • 11 dashboard auth tests pass (9 existing + 2 new SEP-53)
  • Manual: login via Freighter signMessage against provider

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.
@AquiGorka AquiGorka force-pushed the feat/86c8mw0jh-wallet-login branch from 73d0a55 to c36afdf Compare March 17, 2026 18:15
@AquiGorka AquiGorka merged commit 16067ce into dev Mar 17, 2026
2 checks passed
@AquiGorka AquiGorka deleted the feat/86c8mw0jh-wallet-login branch March 17, 2026 18:33
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.

1 participant