Back to Home

Bot

0x9107a6ed55bd...5883dcece39b
ByzantiumSource VerifiedEdit this contract
Deployed August 9, 2018 (8 years ago)Block 6,117,460

Fomo3D automation: one call spawns a throwaway contract that buys keys and withdraws winnings in a loop, then selfdestructs back to the sender.

Byzantium EraVerified Source

Historical Significance

Fomo3D's design rewarded whoever could act fastest and most often, and contracts like this are what that incentive produced: a disposable agent that compresses many rounds of play into a single transaction and leaves nothing on chain to clean up. Creating and destroying a contract inside one transaction was also, at the time, a gas refund, so the loop partly paid for itself. The five hardcoded operator addresses are the whole access-control model.

Token Information
Decimals
0
Key Facts
Deployment Block
6,117,460
Deployment Date
Aug 9, 2018, 04:59 PM
Code Size
643.0 B

Description

execute takes the game address, an affiliate code and a repeat count, and is gated on tx.origin matching one of five operator addresses burned into the code. If it matches, the contract deploys a child and forwards the entire incoming value to it.

The child is where the work happens, and it never outlives its own construction. Its constructor loops count plus one times; each pass calls buyXid on the game with the contract's balance and the affiliate code, then calls withdraw to pull back whatever the game has credited. Both are raw calls with the results ignored, so a failed round does not stop the loop. When the loop ends the child selfdestructs to the transaction origin, which returns the balance in the same transaction that created it.

Nothing is stored anywhere. The child has no functions, no owner and no lifetime; it exists only inside one transaction, which is exactly what makes the pattern cheap to repeat.

Source Verified

Yuleh_crack_source_verified
Compiler: v0.8.17

Bytecode Overview

Opcodes643
Unique Opcodes149
Jump Instructions20
Storage Operations3

External Links