bug(sdk): VestflowClient.createSchedule is missing lockup_duration in args array — all calls fail

[libby-coder]

Problem

sdk/src/client.ts createSchedule builds an args array with 9 elements. The contract's create_schedule expects 10 (lockup_duration was added between cliff_duration and kind). Every SDK call to createSchedule fails at the RPC simulation step.

Fix

Insert nativeToScVal(lockupSecs, { type: 'u64' }) at index 7 in the args array. Add lockupDays?: number to CreateScheduleParams (defaulting to cliffDays).

[Emoji-dot]

@Emoji-dot 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 @Emoji-dot to this issue.

[drips-wave]

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

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

[dev-sylv]

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

I have reviewed this issue and I can work on it. Please assign me.

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

[idrisososanwo]

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

Hi maintainer, I would like to work on this issue.

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

[Johnsource-hub]

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

Hi, I'm Femi — a Full-Stack & Blockchain Developer with 3+ years of experience. I've reviewed this issue and I'm confident I can handle it. I'll submit a clean PR within 1-2 days max. Please assign it to me!

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

[drips-wave]

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

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