Proof Holdings vs Web3Auth
Web3Auth — now MetaMask Embedded Wallets — derives non-custodial key shares from a social login (MPC): wallet creation as a service. Proof Holdings is the opposite motion — verify what already exists, hold no key material at all — for wallets (coming soon) as for phones, emails, and domains today.
Use Web3Auth to onboard users into brand-new wallets. Use Proof to trust what already exists: a control check with no key custody, returning an offline-verifiable signed token — live for 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
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 | Web3Auth |
|---|---|---|
| Core job | Verify control of an existing wallet → proof token | Provision social-login wallets (its headline) |
| Runs key infrastructure (MPC / Shamir) | No | Yes |
| Creates a wallet for the user | No | Yes — from social login |
| Offline-verifiable token | ES256 + JWKS (coming for wallet) | ES256 + JWKS (yes) |
| Token meaning | Proof of control (neutral verifier) | App-scoped (Project Client ID) |
| Also verifies phone / email / domain | Live today | No |
| Pricing model | Per-proof | Per-MAW |
| Free tier | 300 proofs/month | ≤1,000 MAW |
| Owner | Independent | Consensys / MetaMask (2025) |
Pricing
Pricing model
Proof Holdings
Per-proof: €0.0079, 300 free/month
Web3Auth
Per-MAW: free ≤1,000; Growth $69/mo (3,000); Scale $399/mo (10,000)
Key custody & liability
Proof Holdings
None — Proof never holds or shards a key
Web3Auth
Runs MPC/Shamir key-share infrastructure
What the token means
Proof Holdings
Control of wallet X, from a neutral verifier
Web3Auth
A session scoped to your Web3Auth project
Onboarding non-crypto users into wallets
Proof Holdings
Not what Proof does
Web3Auth
Best-in-class social-login wallets (MPC)
Provisioning vs proof-of-control
Web3Auth — now MetaMask Embedded Wallets after Consensys acquired it — creates non-custodial wallets by deriving key shares from a social login (MPC / 2-of-3 Shamir), so a non-crypto user gets a wallet without a seed phrase. That's its headline, and it runs the key infrastructure 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.
Web3Auth's token is verifiable (ES256 with a public JWKS, even labeled a "wallet ownership" token), so "only Proof issues a verifiable token" would be false. The real difference is that its token is audience-scoped to your project — its own docs warn you to check the `aud` — while Proof's is a neutral proof of control issued by a verifier that isn't your app, and Proof carries no key infrastructure to trust. Web3Auth's wallet verification is live; Proof's is coming soon (the model is live for phone, email, and domain).
Where each fits
If your goal is to get non-crypto users into a wallet with a familiar social login, Web3Auth / MetaMask Embedded Wallets is a mature, well-supported way to do it, chain-agnostic and now inside the MetaMask ecosystem.
If your goal is a neutral, multi-asset proof of control — no key infrastructure, one portable format spanning phone, email, and domain today and wallet soon — that's Proof. They're complementary more than competitive: provision with Web3Auth, prove control with Proof.
When to use Web3Auth
- You want to create non-custodial wallets from a social login (MPC)
- You're onboarding non-crypto users and want familiar auth
- You want chain-agnostic embedded wallets inside the MetaMask ecosystem
- You want key shares managed for you (2-of-3 Shamir / MPC)
- 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 MPC/Shamir key infrastructure
- You want a neutral proof of control, not an app-scoped session token
- 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.