Interest-rate reserve-param timelock is queue-only — no UI to apply or cancel pending changes

[grantfox-oss]

Problem

The lending contract implements a proper 2-step governance timelock for interest-rate risk parameters: queue_set_reserve_params → wait out the unlock delay → apply_queued_reserve_params (or cancel_queued_reserve_params before it unlocks). The frontend only wires the first step:

• InterestRateParamsForm.tsx (apps/web-app/src/features/admin/components/) only calls lendingService.setInterestRateParams(), which wraps queue_set_reserve_params.
• apply_queued_reserve_params and cancel_queued_reserve_params are exposed on the generated contract client (packages/contracts/lending/src/index.ts) but are never called anywhere in the frontend.
• There is no getter for QueuedReserveConfig { new_params, unlock_time } in the binding, and no UI surfaces whether a change is pending, when it unlocks, or lets an admin apply/cancel it.

Why this needs real judgment, not a quick patch

Once an admin queues a reserve-param change today, it is effectively stuck — there's no way to see it, wait it out, apply it, or cancel it from the app. Fixing this requires:

• Deciding how to reconstruct pending-queue state given there's no direct getter — most plausibly by querying Soroban contract events by topic, mirroring the existing pattern in getActiveBadDebtAuctions() (apps/web-app/src/lib/helpers/stellar/lending.ts), or by reading contract instance/temporary storage directly.
• Building unlock-time countdown + apply/cancel controls per pool/asset, analogous to the already-working backstop withdrawal-queue flow in apps/web-app/src/features/backstop/hooks/useBackstop.ts (a genuinely similar "queue then execute after a delay" UX, worth using as a pattern reference — not a template to copy verbatim since the domain differs).
• Handling the case where the calling admin isn't the one who queued the change, and where a queued change has already unlocked vs. is still pending.

Scope

• apps/web-app/src/features/admin/components/InterestRateParamsForm.tsx (add pending-queue table + apply/cancel controls)
• A new hook, e.g. useQueuedReserveParams
• apps/web-app/src/lib/services/lending.service.ts (add applyQueuedReserveParams/cancelQueuedReserveParams wrappers)
• Possibly a small addition to apps/web-app/src/lib/helpers/stellar/lending.ts for event querying

Acceptance criteria

• Admin UI shows any currently-queued reserve-param change per pool/asset, including unlock time
• Admin can apply a queued change once unlocked
• Admin can cancel a queued change before it unlocks
• Clear state distinction between "no change queued," "queued but locked," and "queued and ready to apply"
• No regression to the existing queue (setInterestRateParams) flow

This is cross-cutting architectural work (missing half of a contract's governance flow, requiring new state-reconstruction logic) — evaluated per the project's PR rubric as HARD complexity.

[salienne]

Hello, I went through the issue details and have already identified the relevant implementation path. I'm confident I can deliver a maintainable and well-tested solution.

[David-282]

I'd like to work on this issue. I'll carefully review the requirements, implement the necessary changes, add or update tests where needed, and ensure everything meets the project's guidelines before submitting a PR.

[ryzen-xp]

Hi maintainers 👋
I’m a blockchain developer with strong expertise in Stellar, Rust,TS and Stellar SDK integrations. I’ve worked on multiple Stellar-based smart contract and backend systems.

I understand the scope of this issue and can deliver a reliable, production-quality solution with proper tests and documentation.
Plz assign me !!

ETA: 24 hours

[TS-mfon]

GM

i'm a blockchain developer

please can i work on this issue

[Heazzy500]

Hi, I’ve applied for issue #286 (Interest-rate reserve-parameter timelock). I’m interested in working on this task and have gone through the issue requirements. I’d be glad to contribute and implement the solution.

Please let me know if there’s anything specific you’d like me to clarify or focus on regarding the implementation. Thank you!

[Heazzy500]

Hi, I’ve applied for issue #286 (Interest-rate reserve-parameter timelock). I’m interested in working on this task and have gone through the issue requirements. I’d be glad to contribute and implement the solution.

Please let me know if there’s anything specific you’d like me to clarify or focus on regarding the implementation. Thank you!

[DevSolex]

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

[Gentleslyl2006]

Hello maintainer
I'm idea, please assign this issue to me.
I can fix it and will submit PR immediately

[Josue19-08]

Hello maintainers

My name is Josué, and I’m a dedicated open-source contributor and full-stack developer with strong experience building and maintaining production-level applications across both Web2 and Web3 ecosystems. I’ve worked extensively with Stellar infrastructure, Soroban smart contracts, and backend services, alongside modern frontend development using React, TypeScript, and scalable UI architectures. Beyond just implementation, I focus on designing clean, maintainable systems — from structuring data models and APIs to crafting intuitive user experiences. I’ve also been actively involved in multiple open-source initiatives and hackathons, where I’ve contributed meaningful features, improvements, and fixes across different repositories. I’m comfortable navigating the full contribution lifecycle — from understanding the problem and proposing solid technical solutions, to delivering clean code, tests, and well-documented pull requests aligned with project standards. This issue strongly matches my skill set, and I’m confident I can provide a reliable and maintainable solution within a reasonable timeframe. You’re welcome to review my GitHub profile to explore my previous contributions, ongoing open-source work, and technical background. I care deeply about code quality, scalability, and clear collaboration, and I’m genuinely excited about the opportunity to contribute and help move this project forward.

Thank you for your consideration

[IfyJustin91]

hi, i would like to work on this issue

[Promise278]

Hi i have expereince with system design and archecture i would love to work on these please would submit PR after 3 hours given

[bobo-24]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. I’ll prioritize this immediately and ensure a reliable solution is delivered as soon as possible. Thank you!