Zerodust

ZeroDust is a blockchain native token complete exit system based on EIP-7702, allowing users to completely zero out their account balance and transfer it to the target address through sponsored execution, solving the problem of residual funds caused by the need to reserve gas fees in traditional transfers.

Finance Developer tools #Blockchain exit #Zero balance transfer #Cross-chain bridging #EIP-7702 .TypeScript

rating : 2 points

downloads : 6.2K

update time : 2026-03-13

Open Site

What is ZeroDust?

ZeroDust solves the classic dilemma users face when they want to completely exit a blockchain: you need to pay gas fees to send tokens, but if you send all your tokens, there will be no gas fees to pay. This results in a small amount of funds being 'trapped' on the chain. ZeroDust uses EIP-7702 technology, where a sponsor pays the gas fees and executes a transaction to completely zero out your balance and transfer it to the target address, whether it's cross-chain or on the same chain.

How to use ZeroDust?

It's very simple to use: 1) Connect your wallet to the ZeroDust interface. 2) Select the source chain (the chain you want to exit) and the target (it can be another address on the same chain or cross-chain). 3) Sign an authorization once (no gas payment required). 4) ZeroDust's sponsor network will execute the zeroing operation. 5) The funds reach your target address, and the balance on the source chain becomes zero.

Use cases

When you need to: 1) Completely empty all native tokens (such as ETH, BNB) on a chain and migrate to another chain. 2) Combine scattered funds from multiple wallets into one main wallet. 3) Ensure that there are no 'dust balances' left before selling a wallet or stopping using a certain chain.

Main features

100% balance zeroing

The core function ensures that the balance of the source address is exactly zero wei after the transaction, leaving no residue.

No need to pre-deposit gas

Using EIP-7702, users only need to sign an authorization, and the sponsor pays and executes the transaction, achieving a 'gas-free' exit.

Multi-chain and multi-mode support

Supports three fund transfer modes: cross-chain (to different chains), cross-address (to different wallets), and same-chain consolidation.

Unified contract address

Use the same contract address on all 26 supported mainnets and 46 testnets, facilitating integration and invocation.

Transparent fee structure

The fees are clear: 1% service fee (with upper and lower limits) + Gas compensation + Cross-chain bridge fee. All fees are known to the user before signing.

Strong security guarantee

The contract is non-upgradable, has no administrator privileges, enforces a zero balance, uses ERC-7201 storage isolation, and funds are not held in the contract for custody.

Advantages

Solve the fundamental pain point: The only solution that can truly achieve a 100% exit of native tokens.

Minimal user experience: A single signature can complete complex operations without dealing with gas.

High security: Atomic operations, funds do not stay in the contract, and users control the upper limit of fees.

Wide coverage: Supports 26 mainnets including mainstream L2 and EVM chains, with good ecological compatibility.

Controllable cost: The service fee has a cap, and the proportional fee is very low for large transfers.

Limitations

Depends on EIP-7702: Can only be used on chains that support EIP-7702 (some chain testnets do not support it).

There are service fees: It will incur additional costs compared to manual operation (if possible).

Cross-chain depends on third-party bridges: The cross-chain speed and decoupling are affected by the selected bridge (such as Gas.zip).

Only supports native tokens: Currently focuses on the native gas tokens of the chain (ETH, BNB, MATIC, etc.), and does not directly handle ERC-20 tokens.

How to use

Connect wallet

Access the ZeroDust application interface and connect using your Web3 wallet (such as MetaMask). Ensure that your wallet is on the source chain network you want to empty.

Set transfer intent

Select in the interface: 1) The source chain (the chain where your funds are located). 2) The target chain and address (it can be on the same chain or cross-chain, and the address can be the same or different). 3) Select the cross-chain bridge (if cross-chain).

Review and sign

The system will display the estimated net amount you will receive, service fees, Gas compensation fees, etc. After confirming that everything is correct, sign an EIP-7702 authorization message. No gas payment is required for this step.

Wait for execution

After signing, your transfer intent enters the ZeroDust network. The sponsor node will obtain your intent, simulate the transaction to ensure security, and then submit the transaction to the chain.

Completion and verification

After the transaction is successful, you can check the funds on the target chain. At the same time, query your address on the source chain browser, and the balance should show 0.

Usage examples

Case 1: Completely migrate from Arbitrum to Base

Xiaoming has 0.005 ETH on Arbitrum. He wants to transfer all his assets to the Base chain for continued use. He uses ZeroDust, selects the source chain Arbitrum and the target chain Base (the same wallet address). After signing, his Arbitrum balance becomes zero, and about 0.00495 ETH (after deducting fees) appears on the Base chain.

Case 2: Combine small change on Polygon into the main wallet

Xiaohong has several Polygon test wallets, each with a small amount of MATIC. She uses ZeroDust's same-chain mode to zero out the balances from these wallets and send them all to her main wallet address, completing the fund consolidation.

Case 3: Asset cleanup before selling a wallet

Xiaowang plans to sell a wallet containing assets from multiple chains. After transferring ERC-20 tokens and NFTs, there are still small amounts of native tokens remaining on each chain. He uses ZeroDust to zero out the balances on each chain one by one, aggregating all the native tokens to another secure address of his, ensuring that the wallet for sale is completely clean.

Frequently Asked Questions

Is it safe to use ZeroDust? Will my funds be withheld?

How much are the fees? How are they calculated?

Which chains can use ZeroDust?

If my balance is very small (for example, worth less than $0.05), can I still use it?

How long does it take for cross-chain transfers?

Can I transfer ERC-20 tokens?

Related resources

Smart contract code repository (GitHub)

The source code of all ZeroDust smart contracts, developed using the Foundry framework.

Technical specification document

Detailed technical specifications of the protocol, including data structures, function interfaces, and security considerations.

Mainnet contract address and deployment list

The unified contract address `0x3732398281d0606aCB7EC1D490dFB0591BE4c4f2` on all 26 mainnets and browser links for each chain.

Introduction to the EIP-7702 standard

Understand the core standard of 'external account proxy execution' that ZeroDust depends on.

Gas.zip cross-chain bridge

The ultra-fast cross-chain bridge that ZeroDust integrates by default, supporting more than 200 chains.

Verified transaction example

A real transaction record of successfully zeroing out and transferring $3.57 on Arbitrum.

🚀 ZeroDust

Exit a blockchain completely - transfer 100% of your native gas balance via EIP-7702

ZeroDust is an intent-based exit system that enables users to sweep their entire native gas token balance to exactly zero via EIP-7702 sponsored execution.

🚀 Quick Start

When users want to fully exit a blockchain, they face an impossible situation:

User has: 0.0008 ETH on Arbitrum
User wants: 0 ETH on Arbitrum (transfer everything to Base)

The Problem:
├── To send ETH, you need ETH for gas
├── If you send all your ETH, you can't pay gas
├── If you keep gas, you can't send all your ETH
└── Result: Small amount always stranded

ZeroDust is the only solution that enables complete chain exits for native gas tokens.

✨ Features

How It Works

User connects wallet to ZeroDust
User selects source chain and destination (same-chain or cross-chain)
User signs ONE authorization (no gas needed)
ZeroDust sponsor executes the sweep
User receives funds on destination
Origin chain balance: EXACTLY ZERO

Supported Sweep Cases

Case	Description	Example
Cross-chain, same address	Exit to yourself on another chain	Arbitrum → Base (same wallet)
Cross-chain, different address	Exit to another wallet on another chain	Arbitrum → Base (different wallet)
Same-chain, different address	Consolidate to another wallet	Arbitrum → Arbitrum (different wallet)

Post-Condition (enforced on-chain): Source balance = exactly 0 wei

Supported Chains

Contract Address (same on all chains): 0x3732398281d0606aCB7EC1D490dFB0591BE4c4f2

ZeroDust is deployed on 26 mainnet chains with EIP-7702 support:

Chain	ID	Token	Chain	ID	Token
Ethereum	1	ETH	Sei	1329	SEI
Optimism	10	ETH	Astar zkEVM	1514	ETH
BSC	56	BNB	Soneium	1868	ETH
Gnosis	100	xDAI	Mantle	5000	MNT
Unichain	130	ETH	Kaia	5330	KAIA
Polygon	137	POL	Base	8453	ETH
Sonic	146	S	Plasma	9745	XPL
X Layer	196	OKB	ApeChain	33139	APE
Fraxtal	252	frxETH	Mode	34443	ETH
World Chain	480	ETH	Arbitrum	42161	ETH
Celo	42220	CELO	Redstone	57073	ETH
BOB	60808	ETH	Berachain	80094	BERA
Scroll	534352	ETH	Zora	7777777	ETH

Plus 46 testnets for development.

See contracts/README.md for explorer links.

🔧 Technical Details

Project Structure

zerodust/
├── contracts/          # Smart contracts (Foundry)
│   ├── src/
│   │   ├── ZeroDustSweepMainnet.sol   # Production contract
│   │   └── ZeroDustSweepTEST.sol      # Testnet contract
│   ├── script/
│   │   └── DeployMainnet.s.sol        # Mainnet deployment (CREATE2)
│   └── broadcast/                      # Deployment logs
└── docs/

Architecture

Contract Architecture

┌─────────────────────────────────────────────────────────────┐
│                        User's EOA                            │
│                   (EIP-7702 delegated)                       │
│                                                              │
│  ┌─────────────────────────────────────────────────────┐    │
│  │          ZeroDustSweepMainnet (bytecode)             │    │
│  │                                                      │    │
│  │              executeSweep(intent, sig)               │    │
│  │                        │                             │    │
│  │           ┌────────────┴────────────┐                │    │
│  │           ▼                         ▼                │    │
│  │    MODE_TRANSFER (0)         MODE_CALL (1)           │    │
│  │    Same-chain sweep          Cross-chain sweep       │    │
│  │           │                         │                │    │
│  │           ▼                         ▼                │    │
│  │    Transfer to              Call bridge target       │    │
│  │    destination              (callTarget + callData)  │    │
│  │                                     │                │    │
│  └─────────────────────────────────────┼────────────────┘    │
│                                        │                     │
└────────────────────────────────────────┼─────────────────────┘
                                         │
                                         ▼
                          ┌─────────────────────────┐
                          │     External Bridge     │
                          │       (Gas.zip)         │
                          │                         │
                          │   Delivers funds on     │
                          │   destination chain     │
                          └─────────────────────────┘

Security Model

No admin functions - Immutable after deployment
No upgradability - What you see is what you get
Unified SweepIntent - Single signed structure for all sweep types
Zero balance enforcement - Contract reverts if any balance remains
ERC-7201 storage - Prevents slot collisions with other EIP-7702 apps
Immutable sponsors - Stored in bytecode, not storage

Fee Structure

Service Fee: 1% of swept value, with $0.05 minimum and $0.50 maximum.

Total Fee = Gas Reimbursement + Service Fee + Bridge Fee (if cross-chain)

Examples:
- $5 balance → $0.05 fee (1% = $0.05, at min) → User receives ~$4.95
- $10 balance → $0.10 fee (1%) → User receives ~$9.90
- $60 balance → $0.50 fee (max) → User receives ~$59.50

📚 Documentation

contracts/README.md - Contract details and deployment
contracts/SPECIFICATION.md - Technical specification
contracts/DEPLOYMENT.md - Deployment guide

🔒 Security

ZeroDust is designed with security as the top priority:

No fund custody - All operations are atomic, single-transaction
User-controlled limits - maxTotalFeeWei and minReceive signed by user
Mandatory simulation - Every transaction simulated before execution
routeHash binding - Signature bound to specific bridge route (cross-chain)
Internal security review - 7 rounds, 16 issues identified and fixed
External audit - Pending (required before full launch)

📊 Status

Smart Contract: Deployed on 26 mainnets + 46 testnets

Contract Versions

Contract	Status	Features
ZeroDustSweepMainnet	Production	Unified SweepIntent, granular fees, sponsor model
ZeroDustSweepTEST	Testnet	Same as mainnet, for testing

Verified Mainnet Sweeps

Chain	Swept	TX
Base	$3.46 → 0	View
Arbitrum	$3.57 → 0	View
BSC	$2.25 → 0	View
Polygon	$7.55 → 0	View

See contracts/README.md for full deployment list.

Testnets NOT Supporting EIP-7702

The following testnets were tested and do not support EIP-7702:

Abstract, Lens, zkSync, Taiko, opBNB, Avalanche, Swell, Cyber, Boba, Metis, Fuse, Aurora, Flare, Vana, Corn, Rootstock, Apechain, IoTeX, Viction, XDC, Telos, Kava, EDU Chain, Gravity, Manta Pacific, Lightlink, Moonbase, Nibiru, Somnia, Rari, Blast, Xai, B3, Mezo, Chiliz, HashKey, Memecore

Note: Mainnet support may differ from testnet.