Contract 0x0001414bb135...e22782106902

The UserWallet is an exchange deposit wallet pattern deployed across large-scale exchange infrastructure in mid-2017. Each user depositing to an exchange receives their own dedicated contract instance, with the exchange hot wallet set as owner at construction time.

Incoming ETH triggers the payable fallback function, which emits a Deposit(sender, value, value) event with both sender and value as indexed parameters — enabling efficient off-chain event log filtering for the exchange to detect and credit incoming deposits without scanning all transactions.

The owner has three operational functions: collect() transfers all accumulated ETH to the owner address; collectToken(token, to, amount) sweeps ERC-20 tokens by calling the token contract directly via raw bytes4(0xa9059cbb) encoding of the transfer selector; and kill() selfdestructs the contract, forwarding any remaining ETH to owner.

This architecture — one contract per deposit address — was a common pattern among exchanges in 2017 before more efficient multicall and proxy patterns emerged. The raw .call() approach for ERC-20 sweeping predates the standardized SafeERC20 wrappers and reflects the tooling available at the time of deployment.

Source verification achieved with Solidity 0.4.11+commit.68ef5810 (optimizer ON). The reconstructed bytecode is 554 bytes vs 553 bytes on-chain — a 1-byte difference in the LOG3 event encoding sequence attributable to optimizer stack scheduling non-determinism in early Solidity releases.