Skip to content

feat(api): WS ticket auth, Redis-backed matches, staked cancel, tournament API - #1540

Open
sketcherzee wants to merge 1 commit into
OpenKnight-Foundation:mainfrom
sketcherzee:fix/be-103-112-113-114-ws-ticket-matchmaking-redis-tournaments
Open

feat(api): WS ticket auth, Redis-backed matches, staked cancel, tournament API#1540
sketcherzee wants to merge 1 commit into
OpenKnight-Foundation:mainfrom
sketcherzee:fix/be-103-112-113-114-ws-ticket-matchmaking-redis-tournaments

Conversation

@sketcherzee

@sketcherzee sketcherzee commented Oct 22, 2026

Copy link
Copy Markdown

Closes #1380
Closes #1382
Closes #1383
Closes #1384

  • BE-103: single-use WS ticket from an authenticated REST call, accepted via query param / Sec-WebSocket-Protocol; frontend socket hooks updated
  • BE-112: request id -> queue key Redis hash so cancel removes staked requests; test added
  • BE-113: active matches stored in Redis with TTL
  • BE-114: GET/POST /v1/tournaments and POST /v1/tournaments/{id}/register backed by DB tables, 404/409 handling, tournament crate used for brackets

@drips-wave

drips-wave Bot commented Oct 22, 2026

Copy link
Copy Markdown

@sketcherzee Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment