About
Nukez was built for one reason.
“Autonomous agents need infrastructure engineered for their unique capabilities — not just another storage API. Nukez is designed from first principles for agents that pay, store, retrieve, and prove with zero human in the loop.”
Founder Profile
Nukez is the work of a single full-stack engineer with over eight years of zero-to-one production work. An expansive, multi-disciplinary body of knowledge — institutional real-estate valuation, geospatial machine learning, CFO/CTO of a family office, then Solana cryptography — built from first principles and refined through real-world application.
The path that led here is unusual on purpose:
- Hanson Real Estate Advisors (2010–2018) — Lead associate on a $1.16B Amazon HQ campus disposition, a $1.94B CMBS restructuring, a $78.4M foreclosure judgment engagement, and 3,000+ ATM rent models for Cardtronics v. Florida DOR. DCF and NPV across 57 Florida counties and Seattle. This is where I learned to be right to four decimal places under adversarial review.
- Crews Groves, CFO / CTO (2018–2023) — Led a $40M phosphate-mining option negotiation with The Mosaic Company across ~1,357 acres, with a parallel Duke Energy solar lease used as deal leverage. Built geospatial pipelines in QGIS and Python to model parcel-level reserves and create asymmetric information advantage. This is where I learned to ship code against people who would notice.
- Independent Solana work (2025) — Real-time on-chain transfer monitor with Unicode-spoof defense. Forensic demand analytics for the Switchboard ecosystem. A Jito-bundle rescue system deployed in three days under an active private-key compromise — atomic fund-then-sweep, WebSocket sentinel, tip escalation against the attacker's automated drain. secp256k1 implemented from scratch — field arithmetic, point ops, ECDSA, deterministic k. This is where I learned the actual mechanics of the chain Nukez runs on.
- Nukez (2025–present) — Sole architect, engineer, and operator. Permissionless gateway with dual-chain rails (Solana / EVM-Monad). Signed-envelope authentication that eliminates whole categories of vulnerability — sessions, replay, fixation. Merkle attestation pipeline anchored through an independent Switchboard oracle, so the platform is architecturally excluded from its own trust chain. Multi-tier agent service holding flat context growth (~3,450 tokens/call across 41-message sessions, zero byte leaks). Passwordless portal, Python SDK, and MCP server — all shipped solo, observability and deployment owned end-to-end.
Education: M.S. Applied Economics coursework, Johns Hopkins (2017–2019). B.B.A., University of Florida — Warrington (2005–2009).
§ thesis
Three paragraphs.
One. The economic unit of the next decade is not a SaaS seat — it is an autonomous agent with its own wallet, its own memory, and its own accounting. The infrastructure for that agent exists in pieces — MCP, Solana, vector stores, cloud storage. Nobody has fused the pieces into something an agent can actually verify on its own.
Two. The specific fusion that matters is storage × attestation × on-chain anchor. Storage is a commodity; attestation is the differentiator; the on-chain anchor is what makes verification independent of us. Get those three to fit and you have an artifact no central party can tamper with.
Three. Adoption for this kind of infrastructure is event-driven, not marketing-driven. Someone's agent will hallucinate itself into a liability event, or someone will discover that their LLM platform has been silently eating 30% of their outbound tokens on a base64 tax. At that moment, the question stops being “do we need this?” and becomes “can we afford not to have it?”.
§ stage & traction
Live · April 2026
Full protocol live on Solana + Monad · mainnet. Switchboard attestation running. Pricing matrix exposed per provider.
Python · v0.7
PyPI nukez 0.7.2. Async client, four framework adapters, MCP server bundled.
§ on authorship
This site is hand-coded. The illustrations, the circuit-trace, the type decisions, the copy — all authored. AI tooling was used for code autocomplete and draft iterations; nothing on the site was generated end-to-end. When the full frontend is committed to a public Nukez locker, the URL will appear here — verifiable, like everything else.