Implement Database Transactions for Savings History

[codeZe-us]

To prevent data corruption or inconsistencies between the local database and the Stellar blockchain, deposits and withdrawals must be processed within strict ACID transactions.

Implementation guidelines:

• Use Drizzle ORM's db.transaction() wrapper in backend services that write savings data.
• When recording a successful deposit or withdrawal, lock the user's ledger status, insert the transaction history entry, and update the cached savings balance in a single transactional block.
• Roll back the transaction if any of the operations fail or if a conflict is detected.

Files location: backend/src/server/actions.ts, defindex_service.ts

Expected result: Database operations for savings transfers are executed safely, preventing race conditions or partial writes in the database.

Join the contributor Telegram group and ask any questions: https://t.me/+8mSQnieRmIM1Yjc0

[GazzyLee]

gm gm boss, I’d like to take this one on. I’ll wrap the deposit and withdrawal database updates in Drizzle transactions so the ledger status, transaction history, and cached savings balance are updated atomically. I’ll ensure failures or conflicts roll back the entire operation, preventing partial writes and race conditions, and add tests covering successful transactions and rollback scenarios.

[obswrld]

I would like to work on this Issue

[Ogstevyn]

Hi, I’m interested in working on this issue. I’m a full-stack blockchain developer with experience across blockchain development. I’d be happy to contribute to the project and work on this task.

[Ogstevyn]

Hi, I’m interested in working on this issue. I’m a full-stack blockchain developer with experience across blockchain development. I’d be happy to contribute to the project and work on this task.

[QwinDivy]

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

Hi Maintainer, I’d love to work on this. I’ve looked through the codebase and feel confident about the approach. I’ll keep the implementation focused, add appropriate tests, and make sure CI passes. I can also open a draft early for feedback and alignment.

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

[drips-wave]

Congratulations, @QwinDivy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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