Agent-safe signing · Institutional wallet-as-a-service

Coldstar vs Dfns

Dfns is built for institutions: MPC signer nodes in enclaves, velocity limits, sanctions screening, travel-rule integration, and approval groups with quorums. It is the most complete escalation model of the hosted signers. It is also priced and shaped for a compliance team, not for an agent developer.

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

Pick Dfns if

  • You are a regulated business that needs KYT screening, travel rule, and M-of-N approval groups.
  • You want velocity limits (value and count per window) enforced by the platform.
  • You want SOC 2, ISO 27001, and named audit firms, and can budget from $800 to $35,000 a year.

Pick Coldstar if

  • You want an owner-held offline root rather than vendor-run MPC nodes with an undisclosed threshold.
  • You are one team or one operator running agents, not a compliance department.
  • You want free, open-source, self-hosted.

Use both when

Dfns for the regulated operating accounts; Coldstar for the cold reserve behind them.

Side by side

ColdstarDfns
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.Dfns-operated MPC/TSS nodes. The security page does not disclose the threshold or whether customers hold a share. "Break-the-glass" key export is offered. Delegated (end-user) wallets bypass the policy engine entirely.
Where the key livesOn your machine. The air-gapped root signs a bounded policy envelope; a disposable session key signs routine transactions inside it.MPC signer nodes inside AWS Nitro Enclaves; Intel SGX, IBM, Thales HSM, and on-prem options on request.
Policy enginePer-transaction limit, daily cap, program allowlist, recipient allowlist and blocklist, escalate-above threshold. Evaluated locally, first match wins, before any signature exists.Rules: transaction amount limit (USD and nominal), amount velocity and count velocity per time window, recipient whitelist, Chainalysis and travel-rule screening. Actions: block or request approval. Program- or instruction-level Solana rules not listed. Enforcement at the policy layer; not stated as in-enclave.
Out-of-policy transactionsESCALATE to a human over air-gapped QR, or REJECT. No signature is produced for a rejected transaction.Held for approval by one or more approval groups, each with its own quorum; all must pass. The strongest escalation model in this set.
Cold / offline rootYes — the root key never touches a networked machine.No air-gapped root. On-prem and HSM deployments exist for enterprise.
Agent integrationFramework-agnostic: the agent proposes an unsigned transaction, the signer decides. CLI signer today; MCP server in progress.No dedicated agent product or docs found.
Solana supportSolana mainnet. Core is chain-agnostic; EVM signing exists.Yes, including durable nonces.
Source & self-hostingOpen source (MIT), self-hosted. No API key, no SaaS dependency, nothing to go down.Cryptographic libraries donated to the Linux Foundation; service code closed. Hosted or enterprise on-prem.
PricingFree software plus a ~$10 drive.Starter $800/year (10 wallets, 100 signatures/month); Basic $8,000/year; Pro $35,000/year; Enterprise custom. No AUM or per-transaction fees.
MaturityBeta — the signing core and policy engine are in scope for the planned independent audit.Production; SOC 2 Type II (KPMG), ISO 27001; audits by Kudelski, Halborn, Redacted.

Dfns gets escalation right: real quorums, real velocity limits, real screening. If you need those for regulatory reasons, Coldstar is not a substitute. If you need them because an agent should not be able to drain a wallet, Coldstar gives you the limits and the human gate without the institution.

Where each one wins

Where Dfns wins

  • Approval quorums. Multi-group M-of-N holds on transactions.
  • Compliance tooling. KYT, travel rule, ISO 27001.
  • Velocity limits by value and count per window.

Where Coldstar wins

  • Disclosed, simple trust model. One encrypted root on your drive; no undisclosed MPC threshold.
  • Cold root. Never on a networked machine.
  • Cost and openness. Free, MIT, self-hosted, versus a four- to five-figure annual subscription.

What you are actually trusting

Dfns runs the signer nodes. Its security page does not say how many shares exist or whether you hold one, and it notes delegated wallets skip the policy engine. For an institution buying a compliant service with contracts and audits behind it, that is a normal arrangement. For a developer trying to bound an agent, it is a lot of surface you do not control.

Coldstar's arrangement is explicit: one ciphertext root on a drive in your possession; local policy with limits, allowlists, and a daily cap; escalation to a human over QR. You can read all of it.

Dfns is production, certified, and audited. Coldstar is beta, pre-audit.

Frequently asked questions

Does Dfns have an AI-agent product?

We did not find one on its first-party pages at review time. Its API supports programmatic signing under policy, which an agent could use.

Who holds the key with Dfns?

Dfns-operated MPC nodes in enclaves. The threshold and customer share are not disclosed on the security page. Break-the-glass export is offered.

Which has better escalation?

Dfns, for institutional workflows: multi-group quorums. Coldstar has a single escalate-to-human step over QR, which is what a small team actually operates.

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. Dfns security model (Nitro Enclaves, MPC, certifications)
  2. Dfns policy engine (rules and actions)
  3. Dfns: Solana broadcast (durable nonces)
  4. Dfns 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.