Back to Home

TheLuckyOne

Unclassified
0x4e45f2f7707c...e3f730e259a8
FrontierContract #1,722Exact Bytecode MatchEdit this contract

Bytecode verified via sibling

This contract shares identical runtime bytecode with TheLuckyOne (0x2adfc2fe...) which has been verified through compiler archaeology.

Deployed October 2, 2015 (11 years ago)Block 320,658

On-chain lottery from October 2015. Players buy tickets (1-25+ ETH with bulk discounts) in rounds of 1,000. Winners selected via combined server seed, client en

Frontier EraVerified Source
Key Facts
Deployment Block
320,658
Deployment Date
Oct 2, 2015, 04:19 AM
Code Size
3.0 KB
Gas at Deploy
845,041

Description

TheLuckyOne was a lottery contract deployed on October 1, 2015 (block 310,456). Players purchased tickets by sending 1 ETH each, with tiered pricing for bulk purchases. After 1,000 tickets were sold per round, the winner was determined using a three-source entropy scheme: a pre-committed server seed (commit-reveal), a rolling client seed built from SHA3 hashing every ticket purchase, and a future block hash.

The contract included an important player protection mechanism: if the server operator failed to reveal the winning seed within 24 hours (the TIMEOUT constant), any player could call recoverLostFunds() to return ETH to all ticket holders. This addressed a common criticism of early on-chain lottery designs where operators could simply abandon the game after seeing an unfavorable outcome.

The contract also featured adminWithdraw() for the operator to claim excess funds while keeping enough to cover pending payouts, and a public sha3clone() helper that allowed anyone to independently verify seed hashes.

The contract currently holds 56.83 ETH, suggesting the final round never completed and the timeout recovery mechanism was never triggered by players.

Source Verified

SolidityExact bytecode match(3,065 bytes)
Compiler: soljson

Exact byte-for-byte match achieved via getter subroutine reorder proof. Source compiled with soljson v0.1.3+commit.028f561d produces identical bytecode when getter subroutines are rearranged to match native-build ordering. All 14 getter bodies are byte-identical, only their position in the bytecode differs due to C++ memory allocator differences between Emscripten and native builds.

Heuristic Analysis

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

Detected Type: Unclassified

Bytecode Overview

Opcodes3,065
Unique Opcodes189
Jump Instructions124
Storage Operations67

External Links

Related contracts