A 27 byte hand-written contract that self-destructs to its caller, gated on a single hardcoded controller address.
Historical Significance
Two families share this design with different controllers, which is what makes it legible: the code is a template, and the address is the parameter. That pattern of deploying one hand-tuned routine many times with a single constant changed is characteristic of automated deposit and collection systems from this period.
Key Facts
Description
The same twenty-seven byte guard shape as its sibling family, differing only in the twenty bytes of the permitted address. The controller 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 contract has no storage, no functions and no events. It exists to hold a balance and to hand that balance to one address on demand. The published source reproduces the deployed bytes exactly through Yul verbatim, because no compiler emits this shape.
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)
//
// 27 byte hand-written EVM assembly. Only 0x653bc9842cb54fa5454645be2eed7265f9fb9523 may call it.
// The caller is compared by XOR and a PC based jump, then the contract
// self-destructs to the caller. No Solidity compiler emits this shape, so the
// deployed bytes are reproduced exactly with Yul verbatim.
object "Guarded" {
code {
datacopy(0, dataoffset("Guarded_deployed"), datasize("Guarded_deployed"))
return(0, datasize("Guarded_deployed"))
}
object "Guarded_deployed" {
code {
verbatim_0i_0o(hex"73653bc9842cb54fa5454645be2eed7265f9fb95233318585733ff")
}
}
}