ERC-8019 Wallet-managed automatic SIWE login (Minimal Wallet-Managed Auto-Login for SIWE)
Review · Signatures & auth · created 2025-09-02
A standard where the wallet pre-stores permission rules for trusted apps, and if a Sign-In With Ethereum (SIWE) message exactly matches those rules, the wallet automatically signs the login without showing a signing prompt
Why it is needed
Sign-In With Ethereum (SIWE) is a way to log into a website by signing a message with your wallet. But even for an app you already trust and use, a prompt appears asking you to sign an almost identical login message every time you connect. Users have to check the same content and press the button repeatedly, which is tedious. Repeated confirmation prompts can create a habit of pressing without reading the content. In fact, the first time a user connects to an app, they already go through a step in the wallet to decide whether to trust that app. This standard proposes carrying that trust decision over to login as well. It defines a simple allowlist that exists only inside the wallet, and allows signing without asking only when an incoming login message passes every clear matching rule. The policy is created and managed solely by the wallet and the user, and the app cannot influence it
What to implement
wallet_getCurrentAutoLoginPolicy: When called with no parameters, it returns the current auto-login policy object for the calling app as activePolicy. If this standard is disabled or there is no policy for that app, it must return null.
In depth
Structure of the allow-policy
A policy consists of six fields. domain is the value that must match the SIWE message's domain exactly, uriPrefix is the prefix that the SIWE URI must start with, allowedChains is the list of allowed chainIds, allowedResources is the set of allowed resources, supportsEIP6492 is a flag that determines how to handle hardware wallet accounts, and expiresAt is the UNIX timestamp at which the policy expires. If expiresAt is 0, there is no expiration. In the example, domain is example.com and allowedChains is [1].
The five auto-sign rules
For a parsed SIWE message M, the wallet MAY auto-sign only when all of the following hold: 1) M.domain equals policy.domain, 2) M.uri starts with policy.uriPrefix, 3) if M.chainId is present, it is included in policy.allowedChains, 4) if policy.allowedResources is not empty, the set M.resources is a subset of it (order does not matter), otherwise no resources are allowed at all, 5) if policy.expiresAt is not 0, the current time precedes it. The wallet must still perform all other ERC-4361 checks as usual, such as nonce uniqueness, time validity, and signature domain binding.
Policies are managed only inside the wallet
Creation, retrieval, modification, and deletion of policies happen only within the wallet UI, and the wallet decides how much control to give the user. Two approaches are recommended. One is to bundle a default policy list for popular apps, and the other is to auto-generate a policy by obtaining user consent on the first SIWE signature for an app judged safe. In the latter case, instead of the standard signing flow, the wallet shows a notice saying "App X wants to log in with your account" along with a checkbox for "auto-login to this app from now on." There are no hints or headers through which the app can influence policy creation.
Hardware wallets and supportsEIP6492
For hardware wallet accounts, auto-signing does not hold because the user is required to confirm the signature on the device without context. This is why the supportsEIP6492 field exists. If this value is false, the wallet MUST NOT auto-login when the account's default signer is a hardware wallet, because the app has no way to verify a smart contract signature. If true, the wallet MAY generate a login signature without device confirmation when 1) EIP-7702 can be applied to the account or the account is a smart account, and 2) a scoped session key or delegation limited solely to auto-login can be approved. However, applying EIP-7702 and setting up the session key itself still require user confirmation, and the method of managing session keys is out of scope for this ERC; ERC-7710 may be used.
RPC method wallet_getCurrentAutoLoginPolicy
The wallet MAY implement this RPC method. It takes no parameters and returns an object containing the current policy for the calling app. The response's activePolicy field contains either the active policy object or null. If this ERC is disabled in the wallet or there is no active policy for the calling app, it must return null for activePolicy. It is also recommended to return null when the policy has expired or when the app is connected to a chain that is not allowed. The app uses this response to decide whether it can initiate a login request on its own without any user action.
Backwards compatibility and rationale
Backwards compatibility is a primary goal of this ERC. Because it uses ERC-4361 as is, existing apps need not change anything. However, to make full use of this ERC, an app should use wallet_getCurrentAutoLoginPolicy to initiate the login request itself rather than waiting for the user to click a login button. As rationale, the proposal notes that it is far easier from a security standpoint to leave the decision of which apps to allow this policy for to the wallet, since most wallets already manage a list of trusted apps. EIP-712 typed data is out of scope because SIWE is plain-text based.
The current status is Review
This proposal is still at the Review stage. Since it has not yet been finalized as a standard, details such as the policy fields or rules may change through discussion.
Things to watch out for
- Auto-login should be off by default: It is recommended that auto-login be off by default in the wallet UI, with the user enabling it directly for sites they trust.
- Standard SIWE verification is still performed: Even when auto-signing, standard SIWE checks such as new nonce verification, correct domain binding, and time validity must still be performed.
- Keep uriPrefix specific: uriPrefix should be kept specific, like /login, to avoid overly broad matching.
- Provide a master off switch: It is recommended that each wallet provide a top-level setting that can disable this ERC entirely.
- Preventing abuse through iframes: M.domain must always be compared against each app's top-level origin. This is to prevent auto-login from working inside an iframe embedded in a malicious top-level origin.