[Backend] — Competition Bracket Generation

[Olowodarey]

Labels: backend, enhancement, competitions

Problem

Competitions have participants but no automated bracket/seeding, so organizers must arrange matchups manually.

Requirements

1. Add an endpoint to generate a bracket from a competition's participants.
2. Support single-elimination seeding based on a chosen metric.
3. Persist bracket rounds and matchups.
4. Handle byes for non-power-of-two participant counts.

Acceptance Criteria

• A valid bracket is generated for any participant count.
• Byes are assigned deterministically for odd counts.
• Bracket structure is persisted and retrievable.
• Tests cover power-of-two and bye cases.

Files

backend/src/competitions/competitions.service.ts, backend/src/competitions/competitions.controller.ts, backend/src/competitions/entities, backend/src/competitions/dto

[senmalong]

@senmalong has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hi,

This issue aligns well with my experience as a Web3 builder. I’ve worked on Celo-based applications with a focus on usability, smart contracts, stablecoin payments, and real-world adoption.

I also have contribution experience through OnlyDust, Drips Waves 1–5, and the GrantFox beta campaign. I’m confident I can deliver a clean and well-tested solution within 24 hours.

I’d be excited to contribute to this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @senmalong to this issue.

[dehonesty2-svg]

@dehonesty2-svg has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello! I'd like to work on this issue.

I have experience building backend features with a focus on designing RESTful APIs, implementing database-backed workflows, and writing maintainable, well-tested code. This issue aligns well with my experience, particularly around implementing business logic and data modeling.

For this task, I plan to:

• Implement an endpoint to generate competition brackets from registered participants.
• Support single-elimination seeding based on the selected metric.
• Persist bracket rounds and matchups in a clean, extensible schema.
• Correctly handle byes for non-power-of-two participant counts.
• Add tests to verify seeding, bracket generation, bye handling, and persistence to ensure the acceptance criteria are fully met.

I'll follow the project's existing architecture and coding standards, communicate progress throughout the implementation, and ensure the feature is well-tested before submitting a PR.

I'd appreciate the opportunity to contribute. Thank you!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dehonesty2-svg to this issue.

[Emmanuellsensai]

@Emmanuellsensai has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'll take this issue.

Plan:

1. Add a bracket generation endpoint to competitions.controller.ts that accepts a competition ID and seeding metric.
2. Implement bracket generation logic in competitions.service.ts to create single-elimination brackets with deterministic bye assignment for non-power-of-two participant counts.
3. Create bracket and matchup entities in the entities folder to persist the generated bracket structure.
4. Define DTOs in the dto folder for the bracket generation request and response payloads.
5. Add tests covering power-of-two participant counts and bye scenarios to verify bracket validity and persistence.

I'll wait for assignment before opening a PR

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emmanuellsensai to this issue.

[nayt9]

@nayt9 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello sir , my name is Nathan. I’m smart contract developer, and I’d love to contribute to this project. I’m comfortable working with modern frontend tools and blockchain technologies, and I can deliver tasks quickly often within 24 hours.
Please let me know how I can get started or if there are any issues suitable for a first contribution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nayt9 to this issue.

[AJ0070]

@AJ0070 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Could you please assign this to me? I would like to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AJ0070 to this issue.

[bright5455]

@bright5455 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello Maintainers,

I’d like to be assigned to this issue.

I have experience building backend APIs with NestJS, PostgreSQL, and Prisma, and I’ve implemented features involving complex business logic, validation, and relational data modelling. This issue is particularly interesting because it combines algorithmic logic with a clean backend design. I’d like to contribute a solution that is deterministic, scalable, and easy to maintain.

My implementation approach

1. Review the existing competition and participant models to understand the current data relationships and project architecture.
2. Create a dedicated endpoint that generates a tournament bracket for a selected competition after validating that the competition exists and has eligible participants.
3. Implement a single-elimination seeding algorithm that orders participants using the configured seeding metric while ensuring deterministic results.
4. Calculate the nearest power-of-two bracket size and assign byes consistently so that the same participant order always produces the same bracket.
5. Persist the generated bracket by creating bracket, round, and matchup records with the appropriate relationships in the database.
6. Prevent duplicate bracket generation unless regeneration is explicitly supported by the project’s requirements.
7. Add comprehensive tests covering power-of-two and non-power-of-two participant counts, deterministic seeding, bye assignment, and invalid input scenarios.
8. Verify the generated bracket structure against the acceptance criteria and ensure the implementation follows the project’s coding standards before submitting the PR.

My goal is to deliver a clean, well-tested implementation that produces predictable tournament brackets, handles edge cases correctly, and provides a solid foundation for future competition features.

I’d appreciate the opportunity to work on this issue and contribute a production-ready solution. Thank you for your consideration.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bright5455 to this issue.

[Danitello123]

@Danitello123 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Good day maintainer
Please kindly assign me this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Danitello123 to this issue.

[devsimze]

@devsimze has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi I'd like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @devsimze to this issue.

[drips-wave]

Congratulations, @devsimze! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @devsimze: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊