Agent-safe signing · MPC embedded wallets

Coldstar vs Web3Auth

Web3Auth, now MetaMask Embedded Wallets, is the social-login-to-Solana-key onboarding layer. Shares are split between the user's device and an auth network, then reconstructed on login into an Ed25519 key the app can use. That is good for onboarding humans. For an agent it means the agent ends up holding the root.

Last reviewed 2026-09-04 · Facts link to first-party sources below · Corrections welcome

Pick Web3Auth if

  • You are onboarding consumers with social login and need a Solana key per user.
  • You want the MetaMask brand and a free tier to 1,000 monthly active wallets.
  • You will enforce limits elsewhere.

Pick Coldstar if

  • You are running an agent, not onboarding a person.
  • You need the signer to enforce policy.
  • You do not want the root reconstructed on an online client.

Use both when

Web3Auth for your users; Coldstar for your agents. They do not overlap.

Side by side

ColdstarWeb3Auth
Who holds the root keyYou. The cold root lives encrypted on your own USB drive. No vendor holds a key, a share, or an account.Reconstructed on the client at login from a device share and an auth-network share; neither MetaMask nor the login provider can use one share alone. Full private-key export is supported and toggleable in the dashboard.
Where the key livesOn your machine. The air-gapped root signs a bounded policy envelope; a disposable session key signs routine transactions inside it.Shamir shares across device and auth network; the reconstructed key is exposed to the client app.
Policy enginePer-transaction limit, daily cap, program allowlist, recipient allowlist and blocklist, escalate-above threshold. Evaluated locally, first match wins, before any signature exists.None found.
Out-of-policy transactionsESCALATE to a human over air-gapped QR, or REJECT. No signature is produced for a rejected transaction.Not applicable.
Cold / offline rootYes — the root key never touches a networked machine.No.
Agent integrationFramework-agnostic: the agent proposes an unsigned transaction, the signer decides. CLI signer today; MCP server in progress.None found.
Solana supportSolana mainnet. Core is chain-agnostic; EVM signing exists.Yes: users receive an Ed25519 key suitable for Solana.
Source & self-hostingOpen source (MIT), self-hosted. No API key, no SaaS dependency, nothing to go down.SDKs on GitHub; licences not confirmed. Hosted auth network.
PricingFree software plus a ~$10 drive.Free to 1,000 monthly active wallets plus $0.05 per extra; Growth $69/month for 3,000; Scale $399/month for 10,000; Enterprise custom.
MaturityBeta — the signing core and policy engine are in scope for the planned independent audit.Production; now part of MetaMask.

Web3Auth is not trying to be an agent signer, and this page is here because people search for it as one. The reconstructed key on the client is the opposite of what an agent needs.

Where each one wins

Where Web3Auth wins

  • Onboarding. Social login to a Solana key in one step.
  • Distribution under the MetaMask brand.
  • Price for consumer scale.

Where Coldstar wins

  • The root never reconstructs online.
  • Policy at the signer.
  • Designed for processes, not people.

What you are actually trusting

Web3Auth's MPC protects the key from the provider and the login service, which is the right threat model for a consumer who might lose a password. Once reconstructed on the client, though, the key is a normal secret in a normal process, and it can be exported. An agent using it is an agent with a raw key.

Coldstar never reconstructs the root anywhere online. The agent works from a disposable session key under a local policy; the root is decrypted only in locked RAM on an offline machine, to sign the policy envelope.

Web3Auth is production. Coldstar is beta, pre-audit.

Frequently asked questions

Can an agent use a Web3Auth wallet?

Technically yes; the Node SDK returns a signer after login. It would hold the full reconstructed key, with no policy, which is the situation Coldstar exists to prevent.

Is Web3Auth non-custodial?

By its description, yes: no single party can use a single share. The full key exists on the client after login and can be exported.

Does Web3Auth have spending limits?

None found in its docs at review time.

Try Coldstar in two minutes

Open source, MIT. macOS, Linux, Windows — and on the Solana Seeker dApp Store.

pip install coldstar

Related comparisons

Sources

  1. MetaMask Embedded Wallets architecture (Shamir shares)
  2. MetaMask Embedded Wallets: key export
  3. MetaMask Embedded Wallets: Solana
  4. Web3Auth pricing

Third-party facts were checked against the vendor's own pages on the date above. Pricing and feature sets change; if something here is out of date, tell us and we will fix it.