What's Next For Solomon?
What’s Next for Solomon
The ICO is done, but Solomon isn’t “launching from zero.”
We’ve been running in private beta for the past year: the basis engine is live, the Solana programs are live, real users are onchain, and seven-figure TVL is already earning yield.
The system works. The raise wasn’t to fund a prototype, it was to scale something that’s already real.
Scaling is where things break if you rush. So this next phase is about taking a deliberate lap: hardening the rails, tightening controls, and cleaning up the rough edges before we invite everyone in. One of the clearest pieces of feedback we got was on UI/UX, it works, but it’s nowhere near the level of polish we want for showtime. That’s getting a full refresh.
At the same time, we’re not going into a bunker. We’re widening the beta while we do this work. Beta access sign-up is now live directly on the home page, and we’ll be onboarding more wallets, LPs, treasuries, and protocols into USDv and YaaS under guardrails. As the infrastructure is hardened and the surface is rebuilt, more cohorts will come online and the system will keep compounding in the background.
Here’s what happens next.
1. MetaDAO proposal and treasury deployment
As detailed in our ICO blog post, the first step is turning idle USDC in the MetaDAO treasury into USDv under clear rules.
We’ll put forward a MetaDAO proposal that:
Encodes a Squads VaultTransaction instruction that:
Converts the funds raised into USDv directly via the Vault Program.
Deploys this into core DEX liquidity for USDv pairs.
The USDv and LP positions created from this process will remain under direct DAO treasury control, with full transparency into their location and deployment strategy.
2. Audits & controls
Our current onchain programs are audited by zigtur and have been live in beta, but we want another layer of checks before we scale beyond early users.
Audits
Commission additional review of the USDv / sUSDv, vault, and stake programs with fresh eyes.
Launch a public bug bounty so independent researchers can continuously test and harden the system.
Controls
Add (or lengthen) timelocks on critical programs where feasible.
Review and clearly document all roles associated with the programs.
Ensure the Program Authority is separate from any admin role and subject to a longer timelock.
3. Product: UI/UX and YaaS interface
The beta UI/UX met the needs of early users, but it isn’t the standard we want for a public launch. For broader scale, the interface needs to be clearer, easier to navigate, and more refined visually. The product surface is therefore one of the core areas receiving a full end-to-end refresh in this next phase.
UI/UX refresh
Near full overhaul of the main app experience: minting, staking, stats, and program status.
YaaS interface
The current beta is focused on core protocol functionality. The YaaS interface is the next step – the surface where liquidity actually plugs in.
We’re building a dashboard where users and protocols can:
Connect a wallet and sign in.
Detect supported USDv positions (LP tokens, balances, treasuries).
Prove ownership and satisfy onboarding requirements.
Manage yield delegation addresses (same wallet or designated treasury wallets).
End-to-end yield telemetry showing real-time streams, history, and attribution.
YaaS is the critical layer in Solomon’s design, the piece that routes yield to where USDv lives. We’re building an interface that matches its importance.
4. Dashboards and proof of reserves
Backers and integrators should have direct, ongoing visibility. The current dashboard is already better than what most offer, but we want to set a higher bar.
We’ll improve:
Public dashboards that show:
USDv and sUSDv supply.
High-level backing breakdown (venues, assets, T-bill share).
Historical and current realized yield from the basis engine.
Clear breakdown of collateral yield APY vs effective realized yield to holders.
Third-party proof of reserves, by:
Integrating with independent custody providers to attest to assets at custodians and exchanges.
Reconciling those attestations against USDv liabilities on-chain.
Participating in ecosystem-led initiatives like the Blockworks Token Transparency Framework and similar efforts.
5. Infrastructure expansion and institutional integrations
The size of the raise means we have to think institutionally from day one.
Our backend is already built with modular, asynchronous components and full event replay so we can scale each piece independently and keep a complete audit trail. Here’s what we’ll be doing.
Near-term priorities
Venues / CEXs and custody
Integrate additional custody providers.
Onboard and connect to more CEXs and perp venues for the basis engine.
T-bills
Complete onboarding with issuers and qualified custodians.
Redundancy and transparency
Expand existing failover capabilities, distributed messaging, and security controls for continuous uptime.
Implement third-party auditable trade reporting and position tracking as part of our transparency stack
6. Legal and compliance
We’ll be:
Finalizing issuing and operating entities and clearly defining their roles.
Publishing clear disclosures on:
How USDv is backed.
How yield is generated (basis + T-bills).
Where the main risks sit (venue, strategy, program, oracles).
How this all comes together
All of the work above will move in parallel. Different pieces will land at different times, but they all push toward the same goal: making USDv the primary Solana-native stablecoin and the default dollar rail for the ecosystem.
On the team side, we’re interviewing for an additional full-stack engineer to increase our shipping capacity while keeping the group small and focused.
Everything so far has been a test of execution: getting the engine live, running a year of private beta, and now closing the raise. The ICO was a big step, but still a step — it gave us the capital and the backers who share the same conviction. Thousands of people are now directly aligned around a simple idea: better dollar infrastructure on Solana, owned by the people who rely on it.
The next phase is about proving that out in production: more integrations, more USDv circulating, and more yield routed through YaaS under the guardrails we’ve outlined here.
We’ll share concrete updates as each piece lands. In the meantime, the door is open: the beta access form is live on the home page.
 | A guest post by
|