Back to Home

Forwarder

Unclassified
0x00059ab2761f...cb2fed22e947
ByzantiumSource VerifiedEdit this contract

Bytecode verified via sibling

This contract shares identical runtime bytecode with a verified contract (0xedbcd93a...) which has been verified through compiler archaeology.

Deployed November 8, 2018 (7 years ago)Block 6,666,527

Deposit forwarder that requires a non-zero payment and routes it through an internal function to a stored wallet address.

Byzantium Era

Historical Significance

Rejecting zero value payments keeps the deposit log clean: without that check, anyone could produce an endless stream of zero amount forwards. Keeping the owner and the payout wallet as separate stored values is the other notable choice, letting a cold wallet receive funds while a different key retains the ability to recover tokens sent by mistake.

Key Facts
Deployment Block
6,666,527
Deployment Date
Nov 8, 2018, 01:32 PM
Code Size
940.0 B
Gas at Deploy
352,457

Description

The payable fallback requires the incoming value to be greater than zero, then calls an internal helper that transfers the whole amount to the wallet address held in the second storage slot. Splitting the transfer into its own internal function rather than inlining it leaves a distinct jump in the compiled code and suggests the forwarding step was written to be called from more than one place at some point.

transferERC20 is owner gated and moves a chosen token amount to a chosen address. Both the owner and the wallet are readable, and they are separate values, so the address that receives deposits need not be the address that controls the contract.

Heuristic Analysis

The following characteristics were detected through bytecode analysis and may not be accurate.

Detected Type: Unclassified

Bytecode Overview

Opcodes940
Unique Opcodes108
Jump Instructions37
Storage Operations4

External Links

Related contracts