LuckPicker

Blog

What Streamers Get Wrong About Giveaways

The fairness problem in a stream giveaway is almost never the random draw.

There is a step-by-step page on this site for running a draw live, and this is not that. This is the argument about why the advice on nearly every other page is aimed at the wrong problem.

Search for how to run a fair stream giveaway and you will be told about random number generators. Nobody has ever doubted the random number generator.

The suspicion is about you

When chat says a giveaway was fixed, they are not hypothesising that the browser's entropy source was compromised. They are hypothesising that a human being made a choice and called it a draw.

That hypothesis is reasonable because it describes a thing that happens, routinely, without anybody thinking of themselves as dishonest. Running it again because the first result was somebody with four followers. Switching tools because one gave a name you did not recognise. Quietly not including an entry that arrived twice.

None of that requires a rigged generator, which is why an answer about the generator is not an answer. It is a technically accurate response to a question nobody asked, and it reads as one.

Why the advice keeps missing

Guidance about fairness gets written by people who think about fairness as a property of mechanisms, because that is the interesting part and it is the part that can be got right definitively. The awkward part — that the mechanism was never in doubt — is harder to write about and produces less satisfying advice.

So the genre optimises the wrong variable. Every article is about which tool to use, and the disputes are all about what went into it and who was watching.

The uncomfortable corollary is that a streamer who follows the mechanism advice perfectly is no better protected than one who ignores it. The protection lives entirely in the record, and the record is barely mentioned anywhere.

The asymmetry that makes it worse

A giveaway is one of the few things a creator does where the audience's trust is tested with a specific, checkable claim, and where being right is not enough. An honest draw with no record and a dishonest draw with no record are the same object from outside.

That asymmetry is unusual. Most of what a creator says is unfalsifiable in either direction; this is falsifiable and almost nobody arranges for it to be falsified.

It also means the accusation cannot be answered after the fact, which is the part people discover too late. Everything that would have settled it had to happen before the draw, and afterwards there is nothing to reach for.

What would actually change the picture

Almost none of it is technical. Showing the list on camera, saying the count out loud, and not cutting the recording are worth more than any property of the underlying draw, and none of them require understanding anything.

The single highest-value habit is publishing something before the draw rather than after it — the closing time, the entrant count, the method. Anything at all that was fixed in advance converts an argument into a comparison.

The genre could teach that in a paragraph. It teaches cryptography instead, which is more interesting and helps nobody.

Why the incentives point the wrong way

There is a structural reason the record-keeping advice does not spread, and it is not ignorance. Publishing a frozen list and a stated method costs a streamer something real: it removes flexibility they might genuinely need.

A winner who turns out to be a banned account, an entry that was clearly automated, a prize that cannot ship to the winner's country — all of these are handled easily by an organiser who kept their options open and awkwardly by one who published rules in advance. The discretion that looks like a fairness risk is also the thing that makes the giveaway administrable.

Which means the advice has to be specific about what to publish rather than telling people to publish everything. A closing time and an entrant count cost almost no flexibility. An exhaustive rules document costs a lot and is why nobody writes one, and pretending otherwise is why the advice does not land.

The smallest version that actually helps

Given the flexibility cost, the useful question is what the minimum viable record looks like — the smallest thing that converts an accusation into a comparison without tying an organiser's hands.

One message, posted before the draw, containing the closing time and the entry count. That is it. It costs no flexibility at all: it does not commit you on eligibility, on what happens to a no-show, or on anything else you might need to decide later. And it fixes the two facts that almost every dispute turns on.

Everything beyond that is optional and has a real cost attached. A stated method removes the ability to switch tools. A published entrant list removes the ability to quietly exclude an obvious bot. Both are worth doing for a valuable prize and neither is worth pretending is free.

The advice that would actually spread is the one-message version, and it is not what anybody writes, because it is less impressive than a protocol.

Frequently asked questions

What do viewers actually suspect?

That a person made a choice and called it a draw — not that the entropy source was compromised. The mechanism was never in doubt.

Why is that suspicion reasonable?

Because re-running after an unwelcome result, or switching tools mid-way, happens routinely without anyone feeling dishonest.

Why does most advice miss it?

Because fairness as a property of mechanisms is the interesting part and the part that can be settled definitively. The record is harder to write about.

Does following the mechanism advice protect me?

Barely. An honest draw with no record and a dishonest one with no record are indistinguishable from outside.

Can an accusation be answered afterwards?

Almost never. Everything that would settle it had to happen before the draw, which is what people discover too late.

What is the highest-value habit?

Publishing something before the draw — the closing time, the entrant count, the method. Anything fixed in advance turns an argument into a comparison.

Tools mentioned in this guide