Blueprint 1 of 2 Save as PDF
Blueprint 01 · Method

The Twitter Engagement Blueprint.

A method for closed-membership communities where hidden reward mechanics produce a daily stream of content from members. Drawn from 's Guardians program.

Source VerticalWallet · Solana Length~10 minutes SeriesCommunity Growth Blueprints, no. 1 of 2
1,260
Rewarded tweets
in 1 month, only past daily caps
353K
Impressions
across rewarded posts
19,500
Likes
organic engagement
7,300
Comments
+ 846 retweets · 156 quotes
What you're building

A closed-membership engine that turns speculation into content.

A closed-membership community where members are paid in points to perform a specific list of actions on Discord and X. They don't know exactly which actions are rewarded. They speculate, experiment, and post constantly to climb a leaderboard.

The rewards are small. The leaderboard is everything. The speculation is the engine.

Many Guardians post several times a day. Only one of those tweets clears the system and gets rewarded. They don't know that. They keep posting anyway. That's the content factory.

500 Guardians produce 1,260 tweets that generate 353K impressions per month CLOSED COMMUNITY 500 Guardians ×~2.5/day DAILY CONTENT 1,260 tweets / month ×280 reach REACH 353K impressions
The Content Factory · 1 month, Solflare Guardians
Why this works

Six principles. Read them as rules.

01

Speculation is the strongest catalyst.

Tell people what gets rewarded and they execute the minimum. Hide it and they try everything.

02

Closed beats open.

Skin in the game changes everything. Status objects outperform open Discords by an order of magnitude.

03

Many small actions beat one big one.

Reward 13+ tiny daily actions, not one large one. You're building a habit of presence.

04

Caps prevent farms but raise volume.

A hidden one-tweet-per-day cap raises output as users post "just in case." Without it, sybil farm.

05

The leaderboard resets fast.

12 weeks kills participation. 2 weeks creates urgency. People who think they can climb keep coming.

06

Decentralize the gate.

Don't approve applicants. Hand existing members invite tokens. The community polices itself.

The blueprint

Seven steps. Top to bottom.

01

Pick your platform stack.

DISCORD Roles + permissions Trigger automations Voice stages vs TELEGRAM Limited permissions No trigger automations Voice but no rich stages

Discord for the closed community core. X for content output. Telegram only as a casual broadcast layer if your audience already lives there.

Action
Lock in Discord. Set up three zones: public, verified-member, and inner-circle.
02

Define your closed inner circle.

PUBLIC VERIFIED Guardians inner circle

A clear identity, visible status, genuine perks, a waitlist. Not a giveaway program. People should want to be in before they understand what it pays.

Action
Write a one-paragraph definition of who your inner circle is and what they believe. List 3–5 perks only they get — things you can deliver, not promises.
03

Identify 10 to 15 reward-worthy actions.

tweet reply quote retweet react voice attend streak help newcomer refer feedback UGC cross-engage find exploit hidden hidden hidden

Solflare tracks 13+ types of interactions. The exact list is private (that's the point) but the categories are predictable: Twitter posts, replies, quotes, retweets, Discord reactions, voice attendance, streaks, referrals, UGC, partner cross-engagement, exploit reports.

Action
List 10–15 actions you'd love your community to do every day. Score each on a small fractional point value. Set a daily cap so an active member earns ~5–15 points/day.
04

Hide the mechanics.

INTERNAL · PRIVATE ? ? ? ? ? ? PUBLIC EXPLAINER "We reward Guardians who contribute value."

The mystery is the product. Members talk to each other in DMs trying to crack the system. Every conversation about "what gets points" is unpaid marketing for your community.

Action
Write a public explainer that says what kind of behavior gets rewarded but never how.
05

Build the anti-farm rails.

RAW WALLET-AGE VELOCITY · BEHAVIOR QUALITY · DAILY CAPS VERIFIED

Without these, your leaderboard becomes a bot leaderboard within a week.

  • Daily caps per action. Don't tell users.
  • Wallet-age and on-chain history. Yesterday's wallet doesn't count.
  • Behavioral velocity. 50 reactions in 2 seconds is suspicious.
  • Quality filters. No "🔥" replies. Substantive only.
  • Manual review queue. Look at top-of-leaderboard outliers.

Action
Decide your top three filters before launch. Plan a weekly review of the top 10 leaderboard positions.
06

Run a public leaderboard with a clear path.

PUBLIC LEADERBOARD · CYCLE 7 1 @whale.sol 14,820 2 @kira.eth 12,470 3 @nine 11,260 4 @spencer 9,140 invite INNER CIRCLE

Public-facing. Bi-weekly reset. Top 10 get rewards. Top 3 earn an invite to the inner circle. Now public users know that grinding the leaderboard is the on-ramp.

Action
Build the public-zone leaderboard before anything else. It's the single most important visible artifact of the system.
07

Decentralize the invite.

YOU G G G FOUNDERS GUARDIANS INVITED

Solflare's Ascension token system: ~50 tokens per Guardian, ~25 per Ambassador. They vouch for who joins. The team doesn't approve applications.

Action
Decide who gets invite power and how many tokens each tier gets. Make it scarce — not 500 invites per person.
The math

What this costs to run.

For a community of ~500 active members and a target of 1,000+ rewarded posts per month:

Reward pool — top 10 every 2 weeks × ~$200 each$4,000
Public leaderboard prize pool, bi-weekly$1,500
Community-team time (1 person × ~30%)varies
Tooling — automation, analytics, anti-sybil$0–$500
Total cash outlay (monthly)~$5,500
$15.50 CPM at 353K impressions — already competitive with paid X advertising. Math improves dramatically as you scale: reward pools don't grow linearly, impressions do.
Watch for these

Seven ways this breaks.

Mechanics get leaked. Once the point values land on a public Google Doc, the speculation collapses. Vary the rules across cycles, refuse to confirm reverse-engineered guesses.
No caps, sybil army. Within 72 hours of launch, three accounts will hit 50× the average score and crater participation.
No exclusivity, no aspiration. If anyone can become a member by signing up, no one wants to be one.
Manual rewards burnout. Automate distribution before you launch. The community team will quit otherwise.
Long-cycle leaderboards. A 3-month leaderboard loses 80% of participants in the first 2 weeks.
No path from public to inner circle. Without the path, public-zone activity withers.
Static action list. Regulars min-max within 6 weeks. Rotate actions every 2–4 weeks. The mystery has to renew itself.
What you'll need

Tools & capabilities.

  • A Discord server with role-based access and at least three zones — public, verified, inner circle.
  • An X account with the ability to programmatically detect mentions, replies, quote-tweets, and engagement.
  • A way to track all 13+ actions per user, automatically — without your community team copy-pasting from a CSV.
  • A way to send rewards (token, USDC, NFT) automatically when leaderboard cycles end.
  • A way to filter for sybil and farming behavior at the time the action is recorded.

Solflare runs the automation layer on Domino. You can build it yourself, or use one of several quest infrastructure tools. The mechanics in this blueprint don't depend on any specific platform.

Launch plan

Two weeks to live.

Week 01
01
Define the program.
  • Inner circle name, identity, 3–5 perks
  • Discord server with three zones
  • Public explainer — vague but honest
  • 10–15 reward-worthy actions
  • Point values, daily caps, anti-farm filters (private)
  • Reward pool size for cycle 1
Week 02
02
Stand up the rails.
  • Public-zone leaderboard live
  • Automated tracking for top 5 actions
  • Automated reward distribution
  • Seed inner circle with 30–50 members
  • Hand out invite tokens
  • Announce the first 2-week cycle
  • Don't explain how points work
Week 03
03
Iterate live.
  • Watch the leaderboard daily
  • Manually review top 10 for sybil
  • Prepare cycle 2's reward pool
  • Quietly add 2–3 new actions
  • Patch any cycle 1 exploits
What success looks like

When the system is running, you'll know.

It's not a campaign. It's a system that runs itself.

  • Daily, unprompted posts about your project from members
  • A waitlist of public-zone users grinding for an invite
  • Speculation about "what gives points" happening in the open
  • Applicant inflow you can no longer keep up with manually
  • Content production volume that would take a 3-person marketing team to replicate
  • Moderators that can step back because members run the floor

Many Guardians post several times a day. Only one of those tweets clears the system. They don't know that. They keep posting anyway.

Take action

Run this, today.

Two ways to put this blueprint to work without rereading it.