Skip to main content
Hyro Protocol is a modular system: a small on-chain core, two pluggable on-chain layers, and an off-chain execution + oracle stack that writes results back to Solana.

​
The stack

LayerTechnology
BlockchainSolana
Smart contract frameworkAnchor 0.31.1
FrontendNext.js + TypeScript
Oracle transportNATS with JetStream
Client SDK generationCodama (from Anchor IDLs)
Off-chain venue integrationCCXT (Bybit live; others in progress)
Off-chain engineRust (HyroTrader core engine)
Wallet — pro usersPhantom (self-custody)
Wallet — retailEmbedded (email signup, auto-generated Solana wallet via Privy / Dynamic)
Settlement currencyUSDC (SPL)
GasSponsored by Hyro — users never need SOL
AuditAckee Blockchain

​
The dual-wallet UX

Email-based account creation produces a Solana wallet automatically — no extension, removing onboarding friction for retail traders coming from CeFi. Sophisticated managers use Phantom for full self-custody. Users can export keys or migrate to Phantom at any time. Gas sponsorship is a fractional-cent operational cost on Solana that meaningfully improves UX.

​
On-chain vs. off-chain

On-chain (Solana)

Vault state · authorization (policy programs) · fee calculation · share accounting · LP deposits/withdrawals · payout records · challenge-fee collection

Off-chain

Trade execution (Bybit order books) · the Rust risk engine · NAV computation, which the oracle writes back on-chain

​
How the layers connect

The core program (hyro_protocol) holds vault state and orchestrates two pluggable layers over CPI:
  1. Authorization — every privileged instruction issues a validate(ValidateOperation) CPI into the vault’s policy.
  2. Fee calculation — every fund movement issues a charge_fees CPI to the fee dispatcher, which delegates arithmetic to a calculator.
Neither is hard-coded. Each vault stores only the pubkeys of its policy_program and fee_collection_program, and both are swappable.

Program topology

How the on-chain programs connect, instruction by instruction.