Back to Home

UserWallet

0xe37d265902e2...cce59ea9e29b
ByzantiumSource VerifiedEdit this contract
Deployed November 30, 2018 (7 years ago)Block 6,800,939

Exchange deposit wallet that reports every incoming payment to a logger contract and routes token withdrawals through a sweeper registry.

Byzantium EraVerified Source

Historical Significance

The logger is the part worth noticing. Emitting the deposit from a single shared contract rather than from each wallet means an exchange can watch one address for every customer deposit across its whole fleet, instead of subscribing to thousands of individual addresses. That is a practical answer to a real operational problem of the period, and it is why this design kept being redeployed.

Token Information
Decimals
0
Key Facts
Deployment Block
6,800,939
Deployment Date
Nov 30, 2018, 02:40 PM
Code Size
702.0 B

Description

Two addresses are fixed at construction: a sweeper list and a logger. The payable fallback does no accounting of its own; it calls logIncoming on the logger with the sender, its own address, the block number and the value. The record lives in the logger's events rather than in this contract's storage, so the wallet itself stays a few hundred bytes no matter how many deposits it sees.

withdraw asks the sweeper list which sweeper handles a given token and delegatecalls it with the original calldata, so the sweeping code runs against this wallet's balances while living in one shared contract. tokenFallback is present and empty, which is what an ERC-223 token needs to see before it will transfer in.

The fallback records but does not forward. Ether accumulates in the wallet until a sweeper moves it, which is why the logger is given the block number: an operator reconciling deposits needs to know when each one landed, not just that it did.

Source Verified

Solidityeh_crack_source_verified
Compiler: v0.4.24

Bytecode Overview

Opcodes702
Unique Opcodes106
Jump Instructions25
Storage Operations7

External Links