Oracle price-staleness threshold should be governor-configurable

[Jaydbrown]

The staleness window is currently a compile-time constant. Move it into governor config so it can be tuned per-deployment without a contract upgrade, and emit an event when a submission is rejected as stale.

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[Ranjeet2063]

Hi maintainers, I would love to be assigned to this issue.

I am an active core contributor in the Stellar/Soroban ecosystem (#1 contributor on Mova Store with 28 successfully merged PRs), with deep expertise across Soroban SDK smart contracts, cryptographic access controls, and production test suites.

🎯 Technical Execution Plan for Oracle price-staleness threshold should be governor-configurable:

1. Module & Storage Analysis: Pinpoint the exact contract modules in conduit-protocol/streamFi-contracts handling this logic. Define explicit storage DataKeys, TTL policies, and auth boundaries (require_auth()).
2. Canonical Soroban Implementation: Implement the required state changes, validations, and structured event emissions (env.events().publish(...)) adhering strictly to official Soroban best practices and zero arithmetic overflow/underflow.
3. Exhaustive Unit Test Suite: Build comprehensive tests covering:
   • Happy-path state transitions and expected outputs.
   • Boundary limits, edge cases, and zero/saturating values.
   • Negative tests asserting unauthorized callers (mock_auths(&[])) and invalid parameter reverts with exact ContractError variants.
4. CI & Verification Gate: Verify 100% clean cargo check, zero clippy warnings, and full test suite passing locally before opening the PR.

💡 Why Assigning Me Directly Benefits You:

• Zero Maintainer Overhead: Self-documenting code with exhaustive tests so you don't spend valuable time babysitting, debugging, or fixing CI.
• Fast Issue Closure: Production-grade PR delivered in 12–24h, cleanly clearing this issue off your backlog.
• Proven Reliability: 28 merged PRs as #1 contributor on Mova Store — guaranteed senior-level execution from day one.

[shobhamerabacha-star]

Hi maintainers,

I can tackle Oracle price-staleness threshold should be governor-configurable. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in conduit-protocol/streamFi-contracts
• Implementation: Implement Oracle price-staleness threshold should be governor-configurable with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Testing: Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.
• PR: Atomic commit with clean git hygiene and passing CI

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[ranjeet150]

Hi maintainers,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Implement Oracle price-staleness threshold should be governor-configurable with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Testing & Verification: Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.
• Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

Excited to work on this—please assign to me and I'll submit a clean PR shortly!

[guptakumarranjeet150]

Hey team,

I can tackle Oracle price-staleness threshold should be governor-configurable. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in conduit-protocol/streamFi-contracts
• Implementation: Implement Oracle price-staleness threshold should be governor-configurable with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Testing: Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.
• PR: Atomic commit with clean git hygiene and passing CI

Excited to work on this—please assign to me and I'll submit a clean PR shortly!

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@ranjeet150's PR #549 was approved and merged by @Jaydbrown.

🏆 @ranjeet150: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (175 total points). Track your full progress on GrantFox.

👏 Great work, @ranjeet150! Keep contributing to conduit-protocol.