A 22 byte self-destructing holding contract, the shortest of its family because the controller address happens to start with a zero byte.
Historical Significance
A vanity address earning back its own mining cost. Addresses with leading zeros were sought for the calldata discount they gave, and here the same leading zeros let a hand written contract be deployed five bytes cheaper every time it was used. Deployed in bulk that is a real saving, and it shows the author counting bytes at a level most tooling never exposes.
Key Facts
Description
Functionally identical to its 27 byte 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.
This one is five bytes shorter for a reason that has nothing to do with the logic. The controller address begins with leading zero bytes, so the author pushed it with a shorter PUSH instruction instead of the full twenty byte form. The saving is a property of the address, not of the code.
Source Verified
Byzantium Era
First Metropolis hard fork. Added zk-SNARK precompiles, REVERT opcode, and staticcall.
Bytecode Overview
Verified Source Available
This contract has verified source code.
View Verification ProofShow source code (Yul)
// Submitted by EthereumHistory (ethereumhistory.com)
//
// 22 byte hand-written EVM assembly. Only one hardcoded address may call it,
// after which the contract self-destructs and sends its balance to that caller.
// The address is pushed with PUSH15 rather than PUSH20 because its leading zero
// bytes can be dropped, which saves five bytes on every deployment.
object "Guarded" {
code {
datacopy(0, dataoffset("Guarded_deployed"), datasize("Guarded_deployed"))
return(0, datasize("Guarded_deployed"))
}
object "Guarded_deployed" {
code {
verbatim_0i_0o(hex"6e7f6202ba718df41ec639b32dd7fbcf3318585733ff")
}
}
}