Back to Home

DepositForwarder

0x001c00432867...aa56ac0aa98b
Exact Bytecode MatchEdit this contract
Deployed September 14, 2017 (8 years ago)Block 4,273,780

Deposit forwarder that re-points itself at a new destination before forwarding.

Verified Source

Historical Significance

Self updating deposit addresses solved a real problem for operators, who could not change an address already handed out to a customer. Putting the pointer refresh in the deposit path meant every incoming payment paid for the check, and the thousand gas cap on the forwarding call left very little room for the receiver to do any work.

Key Facts
Deployment Block
4,273,780
Deployment Date
Sep 14, 2017, 05:15 PM
Code Size
400.0 B
Transactions by Year
20172

Description

A deposit address that keeps its destination up to date on its own. Before forwarding anything it asks the current destination for a replacement through getUpgradeAddress(), and stores the answer when it is not the zero address. It then calls deposit(address) on the destination with the sender's address and the ether received, capped at a thousand gas. tryUpgrade() exposes the same refresh step so it can be triggered without sending funds. The runtime code matches the deployed bytecode byte for byte. Only the trailing swarm metadata hash differs, because the EthereumHistory attribution comment changes the source text. Sourcify records this as a partial match and Etherscan shows it as verified.

Source Verified

SolidityExact bytecode match(400 bytes)
Compiler: v0.4.7+

Bytecode Overview

Opcodes400
Unique Opcodes98
Jump Instructions20
Storage Operations6

External Links