Cache generated PDFs by content hash

[RUKAYAT-CODER]

Background

Identical PDFs are regenerated on every request. Cache output keyed by a hash of the input.

Files to modify (2-3)

src/services/pdf-generation.ts
src/services/certificate-service.ts

Acceptance Criteria

Implemented across the listed files

Unit/integration tests added or updated and passing

No regression; follows project coding standards

[babawo96]

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

I have reviewed this issue and I would like to work on it

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

[Gentle842]

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

Hello, this task matches my skills and I’m confident I can resolve it properly. Kindly consider assigning it to me.

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

[Moh-dakai]

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

Hi i would love to work on this

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

[AbdulSnk]

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

I would like to apply for this issue.

Proposed Approach:

Hashing & Caching (src/services/pdf-generation.ts): Compute a cryptographic content hash (e.g., SHA-256) of input data prior to document generation to key and retrieve cached PDF buffer outputs, avoiding redundant rendering operations.

Service Integration (src/services/certificate-service.ts): Update the certificate service to check the cache before triggering raw PDF generation dispatches, serving cached assets when inputs are identical.

Testing & Verification: Add unit and integration tests verifying cache hits on identical input payloads, cache misses on updated data, and proper cache expiration/invalidation mechanics without breaking existing PDF delivery pipelines.

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

[drips-wave]

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

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