Morning checklist — start marketing the airdrop
Drafted overnight 2026-06-25/26 while you slept. Everything below is ready to ship — review, tweak voice if needed, then send.
✅ Already shipped overnight (no action needed)
- PR #364 —
docs/airdrop-points-system-design.md(13-product matrix locked) - PR #365 —
docs/tokenomics.md+dex-app/lib/farm-config.ts+CLAUDE.md(10-bucket allocation + LP tier caps locked) - PR #366 — landing pages, blog, whitepaper, airdrop app updated everywhere
- PR for this batch —
docs/airdrop-distributor-spec.md(contract spec) + marketing kit + CLAUDE.md airdrop status block
🌅 Morning steps (in order, ~2 hours total)
Step 1 — Review the contract spec (15 min)
Read docs/airdrop-distributor-spec.md. Sanity-check the three things where I made a call without you:
- Custody: AirdropDistributor owned by protocol-governance 3-of-5 Safe — same Safe that already owns ShieldedPool.
- 365-day claim window per phase before unclaimed reverts to Treasury — generous but not infinite.
- No upgradability and no pausability — credibility > flexibility for an airdrop contract.
If any of these don't sit right, ping me with what to change. Otherwise, ship.
Step 2 — Deploy landing-site updates to production (15 min)
# On laptop or via Railway dashboard
cd landing
npm run build
# Push to Railway via git or trigger deployVerify https://sanect.com/tokenomics now shows the 10-bucket allocation and Day 180/270/360/450 phase dates.
Step 3 — Publish the tokenomics announcement blog (5 min)
Content drafted at docs/marketing/blog-tokenomics-announcement.md — copy into your CMS or as a new file under landing/src/pages/blog/.
Title suggestion: "SNCT tokenomics + airdrop: locked"
URL: sanect.com/blog/tokenomics-locked
Step 4 — Twitter thread (5 min)
Drafted at docs/marketing/twitter-thread-tokenomics.md — 12 tweets, ready to copy-paste into typefully or threadreader.
Schedule for 9-11am UTC (highest crypto-Twitter engagement) or post live if you want real-time replies.
Step 5 — Telegram + Discord pinned message (5 min)
Drafted at docs/marketing/telegram-discord-pinned.md — same content, slightly more conversational.
Pin in:
- @sanectnetwork Telegram
- Discord #announcements
- Optionally repost in #general after 30 min for second wave
Step 6 — Update homepage hero CTA (10 min)
The landing index.astro hero currently shows generic stats. Add a small banner above the fold:
🪂 30% of supply allocated to community via airdrop.
First snapshot Day 180. Start earning points today →Linking to /airdrop (which is airdrop.sanect.com).
Step 7 — Kick off Galxe campaign setup (30 min)
Galxe gives you instant off-chain verification (Twitter, TG, Discord, LinkedIn) without building it yourself. Create a campaign:
- Sign up at galxe.com as project owner
- Verify sanect.com domain ownership
- Create campaign: "sanect launch quests"
- Add starter quests:
- Follow @sanectnetwork on Twitter
- Join @sanectnetwork Telegram
- Join sanect Discord
- Retweet pinned announcement
- (later) Connect wallet + complete first on-chain action
- Reward: just points (no immediate token — they redeem at Phase 1 claim)
Galxe pro tier is ~$5-10k/month. Worth it for the first 90 days; can drop after.
Step 8 — Email list for influencer outreach (1 hour)
Build a list of 50 mid-tier crypto Twitter accounts (5k-100k followers each) in these niches:
- Privacy/ZK (Aztec, Aleo, Penumbra community voices)
- Cosmos ecosystem (Sei, Osmosis, Celestia influencers)
- L1 explainer accounts
- Airdrop hunters who maintain reputation (Cobie, ChartFu)
Send each:
- 1-line pitch
- Link to tokenomics page
- Link to airdrop points doc
- Their unique referral code (format:
?ref=<address>) - No payment — referral commission is their incentive
I'll draft this template at docs/marketing/influencer-outreach-template.md (coming next).
Step 9 — Schedule remaining work for the engineering team (30 min)
Use the docs/airdrop-distributor-spec.md build effort table to plan sprints:
| Week | Focus |
|---|---|
| Week 1 (Days 7-14) | Contract development + Foundry tests |
| Week 2 (Days 14-21) | Internal audit + fuzz |
| Week 3 (Days 21-50) | External audit engagement |
| Week 1-3 in parallel | Indexer development |
| Week 4-5 | Frontend claim flow |
| Week 6-7 | Subgraph + dashboard data integration |
| Week 8-13 | Anti-sybil pipeline + appeals system |
This gets you to Day 90 with everything except the actual indexer cutoff ready to roll. Plenty of buffer.
📋 What you DON'T need to do today
- Don't announce specific Phase 1 snapshot block height — that's revealed Day 90 (7 days before snapshot)
- Don't promise an exact "you'll get X SNCT for action Y" — points convert proportionally to the pool, not to fixed amounts
- Don't engage with "when claim?" beyond "Day 180 per the public roadmap"
- Don't ship the AirdropDistributor contract today — wait for audit
- Don't post specific multisig addresses publicly until Safe migration completes Day 14
🟡 What to track this week
- Twitter thread engagement (likes/RTs/replies in first 24h tells you reach)
- Galxe campaign signups
- Referral code activations
- Telegram + Discord new joins
- DEX volume on sanect (item #1 in points matrix — early signal of organic activity)
- Bridge inbound (item #9)
If activity surges, your Phase 1 anti-sybil pipeline needs to be ready faster than the 13-week plan. Bumpers can be moved up.
🛑 Anti-pattern reminders
- Don't pay influencers in SNCT directly — referral commission is OK, paid promotion isn't. CLAUDE.md anti-pattern list calls this out as conflict of interest.
- Don't run "trade $X to earn N points" promos — points are time-locked or fee-locked. Promoting volume-loops contradicts the anti-wash design.
- Don't extend Phase 1 timeline if launch tweets underperform — credibility of a locked roadmap matters more than first-week metrics.