Proof Holdings vs Magic
Magic — once famous for the magic link, now embedded-wallet infrastructure — provisions non-custodial wallets and runs the key infrastructure at scale. Proof Holdings runs no keys: it proves control of assets a user already holds — wallets included, coming soon.
Magic creates wallets; Proof creates certainty about them. No key infrastructure to trust, one flat per-proof price, and the same signed-token model already verifying phones, emails, and domains in production.
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
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 →
| Feature | Proof Holdings | Magic |
|---|---|---|
| Core job | Verify control of an existing wallet → proof token | Provision embedded wallets (its headline) |
| Runs key infrastructure (TEE / Shamir / KMS) | No | Yes |
| Creates a wallet for the user | No | Yes — from email / social |
| Offline-verifiable token | ES256 + JWKS (coming for wallet) | DID token via ecRecover (15-min, app-scoped) |
| Token meaning | Proof of control (neutral verifier) | App session (short-lived) |
| Also verifies phone / email / domain | Live today | No |
| Pricing model | Per-proof | Per-MAW |
| Free tier | 300 proofs/month | ≤1,000 MAW |
| History | Focused verification API | Pivoted from 'magic links' to wallet infra |
Pricing
Pricing model
Proof Holdings
Per-proof: €0.0079, 300 free/month
Magic
Per-MAW: free ≤1,000; Startup $99/mo (2,500)
Key custody & liability
Proof Holdings
None — Proof never holds or shards a key
Magic
Runs embedded-wallet key infrastructure (TKMS)
What the token means
Proof Holdings
Control of wallet X, from a neutral verifier
Magic
A short-lived app session (DID token)
Embedding wallets from email/social
Proof Holdings
Not what Proof does
Magic
Enterprise-grade embedded-wallet infra
Provisioning vs proof-of-control
Magic — known early on for passwordless "magic links," now positioned as embedded-wallet infrastructure ("The fastest way to build onchain," used by the likes of Polymarket) — provisions non-custodial wallets from email or social login and runs the key infrastructure (TEE + Shamir + KMS) to do it. Proof Holdings does the opposite job: it verifies a wallet the user already controls and never creates, holds, or shards a key.
On tokens: Magic's DID token is verifiable locally (a secp256k1 `personal_sign` you check via ecRecover), so it's not "unverifiable." But it's a short-lived (about 15-minute), app-scoped session with no published vendor JWKS — a login credential. Proof's is a neutral, durable proof of control issued by a verifier that isn't your app. Magic's wallet provisioning is live; Proof's wallet verification is coming soon (live today for phone, email, and domain).
Where each fits
If you want to onboard users into embedded wallets from email or social — with enterprise-grade key management handled for you — Magic is a mature choice, now spanning EVM plus Solana, Cosmos, and Hedera.
If you want a neutral, multi-asset proof of control with no key infrastructure — one portable format across phone, email, and domain today, wallet soon — that's Proof. Provision with Magic, prove control with Proof: complementary, not competing.
When to use Magic
- You want to provision embedded wallets from email or social login
- You want enterprise-grade key management (TEE + Shamir) handled for you
- You're onboarding non-crypto users and wallet UX is core
- You want EVM plus Solana/Cosmos/Hedera coverage in a wallet SDK
- Per-MAW pricing fits your active-wallet economics
When to use Proof Holdings
- You want to verify a wallet the user already owns, not create one
- You don't want to run or trust wallet key infrastructure
- You want a neutral, durable proof of control, not a 15-minute app session
- You want one verification primitive across wallet, phone, email, and domain
- You'd rather pay per verification than per monthly active wallet
- You want zero custody surface and no key-management liability
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.