Work / TEKHQS / 2025 — Present
RYT Chain
The in-house Layer-1 I lead at TEKHQS. Public product at ryt.io — positioned as a gas-free, EVM-compatible chain for institutional and civic rails. I own protocol architecture and the engineering that ships it.
Problem
Enterprise and civic chains fail when they are reskins of public L1 folklore. The job is execution, permissioning, and operational control under real adoption constraints — including mobile-first use.
Context
In-house product at TEKHQS. I lead the chain. The public site is ryt.io.
Role
Architecture owner and engineering lead.
Architecture
In-house Layer-1 aimed at institutional and civic rails, with EVM compatibility and a natively gas-free product posture. Consensus internals, validator topology, and client implementation details are not published here.
Infrastructure
Production in-house chain. Public product surface at ryt.io. Node, validator, and deployment internals stay off this site.
Engineering
- Own protocol architecture for RYT Chain.
- Lead the engineering team that builds and ships the chain.
- Align wallet, identity, and interoperability work with the chain's constraints.
Result
Production in-house L1. Public product: ryt.io. This page does not copy marketing TPS figures as personal metrics.
Stack
Protocol engineering · Distributed systems · EVM
Evidence
- Public product site: ryt.io.
- Resume: RYT Chain as a flagship TEKHQS platform, production delivery in 2025.
Review / Not invented
These details are not in the source materials, so they are not claimed:
- Public chain spec, execution environment, and validator topology — pending approval.