Cowrie Research

ethereum-identity-kit

4 min read

Ethereum Identity Kit

  • Name: Ethereum Identity Kit
  • URL: https://ethidentitykit.com/
  • Category: application-facing identity middleware / ENS+EFP+SIWE integration toolkit / React component library for the Ethereum identity stack
  • Summary: Ethereum Identity Kit is best understood not as a generic UI kit, but as app-facing middleware that packages multiple Ethereum identity primitives into a reusable integration layer. Its primary materials present it as a React component library plus supporting API and transaction-provider infrastructure for bringing ENS, Ethereum Follow Protocol (EFP), and Sign-In with Ethereum (SIWE) into applications without every app rebuilding profile lookups, social-graph queries, wallet wiring, and transaction flows from scratch. That makes it a useful comparison class for EFP, SIWE, ENS-profile tooling, and broader wallet/app middleware such as Reown: the key question is not only who owns identity data, but which library, hosted API, and default component stack decides how that identity data becomes legible inside downstream apps.
  • What it does:
    • Provides a React component library for rendering Ethereum identity surfaces such as profile cards, profile tooltips, avatars, follow buttons, and related account UI
    • Bundles ENS, EFP, and SIWE-adjacent functionality into one application-facing toolkit positioned as the “Ethereum identity stack” for app developers
    • Requires app integrators to wire in Wagmi, TanStack Query, and an Ethereum Identity Kit Transaction Provider, making wallet connectivity, caching, and transaction flow part of the middleware surface
    • Exposes a public API layer for common EFP-derived data such as follower counts, following lists, follower lists, and ENS data
    • Explicitly allows self-hosting by forking EFP’s open-source indexer/API instead of relying solely on the default public endpoint
    • Extends the same identity stack into AI-facing tooling through ETHID MCP, which exposes EFP / ENS / SIWE-oriented social-graph and profile queries to assistants and applications
  • Key claims:
    • The official docs say Ethereum Identity Kit lets developers “easily implement the Ethereum identity stack” inside applications, which is the clearest reason to catalog it as integration middleware rather than as a standalone identity protocol
    • The docs and README both define the project as a React component library, which matters because the practical control surface here is not only identity data storage but the default application layer that chooses how profiles, follows, and account metadata are presented to users
    • The setup docs require Wagmi, TanStack Query, and a Transaction Provider, showing that the kit is opinionated middleware that bundles data fetching, wallet interaction, and transaction orchestration rather than a purely presentational component set
    • The public API docs say developers may use the official EFP-backed endpoint for follower/following stats and ENS data, which reveals an important centralization surface: many downstream apps can inherit one shared hosted indexer/API even if the underlying protocols are open
    • The same API docs explicitly say developers may fork and self-host EFP’s Indexer/API source code, which makes the hosted-versus-self-hosted boundary a first-class design choice instead of an implementation accident
    • ETHID MCP is analytically useful because it shows the stack expanding beyond frontend components into AI-facing query middleware, with a Cloudflare Worker proxying EFP-oriented social-graph and identity requests in an AI-optimized format
    • The reusable insight is that identity stacks do not stop at protocols like ENS, SIWE, or EFP; practical power often shifts upward into packaged component libraries, hosted APIs, caching layers, and opinionated developer tooling that determine which identity data is easiest to import and display
  • Whitepaper: No standalone Ethereum Identity Kit whitepaper or litepaper surfaced in this pass. The clearest current primary materials were the official site, docs, API documentation, ETHID MCP docs, and the official GitHub README collected in ../whitepapers/ethereum-identity-kit-primary-sources-2026-05-12.md.
  • Sources:

Internal linkages

  • Identity-and-follow-data substrate it packages into an app-ready stack: ethereum-follow-protocol

  • Wallet-auth primitive that often sits underneath profile-aware app sessions even when the UI is identity-first: eip-4361

  • App-side wallet/session middleware cousin that packages connection, auth, and account UX into one developer-facing surface: reown

  • Last reviewed: 2026-05-31 UTC

Graph View