How hylo-so/sdk works
Project type and purpose
• This is a Rust SDK monorepo for the “Hylo” protocol on Solana.
• It ships as four distinct crates:
• hylo-core: core data types, math, utilities
• hylo-idl: IDL definitions and helpers for on‐chain programs
• hylo-clients: RPC client wrappers for interacting with Hylo programs
• hylo-jupiter: integration layer with the Jupiter swap aggregator
• Build and maintenance scripts live under bin/ and the repo is managed via Cargo + Nix Flakes.
File structure
• Top‐level: project‐wide configs (Cargo.toml, flake.nix, CI workflows, bin scripts).
• Four sibling subdirectories, each a Cargo crate with its own Cargo.toml and src/.
• Scripts in bin/ orchestrate linting, building, version checks, publishing.
• No “frontend” or “database” directories—this is a library SDK, not an application.
README for additional insights
• Confirms the four crates and their responsibilities.
• No runtime services or UIs—this is a set of reusable libraries.
Final advice
• Be exhaustive: represent all four crates plus the build environment and external systems.
• Both compile-time dependencies (crate layering) and runtime flows (RPC & API calls).
• Keep labels concise but specific (e.g., “hylo-clients: Solana RPC client”).