Research driving the Kentra Protocol product thesis
Four market failures that explain why Kentra Protocol uses distributed signing, passkey recovery, and privacy by design.
Compare custody models
Common Questions
Kentra Protocol combines a desktop client, co-signer service, recovery passkey, Robinhood Chain adapter, and open SDK in one threshold custody architecture.
Yes. The co-signer policy layer can enforce spending limits, velocity controls, session checks, and anomaly detection before a second signature is produced.
The desktop client signs with Shard A, the co-signer signs with Shard B after policy validation, and the partial signatures combine for settlement on Robinhood Chain.
If the desktop shard is lost, the recovery passkey and co-signer can rotate a new client shard without exposing a seed phrase.
No. Kentra Protocol holds only the co-signer shard and cannot move funds without the desktop client or recovery passkey.
Kentra Protocol is built first for Robinhood Chain, an Ethereum-compatible Layer 2 with ETH gas, ERC-4337 support, and chain ID 4663.
The roadmap moves from custody MVP and SDK launch to swaps, invisible setup, confidential activity, and multichain expansion.
Build private payments on Robinhood Chain
Read the research, explore the architecture, and follow the roadmap to native privacy.
