We continue our journey after a month of public progress in our open development phase. Below, you will be able to see the most remarkable updates from last week.

If you would like to know more or have any further questions, feel free to reach out at [email protected] and if you would like to request any additional feature to our roadmap, share your feedback here.

Public beta preparation

We're continuing to prepare our public beta and have implemented a toggle between Production and Beta environments, allowing users to test new platform features.

The public beta environment will be connected to Solana mainnet, meaning deposits will use real assets. However, we've set a maximum limit of 10 USDC per user, allowing participants to acquire and redeem test fund shares while sharing feedback with us. This approach will help mature the platform, build early user traction, and generate valuable feedback for continuous improvement. The estimated launch of the beta environment will be this first half of 2026.

Important: Assets in the beta environment are not regulated managed funds.

Granular Transferability Controls

In our Solana program we have implemented transfer hooks leveraging Token 2022, however current implementation that will be delivered in our first release only allows fund shares transferability enabled or disabled, without additional granularity. As part of US regulation and dependent on the tokenized security type, a fund managed could enable transferability to specific personas, like KYCd investors or accredited investors. On this phase we have completed the first phase of this implementation that is expected to land in Version 1 of our platform, expected to be shipped on the second half of the year.

Fixes

• Bug: Remove duplicated metadata on the landing page so search engines index pages correctly and social previews render as expected

• Bug: Funds → Activity links to Transactions now point to Mainnet instead of Devnet

• Bug: Portfolio → My transactions renders reliably so you can review history without UI errors

• Bug: An issue when redeeming fund shares have been solved and balances update as expected.

• Bug: A sandpit fund was not loading after having intereacted with it. Now the fund page loads consistently.

• Bug: Multiple various minor fixes across frontend to adapt to multiple devices and resolutions.

We continue our journey after three weeks of public progress in our open development phase. Below, you will be able to see the most remarkable updates from last week.

If you would like to know more or have any further questions, feel free to reach out at [email protected] and if you would like to request any additional feature to our roadmap, share your feedback here.

Deposit and Redeem Flow Improvements

You get a clearer flow for depositing and redeeming funds. The new design and implementation in our sandpit environment use a more traditional, public-oriented approach. This new approach is intended to minimize user interactions while at the same time showing all the required information, such as a simulation of shares obtained when depositing and the self-survey to meet the eligibility criteria defined by the SEC.

KYC/KYB implementation with Persona

This past week, we have progressed in our sandpit environment to deploy our end-to-end workflow for KYC/KYB and accredited investor verification with our provider, Persona. This integration, required by the SEC in order to offer our tokenized managed funds, will enable us to comply with regulations while also providing a smooth and quick onboarding experience, with automated workflows and document verification enabled by AI-based capabilities.

This is just an example on how one of our screens will looks like:

Two-Factor Transaction Signing

You can require a second factor authentication when you sign transactions such as adding Passkeys or one time password. This reduces the risk of unauthorized signing and protects you from account takeover and malware-triggered approvals.

Turn it on/off in Account → Security

Below you can also check a list of minor improvements and bug fixes we have solved over the week.

Improvements

• Backend: Add start_time and end_time query param filters to /vaults/investments so you can pull period-specific information.

• Backend: Generated timestamps now use the last safe/known value to avoid gaps in charts and exports when upstream data is delayed

• Backend: Include icon in fund assets in FTaaS endpoint so UIs can display branded asset visuals without extra lookups

• Product Design: We have completed the new designs for the expansion of our staking service to other blockchain networks. This includes new branding assets, new landing page and the addition of a multichain concept in our staking service front end.

• Online shop: We have completed the new page design for the creation of an online shop featuring Starke Finance merchandise. To be enabled after the release of the public beta (H2 2026)

Fixes

• Bug: API endpoint that simulates shares to be received now returns accurate values after fees and rounding

• Bug: Fixed get starke config endpoint to reliably return the correct configuration payload across environments

• Bug: Historic asset holdings synchronization resumes correctly so portfolio charts and totals reflect the full backfill

Historic Fund Holdings

View historic fund holdings has been implemented in our sandpit environment. So you can track portfolio composition over time and explain performance to stakeholders. See position weights and quantities at any past date, compare changes across periods, and understand how inflows, outflows, and market moves affect each Fund. This brings transparency on the portfolio management strategy taken and helps you answer questions about exposure and risk with confidence.

Check the below design screenshot as demonstration of how the end feature will looks like.

FTaaS API documentation in GitBook

Remember that FTaaS is a service that can be consumed in two ways.

As a Fund Manager, you can create a Fund Manager account on our platform to manage your own Managed Funds. In parallel, FTaaS also provides an API, allowing third-party asset managers to consume our IT backend stack, including the data indexer and blockchain logic through our internally developed and now open sourced Solana program.

This API is designed to reduce friction when adopting blockchain-based products within your organization. Browse our API documentation on GitBook, and feel free to contact us with any questions or feedback.

Open-source Starke Vaults Program

You can now access the Starke Vaults Solana program as open source in GitHub. Use the same on-chain contracts we run in production to create, manage, and settle tokenized vaults on Solana. This gives you transparency, contributes to the Solana ecosystem and makes it easier to meet compliance and security reviews across your organization.

Remember that our Solana program is intended to cover most of the global use cases to manage multi asset vaults in compliance with the SEC requirements. You will find out, transferability restrictions, token and user whitelistings methods, maximum and minumim deposits etc. Also the first version was already audited by our partner security firm Kudelski Security (Starke Finance Trust Center), however we are planning new changes for additional features.

Improvements

• Backend: POST /vaults endpoint moved from legacy SDK to new FTaaS API endpoint.

Fixes

• Bug: Stabilized API under load to eliminate CPU spikes and crash loops, so requests complete reliably during traffic surges

• Bug: Redeem now returns the correct deposit token to the investor when fund tokens are burned, restoring a complete redemption flow.

• Bug: Sorting on the vault investors endpoint applies correctly, returning results in the requested order.

New Landing Page

Explore a refreshed landing experience that presents our style and a presentation of our upcoming Managed Funds, what will be the core of our Products.

In the new Landing page you will also get clear pathways to staking, fund overviews, ecosystem and documentation, supported by fast load times and accessible design across devices. The page reflects institutional standards while welcoming crypto-native users.

Visit starke.finance to see it in action.

Starke Staking Service

Stake natively or via liquid staking into the Starke Finance Validator with intuitive user experience and transparency including estimated yields, network costs and current market condition. Connect your wallet or chose our embedded Starke Wallet (powered by Dynamic), choose stake type and track positions from a unified view. The flow is non-custodial and designed to keep you informed at each step.

You earn yield while keeping flexibility that matches your strategy.

Dashboard

We have introduced a preliminary version of the main dashboard of our platform. It includes several sections, such as a summarized view of your portfolio—later expandable into a more detailed and comprehensive view—as well as the performance of individual assets, ETFs, and Starke Funds.

You’ll also find a quick overview that can be skipped at any time by using the intuitive left-hand menu we’ve prepared for you. From there, you’ll be able to navigate across all platform sections, including those that are still under development.

Production Improvements

• Authentication: User accounts experience with embedded wallets to simplify sign-in and reduce context switching

• FrontEnd: Multiple wallet syncing for whitelist to simplify compliance for multi-wallet users

• Frontend: Migrate market data display from Jupiter to Birdeye for fresher prices

• Frontend: Show network and protocol costs before confirming native or liquid staking.

• Frontend: Embedded wallet migration to Dynamic v3.

Production Fixes

• Frontend: Sidebar polishing for clearer icons, spacing, and states

Development progress

• Authentication: User flow design and deployment in sandpit environment of the KYC and KYB required to streamline compliant onboarding.

• Backend: Whitelist API endpoints for admin actions so approved staff can manage tokens, users, and managers securely

• Backend: Include token info across deposit, swap, Jupiter swap-to-deposit, and withdraw operations for clearer confirmations

• Backend: Close Fund capability to stop new deposits while keeping redemptions and reporting available

• Backend: Vaults endpoint adjustments to align with updated portfolio and pricing models

• Backend: Index liquid transactions for faster queries and accurate position histories

• Backend: Max deposit limits per fund to control inflows

• Backend: Refactor GET /v1/api/vaults/vtoken_prices for accuracy and lower latency

• Backend: Refactor POST /v1/api/vaults/{vault_id}/vtoken_price/history for clean, consistent charts

• Backend: Vtoken number of holders over time for investor growth signals

• Backend: Fund inflows/outflows over time to monitor momentum

• Backend: Fund AUM over time for trend analysis

• Backend: Vtoken supply over time to understand dilution and growth

• Backend: Vaults API estimate shares endpoint so you can preview expected shares before depositing

• Backend: Vaults Admin GET & DELETE for whitelisted tokens, users, and managers to keep lists current

• Backend: Vaults API GET deposit/redeem transaction fee to see estimated costs before submitting

• Backend: GET portfolio holdings diversity overtime endpoint to visualize historic fund holdings managementrisk

• Backend: Vaults Admin GET Starke Config for transparent environment and parameter checks

• Backend: Refactor GET /v1/api/vaults/{vault_id}/assets for consistency and pagination

• Backend: Refactor POST /v1/api/vaults/{vault_id}/investors/count_history for reliable investor charts

• Backend: Refactor GET /v1/api/vaults/{vault_id} for a unified detail response

• Backend: Refactor POST /v1/api/vaults/{vault_id}/assets/history to improve data fidelity

• Backend: Deposit transactions for Funds in sandpit environment complete reliably without intermittent failures

• Backend: GET /whitelisted-users and /whitelisted-managers endpoints return correct results

• Backend: POST /whitelist-token and /remove-whitelisted-token operate as expected

• Backend: Vaults Admin POST Pause/Resume Starke endpoints function correctly

• Backend: Refactor POST /v1/api/vaults/{vault_id}/vtoken_volatility/history for consistent volatility histories

• Backend: Refactor POST /v1/api/vaults/{vault_id}/metadata to standardize fund metadata updates

• Backend: Refactor GET /v1/api/vaults/{vault_id}/transactions with filters and performance improvements

• Frontend: Creation of admin panel to unify common operational tasks such as dashboard visualization, token whitelisting and visualization in Explore section.

• Marketing: Gift box preparation for partners and investors.

• Design: New landing page for users designed in Figma to improve conversion coming from ads

• Design: Dedicated rkPool fund page designed in Figma