Comparison

Proof Holdings vs Dynamic

Dynamic (now part of Fireblocks) provisions embedded wallets and connects external ones, and its RS256 token is offline-verifiable, just like Proof's. The real split is the job: Dynamic's headline is creating and operating wallets; Proof verifies control of one you already own, with no key infrastructure. Proof's wallet verification is coming soon.

Verdict

Dynamic runs wallet infrastructure well — and self-issues its tokens. Proof is the neutral verifier: no keys held, no custody stake, one API whose signed proofs cover phone, email, and domain today — wallets next.

One API · One key

One key does what a stack of vendors does

Most platforms on this page run wallet infrastructure. Proof — like SIWE — never touches a key: a single API whose reverse-OTP flow issues a signed, offline-verifiable ES256 token for each of these:

Flat price · Any asset

€0.0079/ proof

One flat price for every asset — phone, email, and domain today, with wallet and social coming soon. No per-seat, no per-MAU, no per-verification tiers — the meter that makes every rival's bill jump.

Free every month
300 proofs
Pay as you go
€0.03 / proof
At volume
€0.0079 / proof

Feature Comparison

Swipe to compare →

FeatureProof HoldingsDynamic
Core jobVerify control of an existing wallet → proof tokenProvision embedded wallets + connect external (its headline)
Runs key infrastructure (TSS-MPC)NoYes
Offline-verifiable tokenES256 + JWKS (coming for wallet)RS256 + JWKS (yes)
Token meaningProof of control (neutral verifier)Environment-scoped session / identity
Verify an existing wallet (SIWE / connect)Coming soonYes — free & unlimited on every tier
Also verifies phone / email / domainLive todayNo
Chains8 plannedBroadest (EVM, Solana, Bitcoin, Cosmos, Sui…)
Pricing modelPer-proofPer-MAU (external-connect-only is free)
OwnerIndependentFireblocks (acquired 2025)

Pricing

Pricing model

Proof Holdings

Per-proof: €0.0079, 300 free/month

Dynamic

Per-MAU: free ≤1,000; Growth $249/mo (5,000, then +$0.05/MAU)

Verify an existing wallet, cheaply

Proof Holdings

Coming soon (per-proof)

Dynamic

Free & unlimited — external-connect users cost nothing

Key custody & liability

Proof Holdings

None — Proof never holds or shards a key

Dynamic

Runs embedded-wallet key infrastructure (TSS-MPC)

What the token means

Proof Holdings

Control of wallet X, from a neutral verifier

Dynamic

A session scoped to your Dynamic environment

Where the line actually falls (Dynamic's token is verifiable too)

Let's not overclaim. Dynamic issues an RS256 JWT with a published JWKS endpoint — genuinely offline-verifiable, the same mechanism Proof Holdings uses: a signed JWT checked against a published key set (the signing algorithm differs — Proof signs ES256 — the mechanism does not). So "only Proof gives you a verifiable token" would simply be false, and this page won't say it.

The real differences are two. First, the job: Dynamic's headline product is creating and operating wallets — embedded wallets via TSS-MPC key sharding, plus external connect — and it's now owned by Fireblocks, a custody-first company. Proof runs no key infrastructure; it verifies a wallet you already control. Second, what the token means: Dynamic's is scoped to your environment (a login/identity session in your app); Proof's is a neutral attestation that control of a specific wallet was proven, issued by a verifier that isn't your app.

Where Dynamic wins, and where Proof fits

Credit where it's due: for simply verifying an existing wallet, Dynamic is hard to beat on price — external-wallet-connect users are free and unlimited on every tier, and its SIWE-based connect is mature, with the broadest chain coverage in this set. If that's all you need today and you're comfortable in Dynamic's SDK, it's an excellent, free choice.

Proof's fit is different: a neutral, multi-asset proof of control that isn't tied to a wallet-provisioning platform or a custody vendor, spanning phone, email, and domain today with wallet coming soon — one portable proof format across all of them. If you want proof of control as a standalone primitive rather than a feature of an embedded-wallet SDK, that's the trade.

When to use Dynamic

  • You want to provision embedded wallets (TSS-MPC) alongside external connect
  • You want to verify existing wallets for free — external-connect users are unlimited
  • You need the broadest chain coverage in one wallet SDK
  • You're building wallet UX as a core part of your product
  • You want Fireblocks-grade custody infrastructure behind your wallets

When to use Proof Holdings

  • You want to verify control without running or trusting any key infrastructure
  • You want a neutral proof of control, not an environment-scoped app session
  • You want one proof format across wallet, phone, email, and domain
  • You want proof-of-control as a standalone primitive, not part of a wallet SDK
  • You'd rather pay per verification than per monthly active user
  • You want a verifier independent of any wallet-provisioning or custody vendor

Frequently Asked Questions

Ready to try Proof Holdings?

300 free proofs per month. No credit card required.

Building with an AI agent? The 176-tool MCP server and test mode let an agent run a real verification right now — machine quickstart in llms-full.txt.