What Matters
AI can reduce Web3 complexity without removing Web3 responsibility. Agents can explain transactions, estimate gas, route users to the right network, simulate approvals and prepare recovery steps. They cannot make custody reversible, guarantee a contract is safe, create liquidity or give informed consent on the user’s behalf.
DN Evidence Block
Reviewed: 20 November 2026. Primary evidence: ERC-4337 and EIP-7702, Ethereum account-abstraction documentation, WalletConnect developer documentation and wallet-security guidance.
Boundary: wallet, paymaster, chain and application support varies. The examples describe architecture, not a security endorsement of a product.
Eight Frictions AI Can Reduce
| Friction | Useful agent action | Evidence required | Failure to prevent |
|---|---|---|---|
| Wallet selection | Match custody and recovery needs | Official wallet capabilities | Choosing convenience without recovery |
| Network selection | Identify correct chain and asset | Chain ID, contract and destination support | Sending to incompatible network |
| Gas | Estimate, sponsor or batch fees | Live quote and sponsor policy | “Gasless” presented as free |
| Transaction meaning | Translate calldata and approvals | Verified contract and simulation | Blind signing |
| Phishing checks | Compare domain, contract and signature | Trusted allowlists and source records | Confident but false reassurance |
| Fiat on/off-ramp | Explain routes, fees and limits | Current provider and jurisdiction terms | Unsupported or non-compliant route |
| Portfolio context | Explain balances and protocol exposure | Read-only verified data | Granting broad signing authority |
| Recovery workflow | Guide tested guardians or passkeys | Wallet-specific recovery policy | Agent inventing a recovery path |
1. Wallet Selection Based on Authority
A beginner may need a simple passkey smart account, a hardware wallet, a multisignature treasury or a read-only portfolio. The agent should ask what value is at risk, who must approve, how recovery works and which applications are needed.
It should not rank wallets solely by interface or token support. Custody, owner-key protection, session-key limits, upgradeability and recovery determine the risk.
2. Network and Asset Resolution
Users often see the same symbol on several chains. The agent should resolve chain ID, contract address, token standard, bridge status and destination support before displaying a “send” action. Contract addresses must come from trusted issuer or application documentation rather than search snippets.
When certainty is low, the correct outcome is a refusal or a small test transaction—not a guessed network.
3. Gas Sponsorship and Fee Abstraction
ERC-4337 paymasters can sponsor gas or apply separate billing rules, and smart accounts can batch actions. This can remove the need for a beginner to acquire native gas before the first interaction.
The interface should still show who pays, what quota applies, what happens when sponsorship fails and the maximum total cost. “Gasless” describes user experience, not economics.
4. Plain-Language Transaction Explanations
Before signing, the agent can identify the contract, function, token amount, recipient, allowance, deadline and whether the action is upgradeable or delegated. Simulation can show expected balance and approval changes.
The explanation should distinguish direct evidence from inference. A model cannot guarantee safety from source code alone, especially when proxies, oracles, governance and offchain systems are involved.
5. Phishing and Approval Screening
Agents can compare domains, certificates, contract addresses, spender permissions and known threat lists. They can warn when an approval is unlimited, a signature grants delegation or the destination is new.
The security decision must be policy-driven. An attacker can manipulate a model through website content, support messages or tool results. High-risk signatures should require a separate trusted simulation and user confirmation.
6. Guided Fiat and Stablecoin Routing
An agent can compare supported on-ramps, bank methods, fees, limits and settlement times for the user’s jurisdiction. It should store the exact legal entity and product availability rather than assuming the same brand offers the same services globally.
It must not route around KYC, sanctions, exchange-control or location restrictions. Where tax or reporting is uncertain, it should explain the record to preserve.
7. Read-Only Portfolio Education
A read-only connection can show protocol positions, approvals, collateral, maturity and bridge exposure. This is a safer first step than giving a new agent transaction authority.
Separate observation from execution. The portfolio assistant can prepare an action and explain the risk while a wallet policy or human approves the transaction.
8. Recovery Guidance
Smart accounts, passkeys, guardians and institutional wallets can offer recovery options beyond one seed phrase. The agent should guide the documented recovery process, verify contacts out of band and explain delays and revocation.
It should never ask users to paste seed phrases, private keys or recovery codes into a chat or support form.
Four Frictions AI Cannot Remove
- Irreversibility: a valid signature can create permanent loss.
- Legal rights: a token or protocol may not grant the rights a user assumes.
- Liquidity and market risk: a clean interface cannot guarantee an exit price.
- Informed consent: the user must approve custody, risk and financial consequences.
DN Rule
The agent may simplify the decision; it must not hide the decision. Every transfer, approval and delegation should remain inspectable and revocable where the architecture permits.
DN Web3 Onboarding Safety Check
Screen one onboarding flow.
Worked Example
A new user wants to deposit USDC into a lending protocol. The agent resolves the correct contract and chain, checks that the wallet has native gas, simulates the approval and deposit, explains liquidation and smart-contract risk, and prepares the transaction. The wallet requires a passkey confirmation.
The agent does not request the recovery phrase, choose an unlimited approval or promise a stable return. It reduces friction while preserving user authority.
Methodology and Limitations
DN mapped onboarding across custody, network resolution, gas, transaction meaning, phishing, fiat rails, portfolio context and recovery. We did not audit every wallet, paymaster or application and do not provide legal or financial advice.
Frequently Asked Questions
Can AI create a wallet for a user safely?
It can guide setup or call a wallet provider, but the user must understand custody, recovery and transaction authority. The model should not receive seed phrases or owner keys.
Can an agent make gas fees disappear?
It can use sponsored transactions, paymasters or fee abstraction, but someone still pays and the policy may impose quotas, pricing or eligibility.
Can AI explain a smart contract accurately?
It can summarize verified code and simulation results, but it can miss hidden dependencies, upgrades or offchain terms. Explanations should link to evidence and uncertainty.
Can AI recover a lost wallet?
Only through a wallet’s existing recovery design, such as guardians, passkeys or institutional procedures. It cannot recreate an unknown private key.
What onboarding friction cannot be automated away?
The user’s informed approval of custody, irreversible risk, legal obligations and financial loss.
Primary Sources
- ERC-4337
- EIP-7702
- Ethereum.org Account Abstraction
- WalletConnect Documentation
- Ethereum.org Security
Editorial disclosure: no wallet, paymaster or onboarding provider paid for inclusion.




