Cowrie Research

cometh

3 min read

Cometh

  • Name: Cometh
  • URL: https://cometh.io/
  • Category: business-wallet and account-abstraction product surface / Safe-based smart-wallet stack / ERC-4337 bundler-and-paymaster integration layer
  • Tags: ethereum-ecosystem
  • Summary: Cometh at the project layer is the developer-facing wallet and execution surface inside a broader Cometh company shell. The useful product cut is not the generic regulated DeFi infrastructure slogan; it is Cometh Connect, its signer integrations, the hosted bundler and paymaster interfaces developers wire against, and the gasless business-wallet UX those pieces make possible. The broader operator, compliance, billing, and Kaiko-parent boundary now lives in cometh.
  • What it does:
    • Ships Cometh Connect, a white-label Safe-based smart-wallet SDK for businesses using biometrics, ERC-4337 account abstraction, gasless flows, recovery, and session-key-style UX
    • Provides a core smart-account SDK with multiple signer and auth integrations including EOA, Magic, Web3Auth, Turnkey, and Privy
    • Exposes Bundler and Paymaster APIs for ERC-4337 UserOperation submission, gas estimation, receipt lookup, and transaction sponsorship across supported EVM networks
    • Gives integrators a concrete path for sponsored-gas UX through dashboard-approved contract sponsorship and paymaster-backed execution
    • Maintains public SDK repositories across web and mobile so the wallet and account-abstraction surface is usable as a real product layer rather than only a marketing promise
  • Key claims:
    • The docs still present the clearest product detail around Cometh Connect, SDK Core, Bundler API, and Paymaster API even while the broader DeFi-as-a-Service layer remains more marketing-heavy than deeply documented
    • Cometh Connect is explicitly framed as a white-label business wallet stack rather than a retail wallet app, which makes this note useful as a product-layer business-wallet and execution surface
    • The Bundler docs show concrete company-hosted endpoints, supported-entry-point discovery, and UserOperation RPC methods, which is the cleanest evidence that developers are meant to integrate a real transaction-submission surface
    • The Paymaster docs show contract-target sponsorship, supported-chain controls, and gasless execution as a first-class part of the product experience rather than an incidental add-on
    • The signer/auth integration list matters because it shows Cometh is packaging account abstraction around a flexible authentication shell instead of insisting on one wallet-or-login model
    • Public repositories across Connect SDK variants and mobile tooling reinforce that Cometh remains a live account-abstraction product surface even as the broader company story expands
  • Whitepaper: No classic whitepaper or litepaper is the key artifact here. The clearest current product-facing sources are Cometh’s docs, SDK, bundler, and paymaster materials, while the broader company shell is captured separately in ../whitepapers/cometh-company-primary-sources-2026-08-09.md.
  • Sources:

Internal linkages

  • Company / operator boundary for hosted endpoints, sponsorship approval, billing, and the newer Kaiko-parent shell: cometh.
  • Strongest product-layer comparisons: safe, alchemy, and turnkey.

Protocol / company boundary

  • Keep this note on the product surface: the business-wallet SDK, signer integrations, bundler and paymaster mechanics, and the gasless execution paths integrators actually implement.
  • Use cometh for the named-operator layer above that surface: endpoint operation, API credential issuance, sponsorship gating, account and dashboard workflow, compliance posture, support, and the Kaiko-parented institutional shell.
  • That split matters because what can a developer integrate? and which company controls the production service path and regulated operating boundary? are related but not identical questions.

Control surface

  • At the product layer, leverage sits in SDK defaults, signer/auth choices, bundler and paymaster integration shape, gasless workflow, and how much of an application’s execution path gets normalized around Cometh-hosted ERC-4337 services.

  • The broader company dependency sits one layer up in cometh: admission, billing, sponsorship approval, dashboard controls, compliance handling, and the growing Kaiko-linked distribution shell.

  • Read Cometh here as a reusable business-wallet and execution product surface, not as a neutral account primitive.

  • Last reviewed: 2026-08-09 UTC

Graph View

Backlinks