Home · About

About RocketXInfo

Play, but responsibly!

What RocketXInfo is

RocketXInfo is a site with detailed, independent information about the crash game Rocket X and the crash-game genre in general. We are not a casino operator, and we do not accept bets.

The project's main goal is to help the reader make informed decisions. Crash games are a legal entertainment product that adults who understand what they're doing have the right to play. The problem is that a large fraudulent industry has grown up around this product — fake "signals," APK trojans, "strategies" with promises of a "guaranteed win." This industry preys on people who don't understand the technical fundamentals of the game.

We write materials after which the reader understands: how Rocket X works technically, why "signals" are mathematically impossible, what RTP is and why it makes a long-term win impossible, where the boundaries between entertainment and addiction lie, and where to turn for help if the game has gotten out of control.

Editorial principles

Six principles we follow when preparing every piece on the site.

  1. No promises of winning. Crash games have a negative expected value; over the distance the player loses money. This is a basic fact that we repeat where appropriate.
  2. Technical claims are verified computationally. If a piece contains a formula or script, it actually works. For example, the Python Provably Fair verification script from the RNG article was tested on test data.
  3. Sources are cited. When it comes to specific facts (game release dates, developer names, help-service contacts), this data is taken from public sources and periodically re-checked.
  4. Sensitive topics — without pressure. The section on gambling addiction is written in a calm, non-moralizing tone. The goal is to provide information and help contacts, not to talk someone into "quitting gambling."
  5. Help contacts are kept current. Helpline numbers, help-service websites, Gamblers Anonymous contacts — all of this is periodically re-checked. If you find outdated information, write to us.
  6. Acknowledging limitations. If we don't know the exact answer, we say so. If a formula, for example, isn't published in full by the provider, that's stated explicitly. An honest "we don't know" is better than invented specifics.

Where we get our data

The information on the site draws on several categories of sources.

Official developer websites

smartsoftgaming.com, spribe.co, 1win.gaming, gamingcorps.com — for up-to-date data on developers, game release years, RTP, licenses. These sources are commercial in nature, but on the factual side (dates, names, figures) they're usually reliable.

Documentation from regulators and audit labs

Curaçao eGaming, Malta Gaming Authority, UK Gambling Commission — for information on licenses. eCOGRA, GLI, iTech Labs, BMM Testlabs — for information on RNG certification.

Academic work

For topics in behavioral economics and the psychology of addiction, we rely on the classic works of Kahneman and Tversky (prospect theory), on DSM-5 and ICD-11 (classifications of mental disorders), and on publications in the journals Journal of Gambling Studies and Addiction.

Cryptographic standards

For the Provably Fair breakdown — the SHA-256 specifications (NIST FIPS 180-4), HMAC (RFC 2104), and the source code of reference crash-game implementations (Bustabit, BC Originals).

Threat intelligence from specialized companies

For the breakdown of Android banking trojans and related fraud schemes — public reports from Group-IB, Kaspersky Lab, Securelist, F-Secure, ESET. These sources document specific trojan families (Cerberus, Anubis, Hydra, Octo, Coper) and their techniques.

Help-service contacts

Checked directly against the organizations' own websites: gamcare.org.uk, gamblersanonymous.org, gamblingtherapy.org, begambleaware.org, gam-anon.org. They're re-checked periodically via web search to make sure the numbers and hours are current.

Feedback

If you have:

  • A note on the factual accuracy of a piece
  • Information about outdated help-service contacts
  • A recent case of a scam scheme worth writing about
  • Personal experience as someone affected that you're willing to share (anonymously)
  • A suggestion for a new article topic
  • A report of a bug on the site

Write to:

Editorial contact

Email: editor@rocketxinfo.example

Emails are read by the editorial team. The anonymity of messages is respected — if you share personal experience, your name and contact details will not be published without your explicit consent.

We especially value:

  • Experience from people affected by scam channels and APK predictors — it helps make our pieces real rather than theoretical.
  • Notes on the technical sections from people with a background in cryptography, information security, statistics.
  • Help from professional psychologists and addiction specialists — where we might unintentionally smooth over or oversimplify.

Common questions about the project

You can — with a link to the source. All texts on the site are written by the editorial team and belong to the RocketXInfo project. When reprinting in full or in part, credit the author (RocketXInfo) and include an active link to the original. This applies especially to the technical sections: the Provably Fair breakdown with the Python verification script, the EV calculations for different strategies, the tables of house-edge levels. These materials are the result of real work, and it would be proper to cite the source.
This is the English edition of the project. RocketXInfo began as an independent Russian-language resource — in Russian there was almost no independent material on the topic, only casino promotion and scam channels, while in English it was already well covered by international resources like GamCare and BeGambleAware. Filling that Russian-language gap is what the project originally set out to do. This English edition makes the same technical and harm-reduction material available to an English-speaking audience, and other languages may follow if there are resources for it.
Every claim in our pieces goes through three levels of checking: 1) a primary source — official developer websites, regulator documentation, academic work on cryptography or behavioral economics; 2) cross-checking against at least two independent sources; 3) a re-check before publication via web search to make sure the data is current. Technical claims (RNG formulas, statistical calculations) are verified computationally — for example, the verify.py script from "How the RNG works" actually runs and was tested on test data.
Yes. The existing 11 pages are a basic framework that covers all the key topics. As data is updated and new material appears (new scam schemes, regulatory changes, new versions of Rocket X or other crash games), the sections will be expanded. We also plan to go deeper on specific topics: a detailed breakdown of individual strategies, cases of affected people with an analysis of what went wrong, a more detailed Fail2Ban guide for those who want to protect their server. If you'd like to suggest a topic, write to the editorial team.