One integration surface
Authentication, wallet state, recovery, and sponsorship share a consistent product-level API.
Architecture comparison
Choose the wallet model, not just the login modal.
Cavos is device-native and chain-agnostic: one product integration, with an explicit adapter for each blockchain. Compare that model with hosted key networks and traditional wallet extensions.
| Capability | Cavos | Hosted embedded wallets | Wallet extensions |
|---|---|---|---|
| Signing authority | A non-exportable device signer controlled by the user | Provider-specific key management or MPC model | A key managed in a separate wallet application |
| Chain strategy | One SDK with chain-native adapters | Network coverage and account model vary by provider | Coverage depends on the wallet and installed networks |
| Current Cavos coverage | Starknet, Solana, and Stellar | Varies by provider | Varies by wallet |
| User experience | Embedded directly in the product; no wallet extension | Embedded directly in the product | Users install, open, and approve in another application |
| Gas sponsorship | Chain-specific paymaster and relayer integrations | Varies by provider and network | Usually funded by the user or a separate paymaster |
| Recovery | Device authorization and non-custodial recovery factors | Provider-defined recovery | Seed phrase, passkey, or wallet-specific recovery |
Why the adapter model matters
Native where it counts
Address derivation, signatures, execution, and fees remain explicit and correct for each blockchain.
Built beyond three chains
New adapters can join the same interface without pretending every blockchain has the same account model.
Frequently asked
What makes Cavos different from hosted embedded wallets?
Cavos makes the user’s device the signing authority. The device key is non-exportable, Cavos does not reconstruct it with MPC, and each chain adapter uses the chain’s native account and transaction model.
Which blockchains does Cavos support?
Cavos currently ships adapters for Starknet, Solana, and Stellar. The SDK is designed around a chain-adapter interface so additional blockchains can be added without changing the product-level integration model.
Does Cavos use MPC?
No. Cavos does not split or reconstruct a master key with MPC. Signing authority stays with device-bound keys or the chain-specific non-custodial control model documented for each adapter.
Can one application use Cavos across multiple chains?
Yes. Applications use the same Cavos.connect entry point and select a chain and network. The returned wallet is a typed, chain-specific object so native transaction behavior stays explicit.
Build the first wallet on your target chain.
Start with the unified SDK, then follow the native guide for each adapter.