YUHAN HUANG Contact

I build with AI at the scale of a team, by myself.

I build and run a fleet of AI agents across five machines, and I point it at things people usually hire a team for: quant trading, a few thousand crypto nodes, and a token allocation I earned by actually trading on the platform. It's all one person.

What I've built

Every claim here is tagged so you can check it yourself: live, on-chain, or historical.

On-chain proof

I earned roughly 0.9% of Lighter's first airdrop

The tokens landed straight in the wallets that qualified, based on how much I actually traded. There was nothing to claim and no vesting schedule.

You can't fake this. It's on-chain: the wallet either qualified or it didn't. I'm leaving the dollar figure and token count off this page on purpose, but I'll walk you through the wallet and the numbers if you ask.

~0.9%

of Lighter's first airdrop, a 250M-LIT pool paid on-chain to the wallets that qualified.

5,000 verifier nodes in Docker, stood up solo

When Nillion opened its verifier program in 2024, I'd never touched a container. I learned Docker with AI as I went, and had the whole fleet running myself.

5,000+

verifier nodes in isolated Docker containers, on a Mac mini cluster I run at home.

I also write crypto how-tos and airdrop guides for a following of ~14K on X: @hank06171.

At 19 I incorporated a company

It's the legal home for this work. I set the whole thing up myself: the domain, the company email, the GitHub org, and the automations that keep it active day to day.

19

the age I registered it. Taiwan entity live; Hong Kong entity in formation.

墨克數位科技股份有限公司 · MKL Digital Technology Co., Ltd. · TW reg. 62201452, incorporated 2026-04-22. On the public Taiwan company registry.

Before Hermes: automation infrastructure built to run unattended

I designed the whole system myself: the isolation between environments, the state machines that tracked each one, and the batch logic that drove them all at once. Hundreds of environments, all behaving the same way, with no one watching.

That's the hard part. At that scale, one bad assumption cascades across everything. Getting it deterministic is what taught me the recovery engineering Hermes runs on now.

An 8-module framework I called Eclipse, across several protocols.

Historical

Hermes: my agent fleet, and it fixes itself when it breaks

Five machines running agents around the clock. When one freezes or crashes, the system notices and brings it back with no one watching. I built the orchestration and the recovery around the models. I didn't train a model.

40+

production failures turned into automatic recovery. One silent freeze that ran for hours now recovers on its own in about 100 seconds.

The parts that matter: a watchdog that restarts dead agents, jobs that survive a crash, auth that renews itself, memory shared across machines, and recovery from a frozen event loop.

Live now

Quant systems

Quant trading, built on top of the same fleet

A cross-exchange latency-arbitrage engine, written in Go. I did the strategy, the signal work, and the execution engine myself, all on my own Hermes fleet. The strategy didn't come from a book. I reverse-engineered it from public fill data on the exchanges.

The edge is in zero-fee pairs and rebate tiers, not the raw spread. I'm not publishing capital, returns, or win rate. It's a live system I run on my own money, not advice and not a managed account.

6

exchanges wired into one Go latency-arb engine, running live on my own fleet.

Live

Origin

How I got here

I went to 師大附中, one of Taiwan's top high schools. I taught myself most of the coursework with AI instead of sitting through it. I took a gap year and left two credits short of a diploma, because re-taking classes to hold onto a piece of paper was not worth the time. So I have a certificate of studies, not a graduation certificate.

The gap year is when I actually started building. I was already deep in crypto, running my own automation at scale. Once the coding models got good in 2024, I leaned on them hard: I taught myself Docker from zero and stood up a Nillion verifier fleet on my own, past 5,000 nodes.

Then I got into 清華大學 (NTHU) through the 拾穗 program, an admissions track that ignores standardized test scores and looks at your work and an interview.

They admitted me on my work, not a test score.

It's the same thing I did in high school, just bigger: use AI to build whatever I want, and don't half-do it. The agent fleet, the quant systems, the company all came out of that.

The Academy

What I want to do at the Academy

The way I work is AI-first: one person plus a fleet of agents, and crypto is where I put it to the test. On-chain there's no hiding. The trade either happened or it didn't, and the allocation either landed or it didn't. I've been working this way since high school.

Of the founding partners, my work lines up with Coinbase most directly. I've already built exchange systems, execution engines, and automation around on-chain incentives. I'm not looking to explore crypto as an application. I've been shipping it, with on-chain proof to show for it. Give me the $50,000+ in partner compute and my edge is turning it into systems that do the work of a whole team.

Most people here will be strong at one thing. I've got three that build on each other: the agent fleet I engineered, the allocation I earned on-chain, and the quant system running on top of both. All of it solo.

And I'm all in. If you take me, I leave 清華大學, move to San Francisco, and spend the year on this full-time. I've bet on work over credentials before, when I walked away from my diploma. I'll do it again.