Dynamic company primary sources — 2026-08-08

Scope

Primary-source capture supporting the taxonomy split from projects/dynamic to companies/dynamic.

Sources captured

1. https://www.dynamic.xyz/
2. https://docs.dynamic.xyz/
3. https://www.dynamic.xyz/features/wallet-infrastructure
4. https://www.dynamic.xyz/security

Why the company/entity split is warranted

The strongest current first-party read is not Dynamic as a neutral protocol, but Dynamic as a named operator running a hosted wallet-control plane.

Homepage

• Frames Dynamic as Wallet infrastructure for fintech, crypto, and stablecoins.
• Says the product lets customers trade, earn, pay, and move money on global crypto rails.
• Says Dynamic offers enterprise self-custody with distributed signing, flexible thresholds, and recovery paths.
• Says Dynamic inherits Fireblocks’ security expertise, practices, and operational rigor.
• Current marketing claims include 99.9% uptime.

Docs welcome page

• Says Dynamic provides one complete wallet stack.
• Tells teams to Create an environment in the Dynamic dashboard.
• That dashboard-centered setup flow is strong evidence that the durable control surface is a hosted operator environment, not only an SDK artifact.

Wallet infrastructure page

• Current claims include 50M+ users onboarded, 800+ external wallets supported, and < 1 second signing speed.
• Positions the stack around enterprise-grade wallets, powered by TSS-MPC.
• Highlights threshold configuration, TEE use, and signing/recovery packaging.

Security page

• Frames security as spanning key management through compliance.
• Highlights Single Sign-On (SSO), Scoped API Access, and Events & Audit Log.
• Those are operator-boundary features: organization access control, permissioning, and workflow visibility.

Taxonomy conclusion

Dynamic is better kept in companies/ because the useful control-surface questions are:

• who runs the dashboard and environment model,
• who controls identity and access workflow,
• who packages recovery and signing defaults,
• who exposes the audit-log and scoped-API surface,
• and which named operator developers depend on when they adopt the complete wallet stack.

That makes projects/dynamic best treated as an alias pointing to the company note.