Refactor assets management page to use Stellar RPC API instead of Horizon #51
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.
Successfully refactored the assets management page (
/dashboard/assets) to use Stellar RPC API instead of the deprecated Horizon API, following the patterns from stellar/stellar-docs#1775.Changes Made
Assets Page (
src/routes/dashboard/assets/+page.svelte)submitimport with local RPC-based implementation using@stellar/stellar-sdk/rpcTransaction Module (
src/lib/stellar/transactions.js)createChangeTrustTransactionto use RPCServer.getAccount()instead of HorizonloadAccount()Balance Data Migration
fetchAccountRPC,fetchAccountBalancesRPC) insrc/lib/stellar/horizonQueries.jssrc/routes/dashboard/+layout.js) to use RPC for balance queries supporting the assets pageKey Features
Testing
The implementation follows the exact patterns from the referenced stellar-docs PR #1775, ensuring consistency with recommended RPC usage patterns for Stellar applications.
This pull request was created as a result of the following prompt from Copilot chat.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.