[ DOCS ]
What Lockey is specified to do, written down before it is built. This page uses native scrolling — no smooth-scroll layer, so in-page anchors and find-in-page behave normally.
Lockey moves supported assets from public state into private state, performs supported actions privately, and returns them to public settlement when the holder chooses.
These pages document the product model as it is specified today. They are concept documentation, not an API reference: there is no SDK, no deployed contract and no endpoint to call yet.
Every module is expressed through the same five phases: Shield, Private State, Private Transfer, Unshield, Disclose. A module that cannot be expressed in those phases does not belong in Lockey.
The lifecycle is described phase by phase, including what each phase makes public, on the Method page.
Read the method →Robinhood Chain is the primary programmable settlement environment. Public verification happens there; private state is kept off the public record and proven rather than published.
No settlement integration is live. Nothing described here has been deployed to a mainnet.
The intended signature primitive proves that a private action is valid — sufficient balance, policy compliance — without revealing the exact balance or the policy detail behind it.
The circuit, prover and verifier for this proof are not written. Treat the description as a specification, not a capability.
Viewing authority and spending authority are separate concerns. A disclosure lets a chosen party read a specific statement about activity; it never grants the ability to move funds.
Key derivation, scoping and revocation are unresolved and tracked as roadmap work.
Viewing Key module →Browser automation is treated as an external web interaction adapter. Lockey keeps private context, redaction, policy, proof generation, signing boundaries and settlement on its own side of the boundary.
Wallet private keys and Zcash spending keys are never handed to a browser automation session or a cloud browser.
Trust boundaries →A Next.js marketing and concept surface, a written architecture, and a phase-by-phase build plan. That is the honest extent of it.
The Status page lists what is built, what is specified and what is untouched.
Build status →