Work / TEKHQS / 2025 — Present
In-house product
RYT Chain
In-house Layer-1 protocol
An in-house TEKHQS Layer-1, led as architecture and engineering at TEKHQS — not a personally owned chain. Public product at ryt.io, positioned as a gas-free, EVM-compatible chain for institutional and civic rails.
The system
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.
The 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 developed at TEKHQS. Protocol architecture and engineering were led there. The public site is ryt.io.
Role
Architecture Owner & Engineering Lead at TEKHQS.
What I architected
- 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.
Engineering decisions
- Treat the chain as an operational product, not a public-L1 clone with different branding.
- Keep consensus, validator, and deployment internals off the public record.
Result
Production in-house L1 at TEKHQS. Public product: ryt.io.
Infrastructure
Production in-house chain. Public product surface at ryt.io. Node, validator, and deployment internals stay off this site.
Stack
Protocol engineering · Distributed systems · EVM
Evidence / Availability
In-house TEKHQS product. Public product surface at ryt.io. Protocol internals are intentionally limited.
- Public product site: ryt.io.