RecheBotGiveaways

Public guide

How RecheBot giveaways work

This page explains how to enter RecheBot's CS2 skin giveaways, what information is published and what can be checked afterwards.

Quick summary

  1. When a giveaway is created, the bot generates a secret random seed and publishes only its fingerprint (hash). This is an upfront randomness commitment.
  2. You enter from the giveaway message on Discord with the Enter button.
  3. When it ends, the bot stops accepting entries, reveals the seed and picks the winners from that seed and the eligible entries.
  4. You can check that the revealed seed matches the published hash. Repeating the selection takes more than that check.
  5. The server team delivers prizes manually through Steam. RecheBot does not send trade offers or control a Steam account.

Entering from Discord

Open the giveaway message in the server and press Enter. Entry is free. Depending on what the server team has configured, each giveaway may require a role, a minimum time in the server, verifying Steam by signing in, or a minimum Steam account age.

In new giveaways, each entry has exactly one ticket. Older giveaways may show more than one ticket per participant: they come from a bonus ticket feature that has since been retired, and they are kept as they were so those giveaways remain verifiable. The same Discord account cannot win the same giveaway twice.

The one entry per Steam account rule is optional. When the server team turns it on, it requires linking and verifying the Steam account by signing in to Steam, and it rejects another entry with the same verified SteamID. This limits that specific case, but on its own it does not prove that a person has only one Discord account, nor does it stop every attempt to use multiple accounts.

Seed and randomness commitment

Before any participant list exists, RecheBot generates a random seed and computes seedHash = sha256(seed). The hash is published in the giveaway message and on its transparency page. The seed stays hidden until the giveaway ends.

At the end, the seed is revealed. Checking that sha256(seed) matches the published hash verifies the commitment: the revealed seed is the same one that was fixed before the participant list was known. That check alone does not repeat the choice of winners.

The selection uses a deterministic sequence based on SHA-256, with no modulo bias, and draws winners without replacement. Reproducing it requires the seed, the same order of eligible entries and the weight of each one. Entries are sorted by entry time and Discord ID. When the giveaway closes, the required role and the minimum time in the server are checked again, and anyone who has left the server is excluded. Steam requirements are checked when entering. Verifying the hash and reproducing the selection are separate checks. If staff replace a winner with a reroll (for example, because they do not reply), the replaced winner stays visible on the page marked as replaced, and the new winner is drawn from the remaining eligible participants with a new seed that was not committed in advance.

Giveaway states

  • Active: accepts entries until its closing time.
  • Ended: no longer accepts entries. The seed is public and the bot completes the selection, or retries it if a transient failure occurred.
  • Cancelled: cancelled while it was active; no winners are picked.

Closing and storing the result are done so that a restart or a retry never draws again winners that were already saved. There may be no winners if no eligible entry remains at closing time.

Prize delivery

After the selection, the bot tries to send the winner a direct message with instructions to save their Steam Trade URL. It can also be saved with the /trade-url command. That URL is used to receive the offer and is treated as private information: it does not appear on the transparency page or in public listings.

The server team sends the trade offer manually from Steam and, when appropriate, marks the delivery on Discord. The bot does not automate trades. Do not share your Steam credentials with anyone; the delivery process does not need them.

What public transparency shows

The detail page shows the state, the committed hash, the seed when applicable, the entries with their public Discord IDs, their tickets and entry time, plus the current winners. It does not publish Trade URLs or other private Steam data.

If someone asks for their data to be deleted, their entries in active giveaways are removed. In giveaways that have already closed, their entry is kept so the selection stays reproducible, but their ID is shown as [deleted].

  1. Open the transparency link from the Discord message.
  2. Write down the hash published when the giveaway was created.
  3. Once it has ended, check that the fingerprint of the revealed seed matches that hash.
  4. Review the entries, their tickets and the applicable requirements.
  5. If you want to reproduce the selection, use the seed, the sorted eligible entries and the same algorithm. Do not confuse this reproduction with verifying the hash.

Public routes

  • A server's published active giveaways: /sorteos?guild={server}
  • Details and transparency of a published giveaway: /sorteos/{id}
  • This documentation: /docs/sorteos?lang=en

There is no combined list of every server: each server shares the link to its own giveaways page. These routes are read-only and do not require signing in to Discord. Add ?lang=en or ?lang=es to any of them to choose the language.