Cowrie Research

eip-4361-primary-sources-2026-05-08

2 min read

EIP-4361 primary sources — 2026-05-08

Classification takeaway

EIP-4361 is most usefully classified as wallet-authentication infrastructure: a standard for offchain login prompts, origin binding, and session bootstrap that gives Ethereum accounts a self-custodied alternative to centralized identity-provider login rails.

Primary sources reviewed

  1. Final ERC page — https://eips.ethereum.org/EIPS/eip-4361

    • Frames SIWE as offchain authentication for Ethereum accounts to establish sessions.
    • Emphasizes self-custodied identity-provider replacement, interoperability, and wallet-readable consent surfaces.

  2. Raw ERC markdown — https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-4361.md

    • Defines the ABNF message format and required fields such as domain, URI, chain ID, nonce, and issued-at timestamp.
    • Requires origin-aware verification and warns implementers about phishing, replay, and contract-account validation concerns.
    • Binds smart-account verification to ERC-1271 behavior on the specified chain.

  3. SIWE overview docs — https://docs.login.xyz/general-information/siwe-overview

    • Reiterates the critique of centralized IdPs and frames wallet-based login as an alternative for both Web2 and Web3 services.
    • Highlights the goal of strict specification plus tooling rather than a loose convention.

  4. EIP-4361 explainer docs — https://docs.login.xyz/general-information/siwe-overview/eip-4361

    • Restates the example message, field meanings, and wallet/server implementation guidelines in a more integrator-facing form.
    • Makes the anti-phishing and session-management expectations easier to compare against the normative ERC text.

  5. Reference implementation README — https://raw.githubusercontent.com/spruceid/siwe/main/README.md

    • Says the work was sponsored by the Ethereum Foundation and ENS and developed in the open.
    • Confirms the project’s role as shared ecosystem infrastructure rather than a single hosted login service.

Why it stays in the active corpus

  • Useful comparison class for where wallet authority extends beyond transaction signing into authentication, consent, and session establishment.
  • Helps connect wallet-provider standards, ENS resolution, smart-account verification, and capability-delegation work into one broader authority stack.
  • Likely valuable alongside EIP-1193, EIP-6963, Delegate.xyz, EIP-7702, and ReCaps-style follow-ons when mapping where wallet UX and origin verification become governance-like chokepoints.

Graph View