Sato Hub
key management

Key-management / server-wallet providers

What one unit is, what it costs to enter, and what we can observe onchain.

  • Week2026-W42
  • Updated2026-10-12
No reading yet

Key-management / server-wallet providers is not measured: these providers mint ordinary EOAs from a TEE or MPC ceremony — a Privy wallet is indistinguishable from a MetaMask wallet by construction.

One unit is
none observable
Entry costs
n/a

Not measurable — and that is the finding

These providers mint ordinary EOAs from a TEE or MPC ceremony — a Privy wallet is indistinguishable from a MetaMask wallet by construction. And when their user DOES deploy a smart account, the factory belongs to a different company, so the deployment attributes to that account-abstraction vendor rather than to them. Providers whose control surface is off-chain cannot be censused from chain data. This is architecture, not tooling.

What we measured

venue-level

Deployednone observable
unknownProof
▸ How these were measured
  • The unmeasurability is the finding. Affects Privy (server + embedded), Turnkey, Coinbase CDP Server Wallets, Dynamic and Fireblocks.
How this is measured

Each figure is read per chain and per lifecycle stage and is never added to another. A rate computed on fewer than 20 observations is stored and shown as “not enough readings”, never as a finding; a value that could not be read says “not measured” with the reason.

What this page cannot settle

  • Headline safety: The unmeasurability itself is the publishable finding.
  • Every method on this page is EVM-shaped. Solana identity registries are covered elsewhere as upper bounds; Solana payment settlement is not covered anywhere on this site.

Cite this

Sato Hub, "Key-management / server-wallet providers — measured on-chain", satohub.ai/agent-economy/key_management, as of 2026-10-12. CC-BY.

Data: satohub.ai/api/export/adoption.json?venue=key_management (CC-BY, current week; every row carries its method, evidence tier and sample size).

Reference

QuestionsShowHide

Questions people ask about Key-management / server-wallet providers

What is one unit of Key-management / server-wallet providers?
none observable. Counting anything else as a "Key-management / server-wallet providers agent" would compare different objects, so every row on this page names the stage it counts.
What does it cost to enter Key-management / server-wallet providers?
n/a. Entry cost is why raw sizes are not comparable across venues: free and permissionless is a different market from bonded.
Why is Key-management / server-wallet providers not measured?
These providers mint ordinary EOAs from a TEE or MPC ceremony — a Privy wallet is indistinguishable from a MetaMask wallet by construction. And when their user DOES deploy a smart account, the factory belongs to a different company, so the deployment attributes to that account-abstraction vendor rather than to them. Providers whose control surface is off-chain cannot be censused from chain data. This is architecture, not tooling.
Does a count here say the agents work?
No. A registration, a launch or a staked service is an entry in a contract. Nothing about funding, activity, competence or safety is implied, and what happens after entry is measured as its own stage.
SourcesShowHide
Cite this pageShowHide

Cite this page

Sato Hub. "Key-management / server-wallet providers — measured on-chain." Sato Hub, updated 2026-10-12, accessed 2026-10-16. https://satohub.ai/agent-economy/key_management

Data last refreshed 2026-10-12; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Take the data: JSON · CSV (CC-BY).