PE-9131: Minimize Solana RPC usage in sync and gateway registry

[vilenarios]

Summary

Investigation of heavy traffic to ArDrive's QuikNode Solana RPC found two structural sources; this PR eliminates both.

1. Sync no longer sweeps ArNS on every run

Every sync (auto-sync ~5 min, tab-focus restarts, manual) called getAntRecordsForWallet(update: true) — deliberately bypassing the repository's 15-minute cache — walking every owned ArNS name on Solana (several RPC calls per name), plus a post-sync saveAllFilesWithAssignedNames pass. ArDrive currently has no ArNS integration, so this was pure RPC cost with no user-facing effect. Both call sites and the ARNSRepository dependency are removed from SyncRepository. On-demand ArNS lookups elsewhere (upload flows, profile name) are untouched; sync-time integration can return later with the feature.

2. GAR gateway list: fetch at most once ever, refresh only on demand

The AR.IO gateway list was re-fetched from Solana RPC every app session (data-fetch fallback, snapshot validation) and on every open of the gateway settings modal. It's now persisted in local storage:

• DataGatewayFallback: memory → persisted cache → single SDK fetch (persisted on success). Across sessions the network is hit at most once, ever.
• Gateway settings serve the cached list; a new "Refresh list" button (new RefreshGateways bloc event) force-fetches and persists — the only path that re-hits the RPC.
• SnapshotValidationService reads through the same shared cache.
• Corrupt/missing persisted entries fall back to a normal fetch; fetch failures are cached in memory only (never persisted) so the next session retries.

Expected impact

Steady-state Solana RPC volume drops to ~zero for a signed-in user who isn't using crypto top-ups or explicitly refreshing the gateway list.

Tests

• New DataGatewayFallback persistence suite (store-hit/no-RPC, fetch-once-persist, cross-session reuse, failure non-persistence, corrupt-entry recovery, forced refresh)
• gar_repository_test rewired to the shared cache (asserts no SDK call on plain getGateways)
• Sync optimization tests updated for the removed dependency
• Includes the shared equatable CI pin (identical commit as PRs PE-9129: Sync and login resiliency quick wins #2162/PE-9130: Point GraphQL at turbo-gateway.com directly with Goldsky fallback #2164; merges cleanly in any order)

Note: local test execution was unavailable for this branch (WSL→Windows interop broke mid-session); CI is the validation gate for this PR — please wait for green before review.

🤖 Generated with Claude Code

https://claude.ai/code/session_0172nfTRDj7wgnhs44Lg6mxC

[coderabbitai]

Warning

Review limit reached

@vilenarios, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 4 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 788e0aa5-c505-4333-a4da-18eb3ed43f5d

📥 Commits

Reviewing files that changed from the base of the PR and between 0860808 and fe3d465.

📒 Files selected for processing (12)

• lib/gar/domain/repositories/gar_repository.dart
• lib/gar/presentation/bloc/gar_bloc.dart
• lib/gar/presentation/bloc/gar_event.dart
• lib/gar/presentation/widgets/gar_modal.dart
• lib/main.dart
• lib/services/arweave/data_gateway_fallback.dart
• lib/sync/data/snapshot_validation_service.dart
• lib/sync/domain/repositories/sync_repository.dart
• packages/ardrive_ui/pubspec.yaml
• test/gar/domain/repository/gar_repository_test.dart
• test/services/arweave/data_gateway_fallback_test.dart
• test/sync/domain/sync_repository_optimization_test.dart

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch perf/minimize-solana-rpc

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[vilenarios]

Consolidated into #2162 so all sync improvements can be tested on one preview build. Branch merged there commit-for-commit.

[github-actions]

Visit the preview URL for this PR (updated for commit fe3d465):

https://ardrive-web--pr2165-perf-minimize-solana-qch8uf45.web.app

_{(expires Thu, 16 Jul 2026 18:04:58 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: a224ebaee2f0939e7665e7630e7d3d6cd7d0f8b0}