Case Study
Horizon Protocol
Starknet yield tokenization protocol with SY/PT/YT assets, AMM markets, router flows, frontend, and indexer.
- Cairo
- Starknet
- TypeScript
- Next.js
- Apibara
- PostgreSQL
Overview
Horizon Protocol is a Pendle-style yield tokenization protocol for Starknet. It separates yield-bearing assets into standardized yield, principal, and yield tokens, with AMM markets, factories, router operations, oracle integration, contracts, frontend, and indexer pieces.
Problem
Yield tokenization needs protocol contracts, market creation, routing, oracle-aware pricing, frontend flows, and indexed data to stay aligned. Each layer has to expose enough detail for advanced DeFi users without creating unsafe or confusing product paths.
My role
I built across the protocol, frontend, and indexing surfaces, connecting Cairo contracts, TypeScript product flows, and data infrastructure into a live alpha.
Technical details
- Implemented Starknet protocol pieces for standardized yield, principal, and yield token flows.
- Built product and router flows around markets, factories, AMM interactions, and documented deployed addresses.
- Connected a Next.js frontend and Bun-based Apibara indexer with PostgreSQL-backed data workflows.
Hard parts and tradeoffs
- Alpha DeFi infrastructure needs clear current-state language because live contracts are useful evidence but do not imply a completed risk or audit posture.
- The protocol surface has to balance composable contract primitives with a frontend that makes tokenized yield operations legible.
Current state
The repository documents an alpha mainnet deployment on Starknet Mainnet, and the SplitYield product is publicly reachable.