We Don't Transfer Crypto. We Transfer Private Keys.
Every cross-chain transaction in crypto today makes the same trade-off: to move an asset from one blockchain to another, something has to give up control of it first. A bridge locks it in a contract. A custodian holds it on your behalf. A wrapped token stands in for it, backed by a promise that the real thing is sitting somewhere safe.
That trade-off has cost the industry billions of dollars in exploited bridges and compromised custodians, not because the idea of cross-chain movement is flawed, but because moving the asset itself was never the only way to do it.
Crypto Processor takes a different position: don't move the asset. Move who controls it.
The problem with moving assets
Look at how most interoperability solutions work today, and you'll find the same pattern underneath different branding. An asset gets locked on its home chain, and a synthetic version gets minted somewhere else, wrapped BTC on Ethereum, a bridged token on a rollup, a custodial IOU on an exchange. The synthetic version is only as trustworthy as whatever holds the original, and that "whatever" is usually a single contract, a small federated multisig, or a company.
That's precisely why bridges have become the most exploited category of infrastructure in crypto history. A single compromised validator set or a single bug in a lock contract puts the entire pool at risk, because control of the underlying asset was concentrated in one place to begin with.
Bitcoin makes this problem more visible than anywhere else. It's the largest asset in the industry by a wide margin, yet it holds a tiny fraction of the market's DeFi liquidity, largely because the only way to bring native BTC into DeFi has been to wrap it, bridge it, or hand it to a custodian. Billions of dollars in BTC sit idle, earning nothing, because every path into DeFi has required giving up the thing that made Bitcoin worth holding in the first place: sole control over the asset.
A different question
Instead of asking "how do we move this asset to where it's needed?", the PoKO Protocol (Proof of Key Ownership) asks a different question: "who needs to control this asset right now, and can we change that without moving anything?"
That distinction sounds subtle, but it changes the entire security model. Here's what actually happens when an asset moves through Crypto Processor:
- The asset is deposited into a Locked Wallet on its native chain, for Bitcoin, that means it never leaves the Bitcoin blockchain. This wallet is non-custodial: no single party, including Crypto Processor, holds the key that controls it.
- The wallet's key is generated through Distributed Key Generation (DKG). No dealer, node, or coordinator ever assembles the full private key, not during creation, not ever. Each participating node in the decentralized MPC network independently computes a fragment of the key, and the complete key simply never exists in one place to be stolen.
- An Ownership Certificate is issued, representing control over the Locked Wallet's contents. This certificate, not the underlying BTC, is what moves when ownership changes hands.
- Transferring the certificate triggers a key rotation. The MPC network redistributes the control shares to the new owner through a cryptographically verified process. The Bitcoin in the Locked Wallet does not move, and no transaction touches the Bitcoin blockchain at all during this step.
- The current certificate holder can redeem it at any time, triggering the final signing operation that releases full, native control of the underlying asset, the same BTC that went in, on the same chain it's always been on.
Every operation that requires signing needs a threshold of independent nodes to cooperate, a Threshold Signature Scheme (TSS) enforced on top of the DKG-generated shares. A single compromised node, or even a large minority of malicious nodes, cannot authorize a transaction on its own. There is no lock contract to exploit, no bridge validator set to bribe, and no wrapped token whose peg can break, because there is no wrapped token at all.
What this actually unlocks
The mechanism matters because of what it enables. Native BTC ownership can now move through an EVM-compatible environment at a completely different performance profile than Bitcoin's base layer was ever designed for:
| Bitcoin L1 | Crypto Processor | |
|---|---|---|
| Throughput | ~7 TPS | ~7,000 TPS |
| Fee | $5–$20 | ~$0.01 |
| Finality | ~3,600 seconds | Near-instant |
| Smart contracts | None | Full EVM |
That gap is not a discount on the same thing, it's a structural difference. A standard Bitcoin transfer requires broadcasting to the Bitcoin network and waiting on block confirmation every time value changes hands. Under the PoKO Protocol, only the initial deposit into a Locked Wallet ever touches Bitcoin's base layer. Every subsequent change of ownership is a key-rotation event on Crypto Processor's own Proof-of-Stake chain, closer in cost and speed to any modern L1 than to Bitcoin settlement.
This is the foundation of what we call the BTC EVM Machine: native Bitcoin, finally able to participate in lending, liquidity pools, staking, and every other DeFi primitive that Ethereum-based assets have had for years, without ever becoming a synthetic version of itself.
Built to keep working
One more design choice is worth calling out directly, because it's the question every serious user should ask of any key-management system: what happens to the architecture over time, as the threats it defends against evolve?
Most wallet and bridge security today rests on the assumption that deriving a private key from a public key is computationally infeasible, an assumption that holds against classical computers but is not guaranteed to hold forever against quantum ones. Crypto Processor's architecture was deliberately built without a hard dependency on any single consensus mechanism or protocol upgrade path, so that post-quantum-resistant primitives can be adopted as they mature, rather than requiring the network to be redesigned from the ground up when that day arrives.
We're not claiming that quantum computers capable of breaking current cryptography exist today. We're building so that when the timeline changes, Crypto Processor isn't the one starting from scratch.
Where this goes next
The PoKO Protocol is live in the Simulator today, where you can watch a native BTC transfer move through Locked Wallets, Ownership Certificates, and key rotation without wrapping, bridging, or a middleman in sight. Testnet and node integration are the next milestones on the roadmap, moving toward public alpha and beta as the network matures.
If you want the deeper technical version of everything above, the specific cryptographic schemes we evaluated (Shamir's Secret Sharing, Verifiable and Publicly Verifiable Secret Sharing, and why we landed on DKG combined with TSS), the full MPC wallet architecture, and the research behind it, that's all documented in our Research docs.
We don't transfer crypto. We transfer private keys. Everything else follows from that one sentence.