Back to Home

Guarded

0x000205cbfd51...372c6295a76f
ByzantiumFailed DeploySource VerifiedEdit this contract
Deployed December 11, 2018 (7 years ago)Block 6,869,203

A 27 byte self-destructing holding contract, gated on its deployer, recovered after every deployment had already destroyed itself.

Byzantium EraVerified Source

Historical Significance

Self-destructed contracts normally leave nothing but an address and a hash. This family is recoverable because it was a template deployed repeatedly with one address substituted, and because a hash of the original runtime was captured while the code still existed. That combination, a known shape plus a surviving hash, is the only reliable way to bring back code that no longer exists anywhere on the chain.

Token Information
Decimals
0
Key Facts
Deployment Block
6,869,203
Deployment Date
Dec 11, 2018, 09:31 PM
Code Size
Unknown

Description

The same hand written guard shape as its surviving siblings: the permitted address is pushed as a literal, compared against the caller, and a jump on that comparison either reaches the self-destruct or falls into an invalid instruction. The permitted address is the deployer of every contract in this family.

Nothing in this family still has code on chain. The runtime was reconstructed from the guard template with the deployer's address substituted, and confirmed by hashing the candidate and matching it against the bytecode hash recorded for the family before the contracts were destroyed. Because there is no deployed code left to compare against, no verification registry can accept it; the source is published here with the reconstruction stated openly.

Source Verified

Yulsource_recovered_self_destructed0
Compiler: v0.8.17

Bytecode Overview

Opcodes0
Unique Opcodes0
Jump Instructions0
Storage Operations0

External Links