Cowrie Research

cometh

4 min read

Cometh

  • Name: Cometh
  • URL: https://cometh.io/
  • Category: regulated wallet-and-execution infrastructure company / Safe-based business-wallet operator / ERC-4337 bundler-and-paymaster operator
  • Tags: ethereum-ecosystem
  • Summary: Cometh belongs in companies/ because the practical dependency is not only a smart-wallet SDK exists. It is a named operator that packages a regulated business-wallet stack, runs bundler and paymaster endpoints, gates sponsored addresses and chains through its dashboard and API secrets, bills for gas sponsorship, and wraps those surfaces in an institutional account, compliance, and support shell. That company boundary matters even more now that Cometh is being marketed as part of Kaiko’s regulated onchain-data-and-execution stack rather than as an isolated wallet toolkit.
  • What it does:
    • Operates Cometh Connect, a white-label Safe-based smart-wallet stack for businesses using ERC-4337 account abstraction, biometrics, gasless UX, recovery, and multiple signer integrations
    • Runs bundler infrastructure for ERC-4337 UserOperation submission, estimation, receipt lookup, and supported-entry-point discovery across supported EVM networks
    • Runs paymaster infrastructure for transaction sponsorship, including dashboard-managed sponsored addresses, sponsored-chain controls, API-key and API-secret workflow, and monthly billing for covered gas
    • Markets a broader regulated DeFi infrastructure layer for custody, staking, trading, and payments aimed at fintechs, asset managers, and corporates rather than retail wallet users
    • Operates an account-bearing web application with Google- and GitHub-linked login, support workflow, and company-managed privacy and compliance handling
    • Now sits inside Kaiko’s broader institutional onchain-data and oracle infrastructure story after Kaiko’s 2026 acquisition announcement
  • Key claims:
    • The homepage frames Cometh as The DeFi Infrastructure for Businesses and promises one API for custody, staking, trading, and payments with an enterprise-grade compliance posture, which is already operator-boundary language rather than protocol language
    • The docs say Cometh is building DeFi-native Banking-as-a-Service (BaaS) infrastructure for Europe and combines Crosschain Safe plus ERC-4337 with a MiCA-aligned regulatory perimeter, which makes the company shell analytically important
    • The Bundler docs expose company-hosted endpoints under bundler.cometh.io, API-keyed network access, and supported-entry-point policy, showing that Cometh operates real transaction-admission infrastructure rather than only a client SDK
    • The Paymaster docs make dashboard-managed sponsorship approval explicit: Cometh decides which sponsored addresses and chains are active, requires API credentials and secrets for control routes, and bills the customer monthly for covered gas
    • The dashboard privacy policy shows Cometh running a real web-app account layer with social-login-based identity, account notifications, analytics, and legal-compliance handling, which is a meaningful offchain control surface above the smart-account contracts
    • Kaiko’s acquisition announcement says Cometh holds a MiCA/CASP license (AMF No. A2025-008, granted December 2025), has ISO 27001:2022 certification, has executed more than 1.3 million relayed transactions on Gnosis Chain, and uses segregated accounts with multi-party signing across independent trust domains; even as a buyer-authored source, those are strong signals about where Cometh and Kaiko think the operating boundary lives
  • Whitepaper: No standalone company whitepaper is the point here. The strongest current primary materials are Cometh’s homepage, docs, dashboard privacy policy, and Kaiko’s acquisition announcement, collected in ../whitepapers/cometh-company-primary-sources-2026-08-09.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep cometh focused on the product surface: Cometh Connect, the SDK and signer integrations, bundler and paymaster integration mechanics, gasless UX, and the specific business-wallet features developers actually integrate.
  • Keep this note focused on the company shell above that surface: hosted endpoint operation, API-key and API-secret issuance, sponsorship approval, billing workflow, account and dashboard controls, regulated-service framing, privacy/compliance handling, and the newer Kaiko-parent boundary.
  • That split matters because what features does Cometh expose? and which operator decides whether those features are available, sponsored, billed, and wrapped in a regulated institutional shell? are related but not identical questions.

Control surface

  • Practical leverage sits in API-key issuance, supported-network exposure, bundler admission, paymaster sponsorship approval, sponsored-address and sponsored-chain management, billing and license limits, signer/auth integration defaults, dashboard account workflow, and the support/compliance shell around regulated deployments.

  • The Kaiko acquisition adds another useful lens: Cometh is no longer just a wallet-infrastructure vendor but part of a wider company-run data, oracle, and execution stack that can package compliant market data and onchain execution together.

  • Read Cometh as a regulated wallet-and-execution operating boundary first, and as a reusable ERC-4337 product surface second.

  • Last reviewed: 2026-08-09 UTC

Graph View

Backlinks