[Bug] Target pool deadline uses ledger sequence but frontend likely passes Unix timestamp

[grantfox-oss]

Getting Started

1. Fork the repository: https://github.com/JointSave-org/Joint_Save
2. Clone your fork:

   git clone https://github.com/<your-username>/Joint_Save.git
   cd Joint_Save

3. Create a new branch:

   git checkout -b fix/target-pool-deadline-ledger-sequence

---

Overview

TargetPool::initialize validates deadline as a ledger sequence number (u32), but the frontend form likely collects a date value (Unix timestamp). This mismatch sets deadlines incorrectly.

Steps to Reproduce

1. Create a Target Pool with a 30-day deadline using the date picker
2. Inspect the transaction on Stellar Expert
3. Compare deadline param to current ledger sequence

Required Fix

Frontend (target-form.tsx + useJointSaveContracts.ts)

• Replace date picker with a duration input (days/weeks/months)
• Add helper:

  function daysToLedgers(days: number): number {
    return Math.floor(days * 24 * 60 * 60 / 6); // ~6s per ledger
  }

• Fetch current ledger sequence from RPC, add offset before submitting

Display

• Show "Deadline: ~30 days (ledger ~XXXXXXX)" in form
• group-details.tsx: convert stored ledger sequence to estimated date

Acceptance Criteria

• Deadline param passed is a valid future ledger sequence
• Form shows human-readable duration, not a raw ledger field
• Group detail shows estimated deadline date
• refund remains callable after deadline passes

[Nanafancy]

Hi maintainer i have experience in rust,java script,typescript, c#, c++ python i have carefully read this and i will like to work on this please assign me

[xJeffx23]

Description
Getting Started
Fork the repository: https://github.com/JointSave-org/Joint_Save
Clone your fork:
git clone https://github.com//Joint_Save.git
cd Joint_Save
Create a new branch:
git checkout -b fix/target-pool-deadline-ledger-sequence
Overview
TargetPool::initialize validates deadline as a ledger sequence number (u32), but the frontend form likely collects a date value (Unix timestamp). This mismatch sets deadlines incorrectly.

Steps to Reproduce
Create a Target Pool with a 30-day deadline using the date picker
Inspect the transaction on Stellar Expert
Compare deadline param to current ledger sequence
Required Fix
Frontend (target-form.tsx + useJointSaveContracts.ts)
Replace date picker with a duration input (days/weeks/months)
Add helper:
function daysToLedgers(days: number): number {
return Math.floor(days * 24 * 60 * 60 / 6); // ~6s per ledger
}
Fetch current ledger sequence from RPC, add offset before submitting
Display
Show "Deadline: ~30 days (ledger ~XXXXXXX)" in form
group-details.tsx: convert stored ledger sequence to estimated date
Acceptance Criteria
Deadline param passed is a valid future ledger sequence
Form shows human-readable duration, not a raw ledger field
Group detail shows estimated deadline date
refund remains callable after deadline passes

[grantfox-oss]

🦊 GrantFox — @Nanafancy has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #13)
2. Your PR will be reviewed by the JointSave-org maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🦊 GrantFox — @xJeffx23 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #13)
2. Your PR will be reviewed by the JointSave-org maintainers

Good luck! Track your progress on GrantFox.