This month's work concentrated on two things: making the platform materially faster to use, and tightening the accuracy of the numbers we display across our funds.

Faster platform response times

Platform

We completed a significant database schema refactor across the platform. Views that previously took ten to twenty seconds to load — Portfolio, fund detail pages, and several admin surfaces — now return in under half a second in typical use. There is no change to what is displayed; the underlying data model was consolidated and the queries behind it were rewritten.

This is a foundational change and it unblocks several accuracy improvements described below, which depended on a cleaner data layer to be practical.

More reliable holdings and price data

Funds, FTaaS

Our on-chain indexer, which is responsible for keeping fund holdings, AUM, and NAV in sync with what happens on Solana, was rebuilt on a more maintainable foundation and now falls back to a polling loop if its live connection drops. In practice, this means fewer situations where a recent deposit or allocation change is slow to appear.

Alongside the indexer work, we identified and corrected a timestamp handling issue in our data pipeline where certain records were stored without timezone information. That discrepancy was quietly skewing a small number of holdings and AUM calculations; those calculations are now consistent.

We want to be direct about what is not yet resolved: in-fund swaps can still fail intermittently, and the per-fund Activity tab is temporarily unavailable while its query is being rebuilt. Both are tracked and will follow in a subsequent release.

Clearer NAV, AUM, and deposit figures

Funds

A rounding mismatch meant that NAV multiplied by the number of shares did not always equal the stated AUM — sometimes by a few cents, occasionally by more. NAV is now presented with enough precision that the two figures reconcile to within one US cent.

On the deposit screen, the minimum deposit is now labelled in the fund's actual deposit asset rather than a generic dollar sign. For the current rkShares funds this reads as USDC; for future funds that accept a different deposit token, it will display that token's symbol.

User experience

Platform, Funds

• Removed the visible flicker that occurred each time the historic holdings chart refreshed its values, on both the Portfolio and Funds views.

• Restored the Wormhole and dogwifhat ($WIF) token logos after their external image sources changed; both now load from a cached copy so they remain stable if the upstream URL moves again.

Fixes

• Bug: Fund detail pages no longer get stuck on the loading screen when opened from the Funds list in the app.

• Bug: The Holdings tab within a fund remains accessible immediately after a deposit. Note that the deposited balance itself can still take a short time to appear while indexing catches up — a separate improvement to that latency is in progress.

• Bug: Corrected the timestamp/timezone handling behind several fund calculations, removing a class of small numerical discrepancies in holdings and AUM.

If anything here does not behave as described, or you would like more detail on a particular change, please reach out via our support portal.