feat(frontend): Integrate backend user transactions in Solana scheduler and services#12229
Merged
AntonioVentilii merged 7 commits intomainfrom Mar 31, 2026
Merged
Conversation
…er and services Made-with: Cursor
Contributor
There was a problem hiding this comment.
Pull request overview
Integrates Solana backend user-transaction persistence into the Solana wallet scheduler and Solana transaction loading service, aligning behavior with the existing EVM pattern.
Changes:
- Load stored Solana user transactions from the backend and merge/seed them into frontend stores.
- Save newly discovered finalized Solana transactions back to the backend (fire-and-forget with error logging).
- Add/extend unit tests for scheduler and services backend integration behavior.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
src/frontend/src/sol/services/sol-transactions.services.ts |
Loads stored backend transactions and saves new RPC transactions, gated by USER_TRANSACTIONS_LOAD_FROM_BACKEND_ENABLED. |
src/frontend/src/sol/schedulers/sol-wallet.scheduler.ts |
Seeds scheduler’s internal transaction store from backend on initial sync and saves newly found RPC transactions. |
src/frontend/src/tests/sol/services/sol-transactions.services.spec.ts |
Adds tests asserting backend load/merge/save behavior for Sol transaction services. |
src/frontend/src/tests/sol/schedulers/sol-wallet.scheduler.spec.ts |
Adds tests asserting backend load-on-initial-sync and save-on-new-RPC behavior for the wallet scheduler. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
DenysKarmazynDFINITY
approved these changes
Mar 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The Solana user transaction services and utilities were introduced in #12220 and #12221, but the scheduler (
SolWalletScheduler) and the transaction loading service (loadSolTransactions) did not yet use them.This PR wires the backend persistence layer into both, matching the pattern already established for EVM in
eth-transactions.services.ts.Changes
sol-wallet.scheduler.ts: On initial sync (isInitialSync), load stored transactions from the backend vialoadSolUserTransactionsand seed the internal store. Save newly discovered RPC transactions back to the backend viasaveSolFinalizedTransactions(fire-and-forget with error logging viaconsoleError).sol-transactions.services.ts: In the privateloadSolTransactions, load stored transactions from the backend and merge them with fresh RPC results. Save new RPC transactions back to the backend. Both operations are gated behindUSER_TRANSACTIONS_LOAD_FROM_BACKEND_ENABLED.Tests
Added tests.