Add structured request/response logging with redaction

[Abdulazeem-code]

Description

Current logging uses ad-hoc logger.error() calls with inconsistent formats. Sensitive fields like signatures and API keys may be logged in plaintext.

Proposed Solution

Configure pino-http with a custom serializer that redacts signature, secret, x-api-key, and authorization fields. Log request method, path, status code, and duration for every request.

Acceptance Criteria

• pino-http configured with custom serializers
• Sensitive fields redacted in all log output
• Every request logged with method, path, status, duration
• Log format is machine-parseable JSON

Suggested Implementation Areas

server.js, src/logger.js

Impact

Enables production log analysis while preventing accidental exposure of secrets in log aggregators.

[Emmycivity]

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

Having carefully examined the details, I’m confident I can resolve the issue effectively while keeping the solution clean and efficient.

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

[Stephan-Thomas]

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

hi, i would like to work on this.

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

[Peolite1]

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

i would love to work on this issue

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

[ositaemmanuel653-netizen]

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

I am confident that I can implement this having worked on similar issues in the past

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

[uche102]

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

Hi maintainer please I would like to work on this

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

[drips-wave]

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

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