Back to Home

Spender

Unclassified
0x0e7fc85094f1...c9f5575545a0
ByzantiumSource VerifiedEdit this contract
Deployed June 3, 2018 (8 years ago)Block 5,725,923

Two-key holding contract with the owner burned into the code as a constant and a rotatable spender key for day to day payouts.

Byzantium EraVerified Source

Historical Significance

The split is the point. A hot spender key signs the routine payouts and can be replaced the moment it is suspected, while the cold owner key exists only in the bytecode and is needed exactly once per rotation. Putting the owner in code rather than storage also means it survives any storage corruption and is visible to anyone reading the contract, which is a deliberate transparency choice rather than an oversight.

Key Facts
Deployment Block
5,725,923
Deployment Date
Jun 3, 2018, 03:52 PM
Code Size
737.0 B
Gas at Deploy
267,876

Description

The owner is a compile time constant rather than a storage value, so it costs nothing to read and cannot be changed after deployment. Only that address may call setSpender, which writes the single storage slot.

Everything else answers to the spender. send forwards ether to any address and sendTokens moves an ERC20 balance, both reverting if the caller is not the current spender. The payable fallback accepts ether without conditions.

Source Verified

Solidityeh_crack_source_verified
Compiler: v0.4.24
Heuristic Analysis

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

Detected Type: Unclassified

Bytecode Overview

Opcodes737
Unique Opcodes134
Jump Instructions46
Storage Operations5

External Links

Related contracts