core: add direct Soroban read layer for on-chain state verification

[EmeditWeb]

Problem

The web app reads all protocol data through the API, including on pages whose
entire purpose is trust-minimized verification — yet Contracts.tsx displays
fabricated SHA-256 hashes (#61) and Home.tsx shows hardcoded pool stats (#60).
Users have no way to verify API-served numbers against the chain. There is no
client-side read path that queries Soroban contract state directly.

Before Starting

Read ALL of these before writing any code:

• context/architecture-context.md
• context/code-standards.md

What To Build

A direct Soroban read layer usable from the services tier:

1. A contract read service using stellar-sdk / Soroban RPC
   getLedgerEntries (and simulated read-only calls) to fetch live pool
   stats, share price, reputation scores, and loan status directly from the
   deployed contracts (addresses from constants/config).
2. A verification surface (Contracts page) that shows the real deployed WASM
   hashes and lets a user reconcile API-reported values against on-chain
   reads, flagging any mismatch.
3. Read-only, no signing; graceful loading/error/empty states and typed
   results.

Files To Touch

• src/services/soroban.service.ts (new)
• src/constants/ (contract addresses / RPC config)
• src/pages/Contracts.tsx, src/pages/Home.tsx (consume real reads)

Acceptance Criteria

• Pool stats/share price/reputation readable directly from Soroban RPC
• Contracts page shows real deployed WASM hashes (no fabricated values)
• API-served values can be reconciled against on-chain reads with mismatch flag
• Read-only path; no signing or writes
• Loading, error, and empty states handled; tests cover the read service

Mandatory Checks Before Opening PR

• All context/ files read and understood
• npm run lint passes with zero errors
• npm run build passes with zero errors
• npm test passes — test count not decreased
• No hardcoded hex colors; icons from lucide-react only
• No API calls in page files
• Tested on 375px mobile viewport
• PR references this issue number

[julianvillalba688]

Hi team,

I would love to take on this issue. Bringing true, trust-minimized verification to the web interface by adding a direct Soroban read path is exactly the kind of task I enjoy. Here is a brief summary of my experience and how I plan to approach the implementation:

My Experience
As a backend and full-stack engineer with deep experience in blockchain integrations and state synchronization, I am highly comfortable interacting directly with RPC nodes and smart contract states. I have hands-on experience handling asynchronous ledger calls, managing state reconciliation between APIs and on-chain environments, and implementing clean, type-safe services. I know exactly how to structure read-only simulations and deal with node latency without compromising front-end performance.

Proposed Approach
Direct Soroban Service (src/services/soroban.service.ts): I will establish a dedicated read layer utilizing stellar-sdk and getLedgerEntries (alongside read-only invocations) to pull live data—such as pool statistics, share prices, reputation scores, and actual deployed WASM hashes—directly from the network using the addresses defined in your configuration constants.

State Reconciliation & Mismatch Indicators: In the page layers, I will pull both the API payloads and the direct Soroban reads via the services tier. I'll implement a comparison mechanism that automatically flags any data discrepancies, replacing the current fabricated hashes and hardcoded pool stats on Contracts.tsx and Home.tsx with authentic ledger data.

Purely Read-Only, Secure Execution: This layer will be entirely decoupled from any wallet signing logic. It will remain a passive, highly efficient, and fully typed querying infrastructure.

Resilient UI/UX & Formatting Constraints: I will ensure all data states (loading, error, empty) are fully handled. All icons will exclusively use lucide-react, all styling will obey your design token constraints (no hardcoded hex colors), and the presentation will be verified to render perfectly down to a 375px mobile viewport.

I will thoroughly read context/architecture-context.md and context/code-standards.md prior to writing code, and ensure that npm run lint, npm run build, and npm test all pass with flying colors before submitting the PR.

Looking forward to helping make StepFi fully trust-minimized!

[Danielodingz]

Hey maintainer, please i would like to work on this issue.

[mubking]

Hi, I'm Mubaraq — a Full-Stack & Blockchain Developer with 3+ years of experience. I've reviewed this issue and I'm confident I can handle it. I'll submit a clean PR within 2–3 days. Please assign it to me!

[mubking]

Hi, I'm Mubaraq — a Full-Stack & Blockchain Developer with 3+ years of experience. I've reviewed this issue and I'm confident I can handle it. I'll submit a clean PR within 2–3 days. Please assign it to me!

[mubking]

Hi, I'm Mubaraq — a Full-Stack & Blockchain Developer with 3+ years of experience. I've reviewed this issue and I'm confident I can handle it. I'll submit a clean PR within 2–3 days. Please assign it to me!