Back to Home

Recovered

0x00049d181b68...6aa253de1d99
ByzantiumFailed DeploySource VerifiedEdit this contract
Deployed December 7, 2018 (7 years ago)Block 6,842,756

Small guard contract that self-destructs to its controller and refuses every other caller.

Byzantium EraVerified Source

Historical Significance

The address is pushed with PUSH17 or PUSH18 rather than PUSH20 because the operator mined a factory address beginning with several zero bytes, which can then be dropped from the push. Saving three bytes matters when the same contract is deployed hundreds of thousands of times.

Token Information
Decimals
0
Key Facts
Deployment Block
6,842,756
Deployment Date
Dec 7, 2018, 01:08 PM
Code Size
Unknown

Description

A guard of 24 bytes. It compares the caller against one address compiled into the code and, on a match, self-destructs and sends the balance to that caller. Any other caller hits an invalid jump and the transaction reverts. The comparison is done with raw arithmetic and the jump target is taken from an opcode that happens to push a suitable value, tricks a compiler would never emit. This contract self-destructed inside the transaction that created it, so a node returns empty code for it at every block. The bytecode here was recovered from the creation trace and checked against the index record for the group, so it is the real deployed code rather than a reconstruction. No public verification registry will accept a contract that no longer has code on chain, so the source is published here instead of on Sourcify or Etherscan.

Source Verified

Soliditysource_recovered_self_destructed0
Compiler: v0.8.17

Bytecode Overview

Opcodes0
Unique Opcodes0
Jump Instructions0
Storage Operations0

External Links