Dmail troubleshooting is wallet login failure and session recovery

One wallet, several Dmail identities

The notable part of Dmail DApp’s unified account model is that one successful wallet login resolves an identity holding wallet addresses, decentralized identifiers, NFT domains and conventional email addresses.

The wallet is the entry credential, while the selected Dmail identity remains a second choice inside the account. ENS, SPACE ID and Unstoppable Domains can resolve named identities; a Dmail NFT domain can also be bound. A fresh signature from the right wallet can therefore open an account whose displayed sender differs from the address remembered from an earlier session. Record the complete wallet address and the active Dmail sender before resetting anything. Those two values reveal whether the fault sits at wallet selection or identity selection.

The account mismatch behind a blank inbox

A blank or unfamiliar Dmail inbox most directly indicates that the browser exposed a different wallet account, even when the extension icon and network name look correct (covered in Dmail requirements guide in detail ).

An Ethereum account address is 20 bytes, rendered as 40 hexadecimal characters; the 0x prefix makes the familiar text form 42 characters. Compare all 42 characters, not a truncated label. ERC-55 keeps the 40-character body and adds about 15 check bits through mixed-case encoding, with a 0.0247% chance that a random typing error passes the checksum. MetaMask lets a user switch accounts without changing the connected chain, while a stale Dmail tab can still hold the previous account in memory. Locking and unlocking the wallet does not prove that Dmail received an accountsChanged event.

Disconnect Dmail from the active wallet account, select the intended address and request a new sign-in. The wallet should present a message-signing request for login, not a value transfer. Reject any prompt that asks to broadcast an unrelated asset movement. Once Dmail displays the intended full address and sender identity, reload the inbox before touching chain settings.

Network selection before a new signature

Dmail network selection must match the chain offered by the chosen wallet provider, because a correct address paired with the wrong chain leaves the login context unresolved.

Six durable EVM identifiers are useful checkpoints in Dmail’s documented wallet flows. Ethereum Mainnet uses chain ID 1, zkSync Era uses 324 and Scroll uses 534352. Linea uses 59144, opBNB uses 204 and Manta Pacific uses 169. MetaMask returns an EVM chain identifier in hexadecimal through its provider interface, although wallet screens commonly display a network name. Read the requested network first, then compare its chain ID with the wallet’s configured network. Do not substitute a similarly named test network; its chain ID represents a separate ledger and provider context.

The table separates network identity from wallet identity. Every row uses a Dmail-documented EVM route, and every chain retains the same 20-byte account format even though balances, contracts and session state remain chain-specific.

If the required network is missing, add it using the wallet’s verified network configuration, then close the stale Dmail tab. A custom Remote Procedure Call endpoint affects connectivity but not the chain ID. Changing only the endpoint will not fix a chain mismatch. Reopen Dmail after MetaMask reports the intended network and address together; that sequence forces the application to read one coherent provider state rather than two snapshots.

On Starknet, use Argent X and the Starknet login route rather than importing an EVM chain ID. That branch uses a different account model and wallet provider.

What does the wallet error code mean?

An EIP-1193 wallet error code identifies whether Dmail lost account permission, met an unsupported method or reached a provider that cannot serve the selected chain.

EIP-1193 defines code 4001 for a rejected request, 4100 for an unauthorized method or account, 4200 for an unsupported method, 4900 for total disconnection and 4901 for disconnection from the requested chain. Code 4001 calls for another deliberate sign-in attempt. Code 4100 calls for restoring site permission to the intended account. Code 4200 points to a wallet-provider capability gap. Codes 4900 and 4901 move the diagnosis to connectivity or chain selection. Browser interfaces sometimes replace these numbers with prose, so use the wording and wallet state together.

A clean session reset in five passes

A clean Dmail session reset removes the application’s old account and chain snapshot, then rebuilds both values from one unlocked wallet provider in a controlled order.

1. Write down the full Dmail sender identity and full wallet address currently shown. This creates two comparison points without changing the mailbox or on-chain account.
2. Disconnect Dmail in the wallet’s connected-sites panel. In a browser with several extensions, disable extra EVM providers for this attempt so MetaMask remains the sole injected choice.
3. Remove Dmail’s site data, including cookies, local storage and session storage. Keep password-manager data and wallet extension storage untouched; they belong to different browser origins and components.
4. Close every Dmail tab, unlock the intended account and reopen one tab. Select the requested network before starting login, not after the sign-in prompt appears.
5. Approve one fresh sign-in request, then compare the complete address and selected Dmail identity. Stop repeating signatures once both values match; the remaining fault sits in account binding or service state.

EIP-1193 standardizes one request method and five provider events: connect, disconnect, chainChanged, accountsChanged and message. A page that misses either state-change event can display an obsolete account or chain until reload. The five-pass reset makes the wallet emit fresh state and gives Dmail one clean initialization path, which is the point to inspect the restored inbox.

DID and NFT domain recovery after login

At that point, Dmail identity recovery starts only after the correct wallet address appears, because ENS, SPACE ID, Unstoppable Domains and Dmail NFT domains resolve within the account layer. Open the sender selector and confirm the expected identity is active and bound. If the wallet address is right but the named identity is absent, preserve the working session and inspect account binding instead of cycling networks. That boundary prevents a valid login from becoming another provider problem.

The diagnostic order that preserves the mailbox

Effective Dmail troubleshooting follows a fixed evidence order: full wallet address, active provider, chain ID, fresh sign-in response and selected mailbox identity inside the Dmail DApp. Stop at the first mismatch and correct only that layer. Changing wallet, network and browser data together erases the comparison that reveals the cause. Once all five checkpoints agree, the recovered session should present the intended sender and inbox. Persistent failure then moves the case to Dmail account binding or service availability.