Fix legacy stake account migration after lock layout change

[cursor]

Bug and impact

Recent stake-lock changes added locked_until directly to StakeAccount. Existing pre-lock stake PDAs used the old serialized layout, so deposit_sol, withdraw_sol, and claim_mentik could fail during Anchor account deserialization before handlers ran. A user with SOL already staked before the redeploy could be unable to withdraw or claim.

Root cause

Instruction account validation used Account<StakeAccount>, which requires the current account layout. Old stake accounts were shorter by 8 bytes and could not be loaded.

Fix

• Load stake PDAs manually and accept both current and pre-lock serialized layouts.
• Treat legacy stake accounts as unlocked (locked_until = 0) and resize/serialize them to the current layout on the next successful deposit, withdraw, or claim.
• Preserve PDA seed/owner/user checks and update claim clients/IDL for the required system_program account.
• Add LiteSVM regressions for legacy withdraw and legacy claim migration.

Validation

• anchor build --ignore-keys
• cargo test -p mentik_sol_pool
• cargo test -p mentik-integration-tests (8 passed, including legacy migration tests)
• npm run build --prefix app

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
app	Error		Jun 6, 2026 9:23am