Multi-asset basket pricing

[Miracle656]

Background

Index/basket prices (e.g., "top 5 LATAM stablecoins") are useful for analytics.

What to build

/basket?asset=…&weight=… returning a weighted basket price.

Key files

• src/routes/basket.ts (new)

Acceptance criteria

• Weighted by user weights
• Normalizes to 1.0

Drips Wave · Complexity: Intermediate · 150 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[Danto1606]

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

I would like to work on this

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

[edehvalentine236-jpg]

@edehvalentine236-jpg has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer, I'm Valentine. I would like to resolve this issue. Kindly assign.

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

[collinsezedike]

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

This is a fun one. Weighted index pricing is simple math but easy to get subtly wrong on the normalization step.

Here's my plan:

• src/routes/basket.ts: new route accepting asset and weight as repeated query params (e.g. ?asset=USDC&weight=0.5&asset=USDT&weight=0.5)
• Normalize the supplied weights to sum to 1.0 before computing the basket price, regardless of what the raw input sums to
• Fetch current prices for each asset, multiply by its normalized weight, and sum for the final basket price
• Validate that asset and weight arrays are the same length and reject otherwise

Happy to start as soon as I'm assigned.

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

[drips-wave]

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

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