[SDK] Implement Keypair.fromMnemonic utility for recovery

[Solomonsolomonsolomon]

Add a securely tested utility to @chenpilot-experimental/sdk for deriving Stellar keys from a standard 12/24-word mnemonic.nn- Priority: High

[Vvictor-commits]

@Vvictor-commits has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

please assign this issue to me

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

[victorEdeh]

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

i want to work on this

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

[Agbasimere]

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

I'd like to work on this issue.

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

[gelluisaac]

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

I’m interested in tackling this! I have a strong background in smart contract development and full-stack systems, so I'm well-equipped to handle the requirements here. Could you please assign this to me?

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

[Habibah371]

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

can i work on this issue please
kindly assign

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

[legend-esc]

@legend-esc has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue because automatically deactivating expired campaigns is an important consistency and reliability improvement that prevents stale campaigns from remaining active indefinitely in both the backend and potentially on-chain state. Automating this process reduces operational overhead, improves data integrity, and ensures frontend users are not presented with expired campaigns as still active.

I have experience implementing background job systems, scheduled maintenance tasks, and blockchain-integrated backend workflows, and I’m comfortable building reliable automation that safely synchronizes off-chain and on-chain state transitions. For this issue, I would focus on extending the existing job runner in backend/src/index.js with a scheduled campaign-expiration task that identifies campaigns whose endDate has passed and automatically marks them inactive in the database.

I would also implement optional on-chain synchronization logic to call set_active(false) when a linked contract exists, while ensuring failures in blockchain interaction do not corrupt backend state or halt the scheduler. Particular attention would be given to idempotency, retry-safe behavior, structured logging, and efficient querying so the job remains safe and performant as campaign volume grows. In addition, I would add tests covering expired campaigns, already-inactive campaigns, missing contract links, and partial-failure scenarios to ensure the automation behaves reliably under real-world conditions.

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

[AkamyUI]

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

Can i work on this issue

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