This pool resolves on the day it is first publicly reported that Rockstar Games (or Take-Two) has identified the individual or group behind CyberLeek.
A report by a named news organization with an editorial masthead, or an official statement by Rockstar, Take-Two, or a law enforcement agency. Social media posts, forum claims, and anonymous sources do not count on their own.
At least three independent reports, or one official statement.
A named individual, a criminal charge, an arrest, or a lawsuit filed against a named defendant. "Under investigation" is not identification.
The day the first qualifying report was published, in UTC — not the day the third one appears.
Whether leaks continue afterwards does not affect this resolution. Whether the site stays online does not affect it.
Links to each qualifying report are published at https://cyberleekwasted.com/log with archive snapshots.
If the condition is not unambiguously met by 2027-03-26 UTC, the pool refunds every stake in full. Ambiguity resolves to refund, never to a judgment call.
The hash below is the SHA-256 of one file: the rule as plain bytes, served at /rules.txt. This page is a rendering of that file, not a second copy of the text.
curl -s https://cyberleekwasted.com/rules.txt | sha256sum # macOS, which has no sha256sum: curl -s https://cyberleekwasted.com/rules.txt | shasum -a 256
sha256:fa3bde494c10e507d8cb590a037ddf324e02636c2d6830a45408ca4d2f0b0980
Compare what that prints against the hash above, and against the sha256: inside the pool's question on chain. All three are the same number, or something is wrong.
A commitment you cannot check is decoration. That is why the file is served exactly as it is hashed — no templating, no framework, nothing rewritten — and why checking it is one command rather than instructions for reassembling the text yourself.