lossporn| look yourself up| how a loss is counted| the vault| verify| @losspornlol

Mod log: the files that decide every number, and their hashes

A loss is only worth reading if the code that computed it cannot be quietly edited to be kinder or crueler. Below is the SHA-256 of every file that produces a number on this site, pinned when the current snapshot was built. Press the button and your browser fetches each file and hashes it live. The hasher is sha256.js, written from scratch so you can read it too.

FileWhat it decidesPinned SHA-256Live

From a terminal, in the project folder, with no server:

sha256sum app/loss.js app/chain.js data/eth-usd.json data/tokens.json data/snapshot.json data/build.mjs

And the deepest check, which is the point of the whole thing: take any wallet the site has shown you and recompute it yourself.

node data/build.mjs --wallet 0x…

Same wallet, same price table, same worst exit, same hash of the transaction. If the terminal ever disagrees with the site, the site is wrong.

If every row says "serve over http", you opened the file directly and browsers block fetch from file://. Run python -m http.server 3015 in the folder and open it over http, or use the terminal commands above.

r/losspornpost your loss how a loss is countedverifythe vault@losspornlol every number on this page came from the chain and can be recomputed by anyone · π