I'm the founder of PhantomLayer. Before that, a decade running operations and reliability programs in industrial environments. The kind of work where failure has a dollar figure and a root cause, not a shrug. I worked my way through technical and senior leadership roles across oil and gas, automotive, and advanced manufacturing, and spent most of that time figuring out why systems break and how to stop them breaking the same way twice. I came to cryptography without a CS background. Just an operational habit of asking why something is built the way it is. The deeper I got into key exposure and custody risk, the clearer it became that authority and identity had been collapsed into the same artifact, and that the field had inherited that assumption without really choosing it. PhantomLayer is built on what happens when you reject it. The result is a commitment-based control model. Exposed authority eliminated as a structural dependency, not managed around.

PhantomLayer Rust SDK v0.2.0: type-enforced lifecycle state transitions across execute, rotate, and recover flows

Published whitepaper with formal specification

Five provisional patents filed

External cryptographic review: commitment model assessed sound, no fundamental design flaws identified

Two independent security reviews complete; all Critical and High findings resolved

If you're evaluating the SDK, the whitepaper and technical brief are the right starting point. Reach out directly.

Background MBA. Master's in AI for Business. Six Sigma certified. Previously founded and exited a small e-commerce company. Co-founded a crypto fintech SaaS. In crypto since 2017. Contact adam@phantomLayer.org