Surge.xyz × Twin3 — FAQ

Yes — but conditional on Surge wiring the prize to our wallet first. Every voter is eligible, not just the top 50 visible on Surge's UI.

The flow:

• Surge wires the prize to our wallet
• ~30-day window for the community to verify the calculation and surface disputes
• Automatic on-chain distribution to each voter's designated wallet

"The amount is significant; once distributed wrong it cannot be recovered. Better to take time to reach consensus." — Ming

70% voters · 10% inviters · 20% community pool

• Voter share = (your Ignites ÷ total Ignites) × 70% × prize at our rank
• Inviter share = 10% on top of every Ignite your invitees cast — paid by the project, not deducted from them
• Community pool reserved for future contributor rewards (hackathons, PoC bounties)

No. Surge's UI displays only the top 50 due to display limits, but all voters are eligible.

Ming has requested Surge's full voter API so the final distribution can be calculated against the complete list.

your Ignites ÷ total Ignites × 70% × prize at our rank

Live — recomputes every refresh. Not locked until the competition ends and the final calculation is announced.

See your live calculation: open your profile on surge.twin3.ai → "Calculation Snapshot" panel.

Dynamic. At twin3 #1 ($100K pool, ~14K total Ignites) it's roughly $5 per Ignite. The figure drops if our rank drops or the total Ignite pool grows.

Your individual $ value is recomputed live; nothing is locked until the competition ends.

Surge is continuously cleaning bots, new voters keep joining, and our rank can shift between 1st–5th. Each of those moves the denominator (total Ignites) or the numerator (prize at rank), so individual shares move with it.

This is normal. All numbers are estimates until the competition ends.

Surge.xyz's vote-weight unit. Each registered Surge user gets a baseline allotment, can earn more via tasks, and allocates them to projects of their choice.

1. Go to surge.xyz/discovery/twin3
2. Allocate your Ignites to twin3
3. Screenshot the page showing the "Allocated to twin3" number
4. Post the screenshot in #🔥-surge_vote on Discord
5. Lucy bot replies "+N Ignites · ≈ $X"

• Connect X / GitHub / LinkedIn on Surge → +15 Ignites (one-time)
• Weekly Surge platform tasks → ~4 Ignites/week
• Invite friends who vote → 10% bonus on every Ignite they cast (paid from the inviter pool, not deducted from them)

Wait for the next weekly Surge tasks, or focus on inviting friends — the inviter share has no cap. Every Ignite your invitees cast gives you 10% bonus.

Yes. The system credits your maximum allocated value per Surge account, not the sum. Re-uploading the same screenshot doesn't double-count — duplicates are detected.

To get more credit: increase your allocation on Surge first, then screenshot again.

Login to surge.twin3.ai → your profile → "Your Invite Links" section. Two options share the same code:

• Discord link (discord.gg/...) — friend joins our server
• Web link (surge.twin3.ai/i/...) — friend signs in via OAuth without joining Discord

Both routes attribute correctly.

Not strictly — but to get inviter credit, the friend must:

1. Click your link
2. Vote on Surge.xyz
3. Post their voting screenshot in #🔥-surge_vote

If they vote on Surge but never post a screenshot here, we can't see them as your invitee and you don't get the 10% bonus.

Common reasons:

• Friend hasn't posted their voting screenshot in #🔥-surge_vote
• Friend ran /claim_inviter @someone-else (claimed someone else)
• Friend's Discord account got flagged as bot during cleanup
• Friend joined Discord but never spoke in any channel — invisible to us

Open your profile → Social Activity tab to see the exact event timeline for every join, claim, release.

Surge.xyz and Twin3 are separate systems — Surge doesn't tell us who invited whom. We attribute only when:

• Your friend used your link AND posts in #🔥-surge_vote, OR
• Your friend runs /claim_inviter @you while still a free agent

Policy P6 (effective 2026-05-08): Once you have an inviter, you cannot unilaterally switch.

Only your current inviter can release you — by clicking the Manage button on their surge.twin3.ai profile. After they release you, you become a free agent and can claim someone else.

Disputes are resolved via Discord DM between the two parties. The system doesn't arbitrate — if the current inviter declines to release you, the attribution stays.

1. Login to surge.twin3.ai
2. Open your profile → "FRIENDS YOU'VE BROUGHT IN"
3. Click Manage → red ✕ next to their pill → confirm

Heads up: their future Ignites won't earn you the 10% bonus once released.

Yes — and each Surge account is rewarded independently. At payout time, the prize for an account's votes goes to that Surge account, not pooled into one lump sum for your Discord ID.

The Discord-side number you see (personal_ignites = Σ max(allocated_here) per account) is for your own visibility — it lets one person track their total contribution across multiple Surge accounts in one place. Discord is essentially a self-reporting tool; the votes recorded on Surge.xyz are the only definitive ones.

What this means for payout:

• Voter rewards are issued per Surge account, based on each account's verified vote record.
• Inviter rewards follow the inviter→invitee map in our system, then verify each invitee's actual Surge votes — every step is checked end-to-end.
• Don't game with duplicate screenshots of the same Surge account — duplicates are detected and credited 0.

Note on invite credit: only invitations recorded in our system count for the 10% inviter bonus — your personal invite link (/i/<your-token>), your assigned Discord per-user invite code, or relationships confirmed via /claim_inviter. Surge's own referral system and unattributed Discord joins don't contribute. That's why joining our Discord (with the inviter relationship recorded) is required to realize invite rewards.

Most likely a historical positional-pairing artifact. Before 2026-05-08, our connector sync occasionally bound new joiners to the wrong inviter when several invite codes incremented in the same sync window. The newer pipeline is much stricter, but a few old attributions may still look off.

Two fast checks before doing anything:

• Open your profile → Social Activity tab. The full timeline of who-attributed-you-when is right there. If it doesn't match your memory, you're probably mis-attributed.
• The "Invited by" card on your profile shows the method:
  discord_invite_tracking (auto-detected via Discord's invite log) — most likely candidate for historical mis-pairing
  mutual_approval (you self-claimed via the Manage UI) — you picked them, no mistake here
  self_claim (legacy Discord /claim_inviter)

If it's wrong, here's the clean fix (no staff intervention needed):

1. Private DM the wrongly-attributed person on Discord. Ask them politely to release you.
2. They open their surge.twin3.ai profile → "FRIENDS YOU'VE BROUGHT IN" → Manage → click ✕ next to your pill → confirm.
3. Once they release you, you become a free agent — and per our 2026-05-08 fix, the connector sync will not grab you back.
4. Run /claim_inviter @the_real_inviter in any Discord channel. The new attribution takes effect immediately, no approval needed from the new inviter.

If the wrong inviter declines or doesn't reply within a reasonable window, ping a moderator in #💬｜chat with a screenshot of your Activity tab. Don't mass-DM strangers — staff has full audit logs and can verify.

The system credits new Ignites only when the new "Allocated to twin3" number is higher than your previous max for that Surge account.

If your screenshot shows the same or lower number, it's flagged as a duplicate and credited 0. To earn more: increase your allocation on Surge first, then re-screenshot.

Surge's UI sometimes lazy-updates personal vs project totals separately, producing transient mismatch ("you allocated 20 but project shows 43" type).

Refresh Surge, wait a minute, then screenshot again. Our system uses max(allocated_here) per account, so old higher records are protected — a stale lower screenshot can't lower your credit.

Surge is actively cleaning bot accounts. If yours got swept incorrectly, raise it with Surge directly — Twin3 has no control over their bot-cleanup process.

Twin3 doesn't actively ban anyone. Surge may clean bots upstream, and we mirror their state. If you use real social account links and behave naturally, you have nothing to worry about.

Post in #2-bug-report with:

1. Page URL where the issue happens
2. Reproduction steps
3. Screenshot (with browser console open if you can)
4. Wallet address (first 6 + last 4 chars)

"Not working" alone isn't actionable — give us details so we can reproduce.