Manual Allowlist Tasks and Proof
Manual tasks are the fastest way to add growth actions to a Solana allowlist without a paid social API. This guide shows how to design tasks, collect proof, and review submissions so teams can approve wallets quickly without sacrificing fairness.
Summary
Manual tasks let teams request specific community actions such as follows, reposts, or tags, then verify proof before approving a wallet. The key is to keep tasks short, make proof submission obvious, and review entries with a consistent rubric. This keeps allowlist growth measurable while protecting supply and community trust.
Why manual tasks still work in 2026
Social gating is still one of the strongest signals of intent for an NFT community. The challenge is that automated checks often require paid APIs and large maintenance budgets. Manual verification keeps teams independent and reduces operational complexity while still capturing the right engagement signals.
Manual workflows are especially useful for early stage projects or sub communities that are just launching their first allowlist. You can collect proof quickly, approve the most relevant wallets, and then decide whether to upgrade to automated verification later.
Design tasks that match your goal
The best tasks are short and specific. If your goal is awareness, a single follow task might be enough. If your goal is proof of participation, require a repost or a tag that mentions the project name. Avoid long lists that feel like chores. Three tasks is a strong ceiling for most launches.
- Follow the project account to build long term audience.
- Repost the mint announcement to surface the launch.
- Tag the project in a short post with your reason for minting.
Teams running campaigns in North America often prioritize timing around late afternoon engagement. Communities in Europe and Asia Pacific may prefer a 24 hour window to avoid regional gaps. Set the task window to match your audience and include the exact time zone in the task text.
Collect proof without slowing users down
Proof should be simple to submit and simple to review. A single proof link plus an optional note is enough for most tasks. For example, a retweet can be verified by the post URL and a follow can be verified by a profile URL. Use a short proof hint to tell users exactly what to paste.
In Culture, you can enable manual tasks per campaign. The waitlist form then requires proof before submission. Admins see the proof link and notes in the moderation table, where they can review quickly and approve to the allowlist.
Review with a simple rubric
Manual review should not feel subjective. Build a lightweight rubric: proof link present, task text matches the requirement, and the timing falls within the task window. If any one item fails, mark the submission for follow up or reject it. Consistency is more important than being overly strict.
- Approve if the proof link and task text match the requirement.
- Hold if the proof looks incomplete or missing context.
- Reject if the proof is clearly unrelated or outside the window.
Protect supply and reduce low quality entries
Manual tasks are also a filter. If you notice spam, tighten the proof hint or ask for a specific post link. If the same wallet appears across multiple submissions, prioritize known community members. Most teams find that a transparent, consistent review policy removes most of the abuse without complicated tooling.
When you run collabs with other projects, align on proof expectations. Shared rules reduce the chance of conflicting approvals and keep partner campaigns clean.
Integrate tasks into the mint timeline
Manual tasks should end before you finalize the allowlist. Most teams lock tasks 24 to 48 hours before mint so there is time to review. If you are coordinating across Los Angeles and Singapore, publish the cutoff time in both local time and UTC to reduce confusion.
After review, export the allowlist and send it to your mint tooling. This gives you a clean handoff with a predictable final list.
Turn task participants into long term members
Manual tasks are more than a pre mint check. Follow up with approved wallets after mint to reinforce the action they took. If someone tagged the project, thank them. If they reposted, share the best community posts. These small acknowledgments convert task participants into long term advocates.
Expert perspective
Manual proof is not a fallback. It is a deliberate choice that keeps teams in control of who joins their community.