I'm an engineer who likes taking a product from an idea to something people can use. My work spans backend systems, interfaces, and tools I've built for myself.
At Avail, I own the backend service behind ShieldTX, coordinating private trades from a request in the app through to completion. I also built the initial SDK and installable UI for Nexus, which helps applications move assets across chains.
Away from work, my attention rotates between my , video games, playing my guitar, and whatever Real Madrid are doing that week. and fill most of the gaps; gadgets fill most of the desk.
A few products and systems I’ve built, from solo tools to privacy infrastructure.
Product, design, engineering · Archived
An AI writing tool I built to draft X posts in my own voice, then launched as a product. I owned the design and engineering, including the web app and browser extension. The product is retired and its backend is offline. Chrome Web Store listing.
Backend systems
Private trading on Hyperliquid. My work focuses on coordinating services and recovering interrupted trades, with tools to understand what happened and what needs attention.
A private trade depends on several services agreeing on what has happened. Keeping that coordination in the frontend made the app responsible for too much, especially when a request was interrupted or an external service responded late.
I proposed moving third-party coordination behind a dedicated backend boundary, designed the layer, and built its first implementation. That gave the frontend one API for trading workflows while the backend coordinated the work between services.
I lead the backend work and build it with the team. My ongoing work covers trading workflows, live market connections, recovery, and tools that help us understand interrupted operations. Testing and user feedback feed back into how those workflows behave.
SDK and UI
Brings balances held across chains together. I separated the UI from the SDK so integration teams could install, own, and customize the components in their own codebases.
Applications needed to bring balances across chains into one flow. I built the initial SDK and UI, but packaging them together limited how teams could customize the interface and added unnecessary package weight.
I separated the headless SDK from the UI and rebuilt the interface as shadcn components installed through a registry. The SDK handled the transaction logic; integration teams could edit the UI source in their own projects.
I built and maintained the Elements distribution site and registry integration, with bridge, swap, and swap-and-execute flows. Teams could use the SDK with their own interface or start with the installable components and adapt them.
Open source
An open-source tool that turns public X posts and articles into clean Markdown, text, or JSON for people and agents.
View source ↗macOS app
A native macOS companion for T3 Code that shows agent activity and context usage around the notch. It is still in active development.
View source ↗AI is part of how I build. I use agents to explore ideas, write code, and review changes so I can move quickly from idea to working software.
2,471 contributions in the last year
Python was the first language I learned. One of the first programs I wrote was an anagram generator. It combined code + secure and produced decocereus. I thought that was cool, and it has been my username ever since.