Implement deposit (lock assets) flow with Freighter signing and simulation

[prodbycorne]

Problem

The farm page has no deposit / lock-assets button. Users can see pool rows and attempt to unlock, but there is no way to actually stake assets into a pool. The sorobanService has a lockAssets method skeleton but there is no UI flow to invoke it.

Expected Behaviour

A Deposit modal (or inline form) allows a connected user to enter an amount, preview the transaction fee via Soroban simulation, and sign + submit the lock_assets call through Freighter. On success the pool row updates to show the new stake and a lockdown countdown begins.

Acceptance Criteria

• A "+ Deposit" button appears on each pool row in src/app/farm/page.tsx (visible when wallet is connected)
• Clicking opens a modal with:
  • Amount input validated against the user's on-chain Stellar balance (fetched from Horizon)
  • Fee preview obtained via rpcServer.simulateTransaction before the user signs
  • A clear display of the minimum lock period so users know when they can unlock
• Transaction is built using TransactionBuilder, simulated, and signed via walletApi.signTransaction; the signed XDR is then submitted through rpcServer.sendTransaction
• Transaction status is polled via rpcServer.getTransaction until SUCCESS or FAILED; the UI shows a progress spinner with hash link during polling
• On success, React Query cache for userPosition and pools is invalidated so balances refresh automatically
• Input is disabled and shows a spinner while the transaction is in-flight to prevent double submission
• A Vitest test mocks rpcServer and asserts the correct Soroban operation is built with the right contract address and argument encoding

Relevant Files

• src/app/farm/page.tsx — add deposit button to EarningRow
• src/lib/soroban.ts — lockAssets method (implement the actual contract call)
• src/hooks/useSorobanQuery.ts — add useLockAssets mutation
• src/config/index.ts — poolContractId, networkPassphrase

[Sparexonzy95]

Hi SmartDropLabs team,

I would like to take this issue.

I understand that this is not only a UI task of adding a Deposit button. The real problem is that the farm page currently does not complete the full lock-assets lifecycle: selecting a pool, validating the deposit amount, preparing the Soroban contract call, simulating before signing, submitting through Freighter, polling the transaction result, and refreshing the user’s position after success.

My approach will be to implement the flow end-to-end in a focused PR.

First, I will add a connected-wallet-only “+ Deposit” action on each pool row in src/app/farm/page.tsx. When clicked, it will open a deposit modal where the user can enter an amount, see the pool’s minimum lock period, and get clear validation feedback before submitting.

Second, I will complete the lock-assets transaction path in src/lib/soroban.ts. The transaction will be built with TransactionBuilder, call the correct pool contract’s lock_assets method with the connected wallet address and encoded amount, run Soroban simulation first to obtain the fee preview, then request signing through walletApi.signTransaction. After signing, the signed XDR will be submitted with rpcServer.sendTransaction.

Third, I will add proper transaction lifecycle handling. After submission, the UI will poll rpcServer.getTransaction until the transaction reaches SUCCESS or FAILED. While the transaction is pending, the modal input and submit button will be disabled to prevent duplicate submissions, and the user will see a progress state with the transaction hash link.

Fourth, I will wire this through a useLockAssets React Query mutation in src/hooks/useSorobanQuery.ts, so a successful deposit invalidates the pool and user position queries. This will allow the farm row to refresh automatically and show the updated stake/countdown state.

I will also include a focused Vitest test that mocks the RPC layer and verifies that the correct Soroban operation is built with the expected contract address and argument encoding.

The PR will stay scoped to the deposit / lock-assets flow, with a clear implementation summary, testing notes, and no unrelated refactors.

[grantfox-oss]

🦊 GrantFox — @Sparexonzy95 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 #19)
2. Your PR will be reviewed by the SmartDropLabs maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Sparexonzy95's PR #61 was approved and merged by @prodbycorne.

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

👏 Great work, @Sparexonzy95! Keep contributing to SmartDropLabs.