Bug: `parseGovernorConfig` / `GovernorConfig` type drop the on-chain `max_duration_seconds` field

[Jaydbrown]

File: src/governor.ts:60-77 (parseGovernorConfig), src/types/index.ts (GovernorConfig)

The on-chain GovernorConfig struct (contracts/governor/src/config.rs) is:

pub struct GovernorConfig {
    pub fee_bps: u32,
    pub fee_recipient: Address,
    pub min_duration_seconds: u64,
    pub max_duration_seconds: u64,   // <-- returned by DripGovernor::config()
    pub max_rate_per_second: i128,
    pub factory_address: Address,
}

parseGovernorConfig reads fee_bps, min_duration_seconds, max_rate_per_second,
fee_recipient and factory_address — but never reads max_duration_seconds, and
the SDK's GovernorConfig type has no field for it.

Impact

client.governor.getConfig() cannot tell a caller the protocol's maximum stream
duration, even though the contract enforces it (extend_duration /
top_up_and_extend reject durations over max_duration_seconds). A client that
wants to validate a stream length before submitting has no way to read the bound.

Suggested fix

Add maxDurationSeconds: number to GovernorConfig and parse
m['max_duration_seconds'] the same way as min_duration_seconds.

[Muyideen-js]

@Muyideen-js has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I can fix this

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

[Hasmong]

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

Hello, I’d be happy to work on this issue. I understand the requirements and can dedicate the necessary time to implementing and testing a suitable solution.

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

[Levi-Ojukwu]

@Levi-Ojukwu has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello maintainer, I can handle this issue.

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

[omoniyiadebayo12goal-crypto]

@omoniyiadebayo12goal-crypto has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer,

I’m adebayo. I have carefully reviewed the issue description, acceptance criteria, and expected deliverables. I am confident in my ability to implement a clean, maintainable, and effective solution. I would appreciate the opportunity to contribute to this task.

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

[drips-wave]

Congratulations, @Levi-Ojukwu! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Levi-Ojukwu's PR #659 was approved and merged by @Jaydbrown.

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

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