Add fee accounting balance-conservation tests

[Chucks1093]

Summary
Add focused tests that verify fee accounting conserves value across protocol and creator fee paths.

Scope

• add tests that validate buy/sell fee splits sum correctly
• assert no value is lost or created across balance movements
• cover at least one edge case around low-value trades

Acceptance Criteria

• tests fail when fee accounting drifts from conservation expectations
• tests pass for current intended fee behavior
• assertions are clear enough for contributors to extend

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[Dagdon]

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

Hello, I will love to work on the accounting balance-conservation tests issue.

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

[Menjay7]

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

Hi! I’m, a full-stack developer with a background in blockchain. I would love to take on this issue. I have extensive experience in both frontend and backend development and am confident I can implement a clean solution. Could you please assign this to me?

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

[latentchronos]

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

Hello, I'd like to take this on, I understand what you're after, conservation tests that act as a safety net, ensuring every wei that enters the fee pipeline comes out the other side correctly split between protocol and creator, with zero value leaked. the tests should be deterministic invariants. I'm ready to get started

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

[Obiajulu-gif]

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

My Chief, I will love to work on this issue

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

[drips-wave]

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

🧑‍💻 @Obiajulu-gif: 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 marked as completed by a Drips Wave moderator for @Obiajulu-gif as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The PR #177 comprehensively addresses the issue by adding detailed tests for fee accounting and balance conservation. It has been open for over 24 hours with no maintainer objections, and the code directly satisfies the acceptance criteria including edge cases and boundary conditions.

😎 @Obiajulu-gif: 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.