§1 — The brief.
The brief.
Alien is decentralized identity infrastructure for the agentic economy. Alien ID establishes proof of unique humanity through the Continuous Human Verification Protocol (CHVP) — biometric verification on-device, decentralized oracles, and social graph signals. Agent ID is the corresponding credential for AI agents, anchored back to a verified human's reputation from day one. The system runs on Alien's L1 chain, with deployments extending to Solana.
Alien's founder team has the protocol thesis and the application surface. The engagement we run is embedded engineering inside Alien's dev team, under Alien's CTO. Our scope spans the chain protocol layer, Solana deployment, bridging between the two chains, node infrastructure, DevOps, and design contributions to the Agent ID system itself.
§2 — What we shipped.
What we shipped.
[01]
Protocol layer · Alien L1 chain
─ CHAIN ENGINEERING
[02]
Solana deployment · cross-chain consistency
─ MULTI-CHAIN
[03]
Alien ↔ Solana bridge · messaging + assets
─ BRIDGE LAYER
[04]
Node infrastructure · monitoring · upgrades
─ OPERATIONS
[05]
DevOps · build pipelines · environments
─ OPERATIONS
[06]
Agent ID credential design contribution
─ PROTOCOL DESIGN
The protocol-layer work is chain engineering inside Alien's L1 — alongside Alien's CTO and core dev team. The Solana deployment keeps state consistent between the two chains. Bridging is design and implementation of messaging and asset bridging between Alien L1 and Solana.
The Agent ID design contribution is the credential structure, the human-anchoring mechanism, and the verification flow that lets external services confirm an agent acting on a request is tied to a verified, accountable human.
§3 — Engineering decisions.
Engineering decisions.
Multi-chain from the start, not after.
Alien's identity system has utility on the chain that hosts the protocol and on the chains where agents and users actually transact. Alien chain + Solana isn't a post-launch expansion — it's the deployment topology from day one. The bridge between them is part of the protocol's design, not infrastructure bolted on later.
Agent ID as credential, not as identifier.
The point of Agent ID isn't naming agents for their own sake. It's binding agents to accountable humans so external services can verify the human chain of accountability behind any agent action. Design contributions held this line: the credential structure exists to anchor agents to humans, not to build a parallel agent reputation system that floats free of human accountability.
Embedded over outstaff for protocol-layer work.
For chain protocol work where design decisions and implementation are entangled — Alien is one such case — embedded engagement under the client's CTO produces faster decisions than outstaff-with-its-own-lead. The client's CTO is the architectural authority. Zpoken's seniority adds depth to the bench, not parallel command.
§4 — Where it stands.
Where it stands.
The Alien L1, Solana deployment, bridging, infrastructure, and Agent ID workstreams are active and continuing.
§5 — Tech stack.
Tech stack.
~/zpoken/work/alien/stack
Alien L1 (chain protocol layer) · Solana (cross-chain deployment) · Cross-chain bridge infrastructure · Node infrastructure tooling · DevOps / CI / deployment automation · Agent ID credential design
§6 — Public surface.
Public surface.
§7 — Founders.
Founders.
Engagement led by Mike Yezhov and Anton Yezhov, working alongside Alien's CTO and dev team.