No documented/enforced request body size limit for IPFS pin content uploads

[meshackyaro]

Description

PinContentDto.content (src/ipfs-pinning/ipfs-pinning.dto.ts) is validated with @IsBase64() and @IsNotEmpty() but has no @MaxLength() or any other size cap, and IpfsPinningService.pinContent() (src/ipfs-pinning/ipfs-pinning.service.ts) does Buffer.from(dto.content, 'base64') on whatever is supplied with no explicit size check before attempting to hash and pin it. main.ts (src/main.ts) never configures an explicit body-size limit either, so the effective cap today is whatever Express's/body-parser's implicit default happens to be — undocumented and easy to hit unexpectedly for legitimate larger deliverables, while also not being a deliberate, reviewed DoS control.

Component

Backend

Difficulty

🟢 Easy

Tasks

• Decide and explicitly configure a maximum request body size in main.ts (e.g. via app.use(json({ limit: '...' }))) appropriate for expected deliverable sizes
• Add a corresponding size cap check in PinContentDto/IpfsPinningService.pinContent() with a clear 400 error rather than relying solely on the framework-level body limit
• Document the maximum deliverable size in the Swagger description for POST /ipfs/pins
• Add a test confirming an oversized payload is rejected with a clear error

Acceptance Criteria

• There is an explicit, documented, and tested maximum size for IPFS pin content uploads
• Exceeding it returns a clear 4xx error rather than an opaque framework-level failure

Estimated Time

3-5 hours

[BikerProDeveloper]

I have experience with API limits and file uploads and have reviewed the code. I can submit a PR within 48 hours.

[Nathanpvd]

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

I’ve looked through the issue requirements and feel prepared to implement a solution that aligns with the proposed design and acceptance criteria.

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

[muokwejosh-cloud]

@muokwejosh-cloud has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’ve reviewed the issue details and documentation, and I understand the problem statement and expected outcome. Please assign this task to me — I’m ready to start working on it.

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

[Suzan-max]

@Suzan-max has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

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

[paulddeveloper-droid]

@paulddeveloper-droid has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on this issue. I’ve reviewed the requirements and understand the expected changes. I’ll follow the existing project patterns, add the required tests, and keep the implementation within the stated scope. I’m ready to start.

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

[biqqest]

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

I can deliver quality work and would appreciate the opportunity to contribute to this issue please

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

[CollinsKRO]

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

Hi, I can fix this kindly assign.

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

[drips-wave]

Congratulations, @Suzan-max! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Suzan-max: 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 🌊