Your wallet. Your business.
No usage analytics. No remote crash reporting. ECF Wallet doesn’t track how you use it.
A simpler Ethereum wallet
No trackers. Less clutter. Fully open source.
A self-custody Ethereum wallet.
Focused on what you actually use.
From the Ethereum Community Foundation
No usage analytics. No remote crash reporting. ECF Wallet doesn’t track how you use it.
No advertisements. Less clutter. A simpler interface that keeps the essentials close.
See how your wallet works. Read the code, follow changes, and contribute.
Built for everyday use
A straightforward wallet you can rely on. Send, receive, and manage your assets with fewer distractions.
Ethereum mainnet automatically switches to a backup provider if its primary connection is unavailable.
You retain custody of your keys. Review requests and choose what you approve.
Use ECF Wallet with your Ledger or Trezor.
READY TO CONNECT
Six networks built in. Add custom EVM networks and choose your own RPC endpoints.
Fully open source
Your wallet’s code should be open to inspection. Explore how ECF Wallet is built, follow its development, and help make it better.
Privacy, in plain language
No usage analytics. No remote crash reporting. Network providers and optional services can still receive your IP address and the requests needed to provide their features.
Read the privacy notesZero telemetry means ECF Wallet doesn’t collect usage analytics or send remote crash reports. The analytics and reporting SDKs have been removed.
Requests for blockchain data, function names, or NFTs provide wallet features. They can still reveal information to the service receiving them. Zero telemetry doesn’t make those requests anonymous or blockchain transactions private.
Yes. The wallet connects to an RPC provider to read blockchain data, simulate transactions, and submit them. That provider receives your IP address and the information needed for each request. A transaction simulation is sent before approval, even if you later reject the transaction. You can choose a custom RPC.
When the wallet looks up an unfamiliar contract function, it asks 4byte.directory. That service receives the function identifier and your IP address. This lookup is enabled by default. You can turn it off in Settings > Security & Privacy to stop these lookups.
NFT detection is off unless you turn it on. When enabled, it uses MetaMask’s NFT API (nft.api.cx.metamask.io) to list the selected account’s NFTs on Ethereum, Arbitrum, Optimism, Polygon, and Base. The service receives the account’s address and your IP address. Turning this feature off clears the NFT list. NFT images are also off by default. If you enable them, image hosts receive requests and your IP address.
Phishing-list updates, ENS gateways, and hardware-wallet integrations can also contact outside services. The privacy notes document these connections.
Closing the approval window refuses the transactions, signatures, and other requests waiting in it. You can turn this behavior off to leave requests waiting for later.
The wallet checks domains against a phishing list locally and warns you about known threats. Visited sites are not sent to the list provider. Phishing detection and list updates are enabled by default; either can be turned off.
Less noise. More wallet.
Zero telemetry. Yours to use.