Perf: Optimize multi-pool health check with batched storage reads

[devdianax]

Context

Liquidators and frontends query health across multiple pools. Each query is a separate storage read.

Current Limitation/Problem

Health check per pool requires separate cross-contract call. N pools = N calls with N storage reads each.

Expected Outcome

Batched health check function that reads multiple pool states in a single call and computes health for all.

Acceptance Criteria

• BatchView function: accepts array of (pool, user, asset) tuples
• Single storage read to load pool config for all queried pools
• Parallel health computation: no cross-contract calls between computations
• Response: array of health factors, collateral values, debt values
• Gas comparison: batched vs individual per query count
• Pagination for large queries (100+ positions)
• Caching: cache batched results within transaction scope

Technical Scope

• contracts/lending-pool/src/batch_view.rs - batched health check
• Frontend use: batch all visible positions in single query
• Gas benchmark: individual vs batched at various query sizes
• Edge cases: partial results on pool failure, stale data in cached results

[Osifowora]

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

​Hi maintainer, I would love to work on this issue. I can get started on it right away.

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

[Adesam007-pr3dator]

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

Hi, I would love to work on this issue

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

[adepoju2006]

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

I have experience optimizing multi-pool queries in Soroban contracts by batching storage reads. I'll implement a batched health check function that reads all required pool state in a single pass, reducing N separate cross-contract calls to one efficient batch, lowering latency for liquidators and frontends significantly.

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

[Jerry-Tekh]

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

Hi repo manager... please can I start on this one?

I'll add a BatchView function to stellarlend in contracts/lending-pool/src/batch_view.rs that accepts an array of (pool, user, asset) tuples, loads pool configs in a single storage read, computes health factors, collateral, and debt in parallel with no cross-contract calls, supports pagination + tx-scope caching, and includes gas benchmarks vs individual queries.

Please assign me.

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

[fairbid01]

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

I would like to work on this issue

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

[devonahi]

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

Hello maintainer, I can handle this issue.

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

[drips-wave]

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

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