Problem
RafflesService.purchaseTickets() returns synthetic confirmation data (line 164) while the blockchain submission and persistence logic is marked TODO (raffles.service.ts:163,175). Users receive a success response but no ticket is recorded — purchases are silently lost and the draw path has no real data to operate on.
Fix
Block the endpoint behind a feature flag until the blockchain integration is implemented and integration-tested end-to-end. Return a 501 in the interim rather than a false 200.
File: backend/src/api/rest/raffles/raffles.service.ts:149-179
Problem
RafflesService.purchaseTickets()returns synthetic confirmation data (line 164) while the blockchain submission and persistence logic is marked TODO (raffles.service.ts:163,175). Users receive a success response but no ticket is recorded — purchases are silently lost and the draw path has no real data to operate on.Fix
Block the endpoint behind a feature flag until the blockchain integration is implemented and integration-tested end-to-end. Return a 501 in the interim rather than a false 200.
File:
backend/src/api/rest/raffles/raffles.service.ts:149-179