Frequently Asked Questions

Toren is giveaway infrastructure for X and YouTube. Hosts can connect their accounts, create giveaways, collect entries, filter suspicious participants, draw winners, and share public proof pages that participants can verify.

Toren supports X and YouTube. X giveaways can use comments, likes, reposts, quote posts, and follow requirements. YouTube giveaways can use video and Shorts comments with optional subscriber checks where supported by the connected account flow.

Account connection verifies that you own the account or channel running the giveaway. It also lets Toren collect the public engagement data needed to validate entries and prevent impersonated giveaways.

Yes. The Free plan supports up to 3 live giveaways at a time. Pro and Agency plans add higher capacity, custom URLs, winner fulfillment features, Survival Wheel access, and white-label branding options.

Toren is built around verification. A normal random picker usually asks participants to trust the host. Toren publishes the proof behind the result, including seed commitments, public entropy, eligible counts, and verification hashes.

Yes. Agency plans support white-label branding and custom domains, so giveaway pages can appear under the agency or client brand while still using Toren's verification infrastructure.

You connect the account, paste the X post or YouTube video URL, choose the entry rules, set the schedule, and let Toren collect and validate entries. When the giveaway ends, Toren draws the winner and creates a public transparency page.

X giveaways can use comments, likes, reposts, quote posts, and follow requirements. Follow requirements work best as an add-on to another entry action so Toren only checks people who already engaged with the giveaway post.

YouTube giveaways are built around video and Shorts comments. Hosts can also use YouTube account connection to verify channel ownership and supported subscriber-related requirements.

Yes. Toren can combine multiple requirements, such as comment plus like, repost plus follow, or comment plus keyword. A participant must meet every selected requirement before they are included in the eligible draw pool.

Yes. Toren syncs giveaway activity in the background so the eligible list can continue updating while the giveaway is live. Hosts can also review the participant list before drawing winners.

Toren checks the final eligible pool, applies the selected filters, runs the winner selection process, and saves a public record of the result. The host can then share the transparency page with participants.

Yes. Toren supports multiple winners when the giveaway is configured for more than one winner. The draw process derives winners from the same fairness proof while preventing duplicate winners when that rule applies.

Yes. Toren supports participant and draw data exports so hosts can keep their own records of entries, winner results, and process details.

Yes. Paid plans can use the winner claim flow to collect the winner information needed for prize fulfillment. Claim pages are separate from public transparency pages so sensitive information is not exposed publicly.

Yes. Each public transparency page shows the proof needed to check the result, including eligible pool details, seed commitment data, public entropy, winner position, and verification hashes.

The server seed is Toren's private randomness for the draw. Toren publishes a hash of that seed before the result is finalized, then reveals the seed after the draw so anyone can confirm it matches the earlier commitment.

Solana entropy is a public block hash used as external randomness. Toren combines it with the committed server seed so neither Toren nor the host can know the final combined hash before the public block exists.

The winner position is the selected spot in the eligible pool after entries are placed in a deterministic order. For weighted wheels, extra valid entries remain as extra spots for the same name.

A verification hash is a fingerprint of the saved draw proof. It binds the seed, entropy, participant pool, and selected result. If the saved proof changes later, the hash changes too.

Process logs summarize what happened during the giveaway, including collection, filtering, draw timing, proof creation, and result publication. They help hosts and participants understand the draw without exposing abuse-detection rules.

Use the transparency page or Verification Center. The proof checks that SHA-256(server seed) matches the committed seed hash, combines the server seed with the public Solana block hash, then derives the winner position from the resulting hash and eligible pool size.

Yes. Anyone with the link can view the proof page. Pro and Agency users can customize public URLs, while Free users receive system-generated URLs.

Toren uses automated abuse checks during entry collection to identify suspicious accounts, duplicate entries, and low-quality spam. The system evaluates multiple account and activity signals together before excluding an entry from the eligible pool.

Publishing exact thresholds would make the filters easier to bypass. Toren shows hosts enough context to review suspicious entries while keeping the precise detection recipe private for abuse prevention.

Yes. Hosts can review flagged entries from the participant view and restore a legitimate entrant if the automated filter catches a false positive.

No. Bot filtering is part of Toren's fairness infrastructure. Making it optional would create inconsistent giveaway standards and could weaken participant trust.

Suspicious entries are marked ineligible and excluded from the winner draw. They remain part of the giveaway record so the host can audit what happened.

Filtering defines the eligible pool before the draw. The fairness proof then applies to that final eligible pool, so the winner is selected from the entries that passed the configured rules and integrity checks.

The Survival Wheel is a live reveal experience for giveaway winners. It looks like a familiar online wheel, but the final winner is protected by Toren's fairness proof instead of relying only on animation.

For giveaway wheels, no. The final winner is locked by Toren's fairness proof before the reveal begins. The wheel reveals the result by removing names until the locked winner remains.

The final winner is predetermined by the fairness proof. The elimination path is the reveal layer. Each spin removes non-winning names and cannot remove the locked winner.

Yes. Non-winning names can remain on the wheel through several rounds and may survive deep into the reveal. They are still part of the show, but they cannot replace the locked winner.

Extra valid entries are treated as extra slots for the same name. If someone has 3 valid entries, that name can appear with 3 slots until those slots are removed or the final winner remains.

After a name or slot is removed, the remaining slots are redrawn into balanced slices. This keeps the wheel readable as the list gets smaller and does not change the locked winner.

Use one elimination per spin for clean suspense. Use shorter spins early, then longer spins for the final rounds. If the wheel is crowded, reduce labels or visible entries so viewers can follow the reveal.

Share the wheel result page or giveaway proof page. It shows the winner, eligible pool details, elimination history when available, and the fairness proof behind the result.

Yes. Paid plans can use the custom wheel experience for manually entered names. The wheel can still save a result page so the outcome is easy to share.

Quick Pick is Toren's fast winner picker for X posts. Paste a public post URL, choose the entrant group, and Toren selects a winner with a shareable proof page.

A normal giveaway has setup, rules, scheduling, participant management, and a full transparency page. Quick Pick is faster. It is meant for selecting from an existing X post without building a full giveaway campaign.

Quick Pick can select from reposts, replies, or quote posts on a public X post. The selected group becomes the entrant pool for that pick.

Yes. Quick Pick creates a seed commitment, uses public entropy when available, derives the winner deterministically, and publishes a result page that can be independently checked.

Yes. Quick Pick supports multiple winners when configured for more than one winner, up to the limit enforced by the Quick Pick flow.

Quick Pick is available on active Pro, Agency, and Founder plans.

Share the Quick Pick result link. It shows the selected winner, the entrant group, the seed hash, the public entropy data when available, and the proof needed to verify the result.