Back to Home

ShapeShift Chain-Split Receiver

utility
0x89afcc1452d4...fc0691a51456
DAO ForkContract #21KExact Bytecode MatchEdit this contract
Deployed July 26, 2016 (9 years ago)Block 1,957,039

ShapeShift ETH/ETC routing contract (Jul 26, 2016). Twin instance of the ShapeShiftReceiver — identical bytecode, configured for the opposite chain fork state.

DAO Fork EraVerified Source

Historical Significance

Twin to 0x3e7756, demonstrating ShapeShifts dual-chain deposit routing architecture. The pair represents the first known use of an external chain oracle to automatically segregate ETH and ETC deposits at the smart contract level.

Context

The pair of ShapeShiftReceiver contracts (0x3e7756 and 0x89afcc) were deployed in blocks 1,957,038 and 1,957,039 -- consecutive blocks, within seconds of each other. This mirrors the dual-chain problem they solve: two chains, two receivers, one oracle.

Key Facts
Deployment Block
1,957,039
Deployment Date
Jul 26, 2016, 05:39 PM
Code Size
287.0 B
Gas at Deploy
176,585
Transactions by Year
20162

Description

Deployed July 26, 2016 — 6 days after the DAO hard fork. Twin instance of 0x3e7756, deployed in the immediately following block by the same ShapeShift ETH wallet. Identical 287-byte bytecode, configured with forked=false for the ETC chain routing (where forked() oracle returns false). Together with its sibling, the ShapeShiftSplit contract, and the earlier 94-byte forwarder, these represent the first on-chain smart contract infrastructure deployed by ShapeShift.

Source Verified

SolidityExact bytecode match(287 bytes)
Compiler: solc v0

Identical bytecode to 0x3e7756b1 (287 bytes). Same source, same compiler, different constructor arguments.

Heuristic Analysis

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

Detected Type: utility

Bytecode Overview

Opcodes287
Unique Opcodes57
Jump Instructions16
Storage Operations7

External Links