Enforce canonical token ordering in pair identifiers

[Baskarayelu]

Enforce canonical token ordering in pair identifiers

Description

• Pair keys can be generated in non-canonical order, enabling duplicate market representations.

Requirements and context

• Standardize key creation with deterministic ordering.
• Keep lookup compatibility for existing pairs.

Suggested execution

• Sort token addresses when deriving pair IDs.
• Migrate or alias legacy keys where necessary.

Test and commit

• Add tests proving (A,B) and (B,A) resolve identically.
• Ensure duplicate pair creation is impossible.

Example commit message

• fix(contracts): canonicalize token ordering in pair keys

Guidelines

• Avoid expensive sorting beyond two-token pairs.
• Keep event payload ordering consistent.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Abolax123]

@Abolax123 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi, I’d like to work on this issue. I can implement canonical token ordering for pair identifiers by deterministically sorting token addresses during pair key derivation, ensuring (A, B) and (B, A) resolve to the same key. I’ll maintain backward compatibility by handling or aliasing legacy keys, prevent duplicate pair creation, and add tests to verify consistent behavior. The solution will be efficient, secure, and easy to review.

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

[drips-wave]

Congratulations, @Abolax123! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

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