Back to Home

UserWallet

0x6e00977f0576...16ee1cea460a
ByzantiumSource VerifiedEdit this contract
Deployed October 27, 2018 (7 years ago)Block 6,593,004

Deposit wallet with an ERC-223 receive hook, routing token sweeps through a shared sweeper registry by delegatecall.

Byzantium EraVerified Source

Historical Significance

Adding tokenFallback is a small change with a real consequence: without it, an ERC-223 token transfer to this address reverts, and a customer's deposit simply fails. It is a record of the brief period when ERC-223 looked like it might displace ERC-20, and of the cost that fell on anyone operating deposit addresses at scale, who had to redeploy their whole fleet to accept a standard that never took hold.

Token Information
Decimals
0
Key Facts
Deployment Block
6,593,004
Deployment Date
Oct 27, 2018, 12:04 PM
Code Size
690.0 B
Transactions by Year
20182

Description

The sweeper list address is fixed at construction and is the only thing in storage. The payable fallback is empty, so the address behaves like a plain account for incoming ether.

tokenFallback exists for ERC-223 tokens, which refuse to transfer into a contract that does not implement it. The body does nothing except read its three parameters, a deliberate no-op written that way to silence the unused-parameter warning while keeping the function present in the ABI.

sweep asks the registry which sweeper handles the named token, then delegatecalls it with the calldata it received, so the sweeping logic executes against this wallet's balances. The amount parameter is likewise read and discarded here, because the sweeper reads it out of the forwarded calldata instead.

Source Verified

Solidityeh_crack_source_verified
Compiler: v0.4.23

Bytecode Overview

Opcodes690
Unique Opcodes97
Jump Instructions22
Storage Operations2

External Links