Openclaw Research Brief

Wallet Infrastructure
for the Agent Economy

A technical comparison of OWS, Turnkey, and Dynamic — three signing architectures for autonomous trading agents, treasury management, and multi-chain operations.

March 2026 Prepared for Openclaw v1.0
01 Overview
OWS
Local-first wallet standard for AI agents. Single mnemonic, policy-gated signing, MCP-native. MIT licensed.
Best for
  • Autonomous bot signing
  • Arena-scoped wallets
  • MCP tool integration
  • Zero-cost, self-hosted ops
Security
Software enclave
Key model
Single mnemonic
Maturity
v0.3.x (new)
License
MIT / CC0
Turnkey
TEE-native signing with human approval gates. AWS Nitro Enclaves, passkey auth, native AA support.
Best for
  • Human-gated hot wallet ops
  • Passkey co-signing flows
  • ERC-4337 / EIP-7702
  • Gas-sponsored transactions
Security
AWS Nitro TEE
Key model
Single key in enclave
Maturity
Production, SOC 2
License
Proprietary SaaS
Dynamic
True TSS-MPC — the private key never exists. DKLs19 + FROST across EVM, Solana, Bitcoin. Threshold signing with TEE.
Best for
  • Treasury / multi-party MPC
  • Multi-chain TSS signing
  • Server wallets for agents
  • Flexible t-of-n thresholds
Security
TSS-MPC + TEE
Key model
Distributed shares
Maturity
Production, SOC 2 II
License
Proprietary SaaS
02 Integration surfaces
CapabilityOWSTurnkeyDynamic
CLI tool Yesows command Yesturnkey (tkcli) None
MCP server Native, built-in None None
REST API Localhost only Remote (TEE-backed) Remote (TEE-backed)
Node.js / TS SDK Yes — Rust FFI Yes — full suite Yes — React, vanilla, headless
Python SDK Yes — Rust FFI Community None (REST only)
React SDK None Yes Yes — primary path
Mobile SDK None Swift, React Native React Native, Flutter
x402 protocol Yes No Yes
03 Security & signing architecture
DimensionOWSTurnkeyDynamic
Cryptographic model Single key
BIP-39 mnemonic
Single key in TEE
Enclave-isolated
TSS-MPC distributed
Key never exists
Key isolation Software subprocess
(mlock + zeroize)
AWS Nitro Enclave
(hardware boundary)
MPC shares across TEEs
(hardware + cryptographic)
Signing speed ~1 ms
local
50–100 ms
remote TEE
sub-second
MPC ceremony
Co-signing / multi-party None
Single signer only
Hierarchical
Owner → delegate approval
Native t-of-n
2/2, 2/3, 3/5 thresholds
Key resharing N/A N/A Yes — rotate shards, same address
Key export Full — your mnemonic HPKE encrypted export User-initiated export
Audit / compliance Append-only local JSONL SOC 2, full activity logs SOC 2 Type II, yearly audits
04 Chain coverage & account abstraction
FeatureOWSTurnkeyDynamic
EVM chains Yes — secp256k1 Yes — secp256k1 Yes — DKLs19 ECDSA
Solana Yes — Ed25519 Yes Yes — FROST EdDSA
Bitcoin Yes — BIP-84 Limited Yes — FROST BIP-340
Cosmos / TON / Tron All three Partial EVM + SVM focus
ERC-4337 smart accounts None Native Via ZeroDev / Biconomy
EIP-7702 (Type 4 tx) None Native Native
Gas sponsorship None Paymaster native Automated
Addressing standard CAIP-2 / CAIP-10 Chain-native Chain-native
05 Policy engine & access control
CapabilityOWSTurnkeyDynamic
Policy model Declarative rules +
executable subprocess
TEE-native policies +
async human approval
Granular API-level policies +
m-of-n quorum
Chain restrictions Yes Yes Yes
Spending limits Via custom executable Native Native
Contract allowlists Via custom executable Native Native
Human approval gate 5s timeout kills it Native — passkey/webhook Quorum-based
Time-bound access expires_at rule Session expiry Authorization keys
Tx simulation gate Custom executable Built-in External integration
06 Operational considerations
FactorOWSTurnkeyDynamic
Deployment model Self-hosted, local-first Managed cloud (TEE) Managed cloud (TEE)
KYB / KYC required None None None
Cost Free forever Per-signature Per-MAU + free tier
Vendor dependency None — fully local Turnkey infra required Dynamic/Fireblocks infra
Backers / ecosystem MoonPay, PayPal, Circle,
ETH/SOL/TON Foundations
Independent, VC-funded
(Sequoia backing)
Fireblocks (acquired 2025),
Stripe, Magic Eden, Kraken
Open source Fully open — MIT CLI open, service closed SSS lib open, service closed
Server wallets (agentic) Via API token scoping Sub-org + session keys Dedicated server wallet API
07 Key concerns to watch

OWS

v0.3.x — launched March 23, 2026. No security audit yet. Software-only key isolation (no TEE). 5-second policy timeout blocks human approval flows. No native AA or gas sponsorship.

Turnkey

Single key in enclave — not MPC, not threshold. No native m-of-n quorum. Co-signing is hierarchical (owner → delegates), not peer multi-party. Per-signature cost scales with volume.

Dynamic

Server share lives on Dynamic/Fireblocks infra — vendor dependency for signing. No CLI, no MCP server, no Python SDK. Acquired by Fireblocks — long-term roadmap may shift to enterprise. TSS-MPC still in beta for some features.

08 Recommended stack for Openclaw

Three-tier signing architecture

Each tier handles a different risk profile. Transactions are routed by the Openclaw orchestration layer based on value, destination, and policy requirements.

Tier 1 — OWS

Bot-level arena wallets. Small balances, autonomous DEX routing, MCP-native. Each bot gets a scoped API token with contract allowlists and chain restrictions. Signs in microseconds.

Tier 2 — Turnkey

User deposit wallets, withdrawal approval, hot-wallet ops requiring personal sign-off. Passkey-gated on your phone. Native ERC-4337 + EIP-7702 for gas sponsorship and batching.

Tier 3 — Dynamic

Treasury management with true MPC. Private key never exists. Threshold signing (2/3, 3/5) for high-value multi-chain ops. Server wallets for automated rebalancing with policy guardrails.