Contest voting with IP and device limits: a guide for shared audiences

What should you establish before sharing an entry?

First establish what the contest actually says about repeat voting, networks and devices. A short rule check prevents an invitation from implying that someone should vote again when the contest permits only one attempt.

Look for the exact wording on the voting page and in the contest rules. Note whether the stated limit refers to a person, a device, a network, or more than one of these. Also check whether the organizer describes what a supporter should do after a block. Do not infer hidden mechanics from a message on the voting screen: keep your notes to what the rules and page visibly say.

Before you promote the entry, prepare a simple reference for everyone sending invitations:

• The contest link and the entry being promoted.
• The sentence in the rules that explains the voting limit.
• Any stated instruction for a supporter who cannot submit a vote.
• A contact route for questions that the published rules do not answer.

If the rules clearly prohibit outside promotion, do not launch outreach. For a broader review of contest requirements, see contest rules and risk consulting. For other kinds of voting protection, the voting protection overview helps distinguish this issue from email checks, daily limits and other requirements.

Which supporters are likely to share a network or device?

A useful outreach plan identifies groups that may connect through the same Wi-Fi or use a shared device, then gives each group an instruction that fits its setting. This is a planning aid, not a way to predict which individual vote will be accepted.

Use the table to segment your outreach list, not to label people as eligible or ineligible. A family chat can receive a short reminder about one vote per person; a school group may need organizer clarification before promotion begins. Where young people are involved, obtain parent or guardian agreement and follow the applicable age and privacy rules before inviting participation. For youth-specific considerations, see beauty, kids, pets and school contests.

What should an invitation say to people on shared Wi-Fi?

An effective invitation states the voting rule before the link and gives a calm, honest instruction for a blocked attempt. That way, supporters are not surprised and are not encouraged to keep trying to submit the same vote.

A useful message can be brief: “Please read the contest rules and vote once for this entry using your own device. If the page says a vote has already been recorded, stop and let me know; I’ll check the published instructions with the organizer.” Adapt the wording to the audience, but keep the one-vote instruction clear. Avoid claims that switching connections or devices will make a vote count.

For each group, check the invitation against these points:

• Does it identify the entry and link to the correct voting page?
• Does it state the rule in plain language, without adding an exception?
• Does it explain what to report if the page blocks a first attempt?
• Is the request appropriate for the group and sent through a channel where outreach is welcome?

A shared message should invite participation, not create a room-wide voting event. You can use the templates for asking people to vote as a starting point, and community, email and messenger outreach covers consent-based ways to reach supporters.

How can you pace outreach without creating a voting bottleneck?

Pace outreach by audience and channel rather than asking a large shared group to act at the same moment. Staggering messages makes the instructions easier to follow and gives you a clearer view of where supporters are encountering friction.

Start with a simple sequence: prepare the rules-based invitation, send it to one audience group, review questions and blocked reports, then adjust the next message without changing the contest’s voting conditions. The purpose is orderly communication, not to secure extra attempts. For example, a workplace note can be shared as an invitation for colleagues to participate individually, while a school outreach plan should first resolve any rule questions with the organizer.

Keep a lightweight record as the campaign runs. For each outreach wave, note the audience group, when the message was sent, the link used, questions received and any reports of a blocked first attempt. Avoid collecting unnecessary personal information; a general group label and the supporter’s description may be enough to raise a pattern with the organizer.

A calendar can help coordinate those waves with other promotion. The 7, 14 and 30 day contest campaign calendar offers a way to plan communications, while contest marketing explains how outreach can fit alongside other campaign activity.

What is a fair response when a supporter is blocked?

Treat a blocked message as a reason to pause and clarify, not as an invitation to find another route for the same vote. The supporter should follow the page’s instructions, avoid repeated submissions and share a concise account of what happened if they want help.

Ask for only the details needed to describe the issue: the approximate time, the wording shown on the page, whether the person had already voted, and whether they were on a shared school, workplace or household connection. A screenshot can be useful if it does not expose someone else’s private information. Keep the original message and the rules link together so the organizer can understand the context.

Then send one clear question to the organizer: explain that a supporter reports being blocked on a first attempt and ask what the rules say that person should do. Do not ask the supporter to clear browser data, use a proxy or VPN, borrow another device, or conceal their connection. We do not recommend those tactics, and we do not accept projects that depend on them. Our white-hat approach does not sell votes, followers or engagement and uses no bots, scripts, fake accounts or click farms.

For a wider view of acceptable promotion practices, read the contest promotion methodology and the no-bots policy.

How can you document a pattern without guessing at hidden causes?

You can document what supporters report and what the campaign team can observe; you cannot determine a contest’s unseen technical process from those reports alone. Keep the record factual so the organizer can assess the issue using the information available to them.

A practical log might include the outreach group, date of the message, link destination, exact block wording, and whether the supporter says this was their first attempt. Record the entry counter or visible page status only when it is available, and note when you checked it. Do not present a change in a counter as proof that a particular group was accepted or rejected; the log is evidence of what people experienced, not an audit of the voting system.

When you see multiple reports from one setting, compare the wording and circumstances, then send the organizer a concise summary. Keep individual identities private unless the organizer requests information and the supporter agrees to share it. If no pattern emerges, keep the guidance simple rather than inventing an explanation.

This discipline also improves campaign reporting. The contest campaign budget planner can support planning resources for outreach, while paid promotion of contest entries describes how paid distribution can fit within a rules-first campaign.

What can the organizer clarify about an IP or device block?

The organizer controls how the contest applies its stated voting limit and whether it will clarify a shared-network case. We can review the published rules and the supporter reports, but cannot inspect or change the contest’s voting mechanism; a platform may also reject or remove activity under its own review and rules.

For this kind of campaign, Bitcoin Insider can bring the rules, audience map and sample invitations together in a Desk Review, then shape the practical guidance into an Advisory Brief. That gives the entrant a clear set of messages for households, schools, offices and other relevant groups, plus a concise organizer query when clarification is needed. Any projections are identified as projections; the work is to plan and deliver the agreed promotion, not to promise accepted votes, a win or a ranking.

Before seeking help, gather the contest page, entry link, rules, deadline, draft invitation and a short description of where supporters are likely to connect. If you have reports of blocks, include the wording and context without unnecessary personal data. Send those materials for the free contest analysis; we will review the rules and outline a fair next step for your entry.

How it works

1. Read the voting rulesRecord exactly what the contest says about people, networks and devices. Note any published instruction for a blocked attempt.
2. Sort supporters by settingGroup likely audiences as households, schools, workplaces, venues or individual mobile users so their instructions fit their situation.
3. Prepare the invitationState the one-vote rule, include the correct entry link and tell supporters to pause and report a first-attempt block.
4. Send outreach in manageable wavesReach groups through suitable channels without turning a shared room or connection into a group voting session.
5. Record and raise access problemsKeep factual notes on the message and setting, then ask the organizer for clarification rather than suggesting a way around the limit.