Back to Home

Forwarder

0xebf64adf55c6...ba65dabce574
ByzantiumSource VerifiedEdit this contract
Deployed June 27, 2018 (8 years ago)Block 5,861,790

Payment forwarder that sends every incoming payment to a receiver address and logs both ether and token movements with the contract as an explicit party.

Byzantium EraVerified Source

Historical Significance

Both events name this contract as a party rather than only the sender and receiver. For an operator running many forwarding addresses, that makes a single log stream enough to attribute a payment to the address it arrived at, without needing to join against a deployment list. Leaving the token sweep open to any caller is a deliberate trade: it costs nothing to let a stranger pay gas to move funds that can only ever go to the receiver.

Key Facts
Deployment Block
5,861,790
Deployment Date
Jun 27, 2018, 06:33 AM
Code Size
1.5 KB
Transactions by Year
20181

Description

The payable fallback transfers the full incoming value to the receiver held in the first storage slot and emits ethTransfer carrying the sender, this contract, the receiver and the amount. transferToken does the same job for an ERC20: it reads the contract's own balance, and if there is anything to move it transfers the whole balance to the receiver and emits tokenTransfer with the token address, this contract, the receiver and the amount.

updateReceiver is the only privileged function, gated on a second stored owner address, and it carries the revert reason only can be called by owner. transferToken itself is deliberately unguarded, so anyone can push a stranded token balance onward.

Source Verified

Solidityeh_crack_source_verified
Compiler: v0.4.24

Bytecode Overview

Opcodes1,581
Unique Opcodes147
Jump Instructions38
Storage Operations12

External Links