Build a Main Runner with Scenario Output

[codeZe-us]

Build a main.go that constructs realistic deposit scenarios, runs each through extractRouting then FilterDeposit, and prints a formatted summary using structured logging.

Contribution Guide

• PRs go to the dev branch, not main
• Application must explain your specific approach to this task ; generic applications will not be assigned
• PR description must clearly describe what you built and changed
• Link your PR to the correct issue number (e.g. Closes #12)

Implementation Guidelines
Key files: examples/go-exchange/contract-deposit-firewall/cmd/main.go

• At least 6 scenarios: clean muxed, clean memo, contract sender, muxed + memo collision, no routing info, contract sender + ambiguous routing combined.
• For each: construct RoutingInput, call extractRouting, call FilterDeposit, log the result.
• Use log/slog with JSON handler. Each log entry: scenario name, routing source, warnings, decision.
• Exit code 0 if all decisions match inline expectations, exit code 1 on mismatch.

Expectations
What done looks like: go run ./cmd/main.go prints six structured JSON log lines. All decisions match expectations.

Discord for questions: codeze_us

[Jidetireni]

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

HI! I'D LIKE TO TAKE ON ISSUE #222.

MY APPROACH: I'LL BUILD cmd/main.go WITH 6+ DEPOSIT SCENARIOS (CLEAN MUXED, CLEAN MEMO, CONTRACT SENDER, MUXED + MEMO COLLISION, NO ROUTING INFO, AND CONTRACT SENDER + AMBIGUOUS ROUTING). EACH SCENARIO WILL CONSTRUCT A RoutingInput, RUN IT THROUGH extractRouting AND FilterDeposit, THEN LOG THE RESULT AS STRUCTURED JSON USING log/slog. EXIT CODE WILL REFLECT WHETHER ALL DECISIONS MATCH INLINE EXPECTATIONS.

THANKS FOR CONSIDERING!

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

[drips-wave]

Congratulations, @Jidetireni! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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