Understanding Transaction Data
Why your wallet shows HEX data
When selling tokens through RateVault, your wallet (MetaMask, Rainbow, etc.) will display complex transaction data in hexadecimal (HEX) format. This is expected behavior and necessary for the protocol to function correctly.
💡 What You'll See
Your wallet will show something like:
This is completely normal and does not indicate any problem.
Why HEX Data?
The transaction data contains encoded swap routing instructions that tell the DEX aggregator (0x or ODOS) exactly how to execute your trade across multiple liquidity sources to get you the best price.
Data Contents
The HEX data includes:
- •Token addresses: Your sell token and ETH (buy token)
- •Amounts: Exact tokens to sell and minimum ETH to receive
- •DEX routes: Which liquidity pools to use (Uniswap, SushiSwap, etc.)
- •Split percentages: How to divide the trade across multiple pools
- •Slippage protection: Maximum price movement parameters
- •Protocol fees: RateVault's 1% fee calculation
Why Can't Wallets Decode It?
MetaMask and other wallets cannot display this data in human-readable format because each DEX aggregator (0x, ODOS) uses its own proprietary encoding scheme for routing instructions. The complexity is what enables these aggregators to find optimal prices across dozens of liquidity sources.
Example Routing
A single swap might be routed like this:
All of this routing logic is encoded in the HEX data.
Safety Guarantees
✓ Contract-Level Protection
Even with complex routing data, the vault contract enforces strict safety rules:
- • Only whitelisted aggregators can execute swaps (0x, ODOS)
- • Daily limits are enforced regardless of routing complexity
- • Cliff periods cannot be bypassed
- • Only the beneficiary can initiate sells
- • ETH always goes to the beneficiary address
- • All transactions are atomic (complete fully or revert)
Verifying Transactions
Once a transaction is confirmed, you can verify all details on Etherscan. The vault contract is verified, allowing you to see decoded function calls and parameters.
On Etherscan You Can See:
- 1.Function: "sell" - confirms it's a legitimate vault sell
- 2.Token Transfers: Exact amount of tokens sold
- 3.ETH Received: Total ETH from the swap
- 4.Protocol Fee: 1% fee sent to protocol
- 5.Beneficiary Payment: Remaining ETH to your wallet
Common Questions
Is this a security risk?
No. The HEX data is routing instructions for legitimate DEX aggregators. The vault contract only allows calls to whitelisted, audited contracts (0x, ODOS). You cannot be tricked into approving malicious transactions.
Can I avoid the HEX data display?
No. This is how DEX aggregators work at a fundamental level. The complexity is what enables optimal pricing across dozens of liquidity sources. Modern wallets like MetaMask show this by design for transparency.
Should I verify the transaction destination?
Yes, always check that the transaction is going to your vault address. This is shown clearly at the top of the MetaMask confirmation dialog. The "To:" field should match your vault address from the detail page.
What if I'm still concerned?
Start with a small test transaction. Execute a minimal sell to verify the process. Check the Etherscan transaction details to confirm everything worked as expected. Then proceed with larger amounts.