Doom on Robinhood (@DoomOnRh) header
Doom on Robinhood (@DoomOnRh) profile picture

DOOM (1993) stored as the runtime code of 23 contracts on Robinhood Chain first time. The chain reassembled it and hashed it itself.

Robinhood
Joined June 2026
Photo by Doom on Robinhood (@DoomOnRh)Photo by Doom on Robinhood (@DoomOnRh)
DOOM is a contract on robinhood chain now The whole 1993 shareware game, stored as the runtime code of 24 contracts on Robinhood Chain and the chain reassembled every byte and hashed it itself. ca: 0x867dabe089ebc72086c13fd3dcdf04da44d9421d doomonrh.fun/
5
1
6
789
The game is sealed, ownerless and finished. The token will do whatever tokens do. The 24 contracts holding DOOM cannot be told it exists.
1
33
This is DOOM running out of contract bytecode on @RobinhoodCrypto Chain. The whole 1993 game is stored as the code of 24 contracts. The page reads every byte off the chain, one eth_getCode at a time, then runs it. Nothing cached. No server of ours.
8
1
9
392
If you think DOOM belongs in a state trie, a repost is what gets the next person to see it.
2
37
If you think DOOM belongs in a state trie, a repost is what gets the next person to see it.
2
29
Is this the first game stored in, and run out of, contract bytecode on Robinhood Chain?
4
58
A contract's runtime code is just bytes in the state trie. Put a STOP at the front calling it halts before your data and the rest is storage every node carries, rent-free, readable with EXTCODECOPY. Robinhood Chain stores 98,304 bytes in a contract. Its sequencer accepts 95,000 in a transaction, and a payload has to be sent before it can be stored. Hence 24.
1
1
109
Anyone can put a file on a blockchain. This is the one where the blockchain checked it. 0xb1fb5cec7afda91d101ce6a939ed4d02801025a8357615c0b3ca230991d571c2 seal() rehashed 2,241,676 bytes in the EVM and matched the digest published before launch. 11,033,615 gas.
2
97