fix: relayer logging standards

[N-thnI]

Description
Unified JSON logging.

Problem Statement
Hard to parse/audit.

Technical Requirements

• Structured log fmt.

Implementation Guide

• Suggested Approach: Use winston/pino.
• Affected Areas: src/

Acceptance Criteria

• Logs searchable.

Security & Audit Considerations

• None.

Definition of Done

• Audit friendly.

[Chigybillionz]

Hi, I'd like to work on this issue.

I'm a full-stack developer with experience setting up structured logging in Node.js/TypeScript backends. My plan:

• Introduce pino (or winston if the project already has a preference) as the single logging dependency across src/
• Create a shared logger instance with consistent fields on every log line: timestamp, level, service name, request/correlation ID where available
• Replace all existing console.log, console.error, and ad-hoc logging calls in src/ with the structured logger
• Ensure sensitive fields (tokens, passwords, keys) are redacted before they reach the log output
• Verify the output is valid JSON so it can be ingested directly by log aggregators like Datadog, CloudWatch, or Loki without a custom parser

Can I be assigned?

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.

[Ahmedscreativeverse]

I can implement a unified structured logging system across the entire src/ codebase, making logs consistent, searchable, and audit-friendly.

My approach is to standardize all application logging using a structured JSON format with a proven logging framework such as Winston or Pino. This will replace inconsistent log outputs with machine-readable logs that are easy to filter, aggregate, monitor, and analyze across environments.

Key deliverables:

• Implement a centralized logging layer using Winston or Pino.
• Standardize log formats across all modules.
• Output structured JSON logs with consistent schemas.
• Include useful metadata such as timestamps, log levels, request IDs, module names, and context.
• Refactor existing logging calls to use the unified logger.
• Ensure compatibility with log aggregation and monitoring tools.
• Maintain backward compatibility with existing application behavior.

Expected outcome:

• Fully searchable and filterable logs.
• Improved debugging and operational visibility.
• Simplified auditing and compliance review.
• Consistent log structure across the application.
• Reduced effort for monitoring and incident investigation.

I have experience implementing structured logging systems in production applications and can deliver a scalable, audit-friendly solution that improves observability while keeping performance overhead minimal.

[Johnsource-hub]

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

[grantfox-oss]

🦊 GrantFox — @Johnsource-hub has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #29)
2. Your PR will be reviewed by the Vero-protocol maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Johnsource-hub's PR #58 was approved and merged by @N-thnI.

🏆 @Johnsource-hub: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (83 total points). Track your full progress on GrantFox.

👏 Great work, @Johnsource-hub! Keep contributing to Vero-protocol.