I just released the first major version of Hyperliquid's only Ruby SDK. It features implementations for Hyperliquid's Info and Exchange APIs, as well as WebSockets for real time streaming.

I wrote the vast majority of the code with Claude Code. Having previously spent most of my time in Cursor, I was extremely impressed with CC. It’s clear to me now that Claude Code is the leader in LLM coding tools.

What I found most interesting while developing the SDK was the WebSockets implementation. I’d never worked with WebSockets before, so directly interacting with them and exposing a clean interface to Hyperliquid’s WS endpoints was new and exciting. I initially used an existing gem, ruby-jp/websocket-client-simple, but it fell short in configurability and had several open issues that were breaking parts of my WS functionality. In response, I built ws_lite, a fork of websocket-client-simple that’s more flexible, more reliable, and avoids several SSL-related issues I ran into.

The motivation for building the SDK comes directly from what I'm working on next. Over the past year I've spent a lot of time delving into Concentrated Liquidity Pools. Depending on market conditions, I'll hedge those positions by shorting each asset in the pool (easily done on Hyperliquid). The issue is that the distribution of your assets don't stay fixed in the pool: as prices move, the asset composition shifts, and hedges can drift into being over or under exposed.

I aim to build an automatic short rebalancer that tracks a CLP position and adjusts hedges accordingly. I'm thinking of either a ruby daemon running on my homelab or a Rails-based dashboard so I can peek at a UI wherever I am.