📂 Testnet | Network Boundary Logging Separation

[Sadeequ]

Description

Mixing local development logs with public network interaction data makes it incredibly difficult to audit transaction performance during integration phases.

Technical Requirements

Configure the logger to split outputs into separate files: system.log for internal engine behaviors and stellar-network.log exclusively for XDR envelopes, hashes, and network error codes.

[wokedi]

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

gm gm maintainer, I have reviewed the task description and will like to work on this issue please. ETA: 7hours. Thank you

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

[SharifIbrahimDev]

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

Hi @Sadeequ, I’d like to work on this issue.

I have experience building structured logging systems for backend services and blockchain-integrated applications. I can implement a clean logging separation strategy to isolate internal engine activity from Stellar network interaction data for easier auditing and debugging during Testnet integration.

My implementation will include:

• Separate log streams for system.log and stellar-network.log
• Dedicated handling for XDR envelopes, transaction hashes, Horizon/RPC responses, and network error codes
• Structured and consistent log formatting for easier traceability
• Minimal disruption to the existing logging flow while improving observability and debugging efficiency

I’ll also verify that the logging boundaries remain reliable under concurrent network activity and error scenarios.

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

[drips-wave]

Congratulations, @SharifIbrahimDev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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

[drips-wave]

This issue has been completed by @SharifIbrahimDev as part of the Stellar Wave Program's 5th Wave 🥳

😎 @SharifIbrahimDev: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.