You're using your Ledger on a DApp when an EIP-7702 authorization request pops up. Before you can even read it, your hardware wallet screen shows "Rejected" or "Not Supported."
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
This is not a bug. It's the device's built-in security mechanism actively blocking the request — you didn't reject the authorization, your hardware wallet rejected it for you.
First, understand: Why hardware wallets reject 7702 authorization
EIP-7702 allows a regular EOA account to temporarily "borrow" smart contract functionality with a single signature. But this feature is restricted by default on hardware wallets.
After the Pectra upgrade, Ledger took a conservative approach: the device supports EIP-7702 at the firmware level, but initially only allows interaction with simple contracts provided by the Ethereum Foundation. Other contracts are blocked directly at the device level. This means that most 7702 authorization requests from DApps will show "Rejected" on your Ledger — and that's normal.
MetaMask is also adjusting its 7702 support for hardware wallets. In the current version, hardware wallet accounts fall back to the traditional model where the user pays gas, rather than using EIP-7702's gas sponsorship feature.
To authorize, first check the whitelist
Confirm whether the contract address you want to authorize is on your hardware wallet manufacturer's allowed list. Follow these steps:
Step 1: Check your wallet manufacturer's 7702 support policy
Different hardware wallets support EIP-7702 differently. First check your brand:
- Ledger: Currently only supports simple 7702 contracts deployed by the Ethereum Foundation. If a DApp uses other complex contracts, the device will block them directly. You need to compare against Ledger's officially published contract addresses and confirm that the address you're interacting with is on the whitelist.
- GridPlus Lattice: Already supports EIP-7702 and is the first hardware wallet manufacturer to fully support this standard. If you use a Lattice, the authorization process will be smoother.
- SafePal: S1 Pro firmware V1.0.78 supports revoking 7702 authorization, and V1.0.77 supports the 7702 protocol.
Step 2: Get the target contract address
When a DApp initiates a 7702 authorization request, pay attention to the contract address shown on the wallet's signing screen. If the hardware wallet screen cannot display it fully, expand the transaction details in your browser first and copy the "To" or "Delegate Address" field.
Step 3: Compare against the official whitelist
Go to your hardware wallet manufacturer's official announcement or documentation, find the whitelist of contract addresses supported for EIP-7702, and compare character by character.
Completion standard: You can confirm that the target contract address is on the whitelist, or confirm that your hardware wallet (such as GridPlus) fully supports 7702 and does not rely on a whitelist.
Common reasons for failure
Many people see their hardware wallet reject a 7702 request and immediately think "the device is broken." Then they upgrade firmware, reinstall the app, or even try a different computer. But these actions won't solve the problem — because the block happens at the device level, not the client level.
If you try to bypass your hardware wallet's restrictions (for example, by importing your seed phrase into a software wallet to execute the authorization), you're tearing down the security foundation of your hardware wallet. Once you authorize a malicious contract, your assets can be drained instantly. Never give up hardware wallet protection just to complete a transaction.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
A troubleshooting checklist for similar situations
Next time your hardware wallet rejects a 7702 authorization, go through this checklist:
| Check Item | Safe Status | Danger Signal |
|---|---|---|
| Target contract address | On the whitelist, or hardware wallet fully supports 7702 | Not on the whitelist, and hardware wallet requires whitelist |
| Hardware wallet firmware | Updated to the latest supported version | Version too old, does not support 7702 protocol |
| Authorization source | A DApp action you initiated yourself | An "upgrade" popup from an unfamiliar website |
| Alternative approach | Choose a DApp that supports 7702 or wait for the official whitelist to expand | Consider using a software wallet to bypass device restrictions |
Risk reminder: You can use eip7702.app to check authorization records by entering an address, but do not connect your wallet — only enter the address for lookup.
How to verify completion: Check whether the target contract address is on the official whitelist. If it is, confirm that your hardware wallet firmware is updated to a version that supports 7702. If it is not on the whitelist, the operation will be blocked at the device level — this is a normal security mechanism.
Next step: If you really need to execute a 7702 authorization, first check the latest whitelist announcement on your hardware wallet manufacturer's official website or documentation, and confirm whether the contract you're interacting with is included. If it's not included and your wallet (such as GridPlus) fully supports 7702, you can try operating through a compatible wallet.
