Surge.xyz × Twin3 — FAQ

Yes — but conditional on Surge wiring the prize to our wallet first. Every voter on the Surge API roster is eligible — final tally is taken from surge.twin3.ai/api, not from any UI ranking.

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 verified 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)

"Verified Ignites" = your Surge.xyz active_amount at season-end, looked up via your X-verified binding (Q29). Without X verification, voter share is 0 and inviter bonus is 0 — for both you and any inviter who invited you.

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

"Your verified Ignites" comes from the Surge API, looked up via the X handle you bound on surge.twin3.ai (see Q29). Live — recomputes every refresh. Not locked until the competition ends and the final calculation is announced.

Without X verification, your verified Ignites count as 0 — your screenshots are kept as Self-Report data but don't enter this formula.

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.

Because the prize at each rank is a fixed dollar amount (see the prize table at the top), and you're getting a share of that pool — not a flat per-Ignite rate.

The formula behind your "Reward Share · est." tile is:

• your share = (your Ignites ÷ total twin3 Ignites) × pool at our rank

When more people vote for twin3, the denominator grows — so even if your numerator (your own Ignites) doesn't change, your slice of the pie shrinks. Concrete example:

• You have 100 Ignites, total network has 10,000 → you own 1% → at $70k voter pool that's $700
• Next day, you still have 100 Ignites but total network is 20,000 → you own 0.5% → same pool, now $350

This isn't a bug — it's the design. The way to grow your share is either to vote more Ignites yourself or to invite friends (their Ignites stay in the denominator but you collect a 10% bonus on each invitee's voter-pool share, paid by the project on top of their payout — see Q3).

This is distinct from Q24, which covers the case where your Ignite count itself drops (reallocation on Surge, unbind, bot-sweep) — that's a numerator effect, not a denominator effect.

If twin3's rank changes, the pool size itself changes too (see the prize table) — at #1 the voter pool is $70k, at #5 it's $14k. Currently we're locked at #1.

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 and allocate your Ignites to twin3
2. Open surge.twin3.ai and sign in with Discord
3. On your profile, click 🐦 Connect X (Twitter) to verify your Surge identity (one-time, see Q29)
4. Your Ignite total auto-syncs from the Surge API — no screenshot needed for payout

You can still post screenshots in #🔥-surge_vote for fun / social — Lucy will still reply with verification. But that path is kept as Self-Report only now; the API number is what determines your payout.

• 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 — allocate as many Ignites to twin3 as you have on surge.xyz. The Surge API tracks your live active_amount and we re-read it hourly, so any change you make on Surge will reflect on our dashboard within an hour.

No need to screenshot every vote — once you've verified X on your profile (Q29), the API does the bookkeeping.

1. Log in to surge.twin3.ai with Discord.
2. Open your own profile. The "Your invite link" section shows your link — it looks like surge.twin3.ai/i/<6-char-token>.
3. Copy it and share it anywhere — Twitter, Telegram, DMs, etc.

What happens when a friend clicks it: they sign in with Discord, get auto-added to the Twin3 server, and you're recorded as their inviter. From that point on, every Ignite they vote on Surge.xyz credits you with 10% as an Invite Point (paid by the project — not deducted from them; see Q3 for prize details).

Important: for the 10% to actually pay out at season-end, both you AND your invitee need to verify X on surge.twin3.ai (Q29). Unverified invitees count as 0 Ignites in the formula, which means 0 bonus for you. The strongest thing you can do as an inviter is help each invitee finish their X verification.

Your friend doesn't need to already have a Discord account — the flow handles new Discord users too.

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

1. Click your surge.twin3.ai/i/<token> link and sign in with Discord (this is what creates the attribution row)
2. Vote on surge.xyz/discovery/twin3
3. Verify their X (Twitter) on their surge.twin3.ai profile (Q29) — without this their Ignites count as 0 and your 10% bonus on them is 0

Steps 1+2 alone don't pay you anything — without step 3, the system sees your invitee as "attributed but unverified" and the API has nothing to credit. Get them through step 3.

Clicking your link doesn't equal attribution. For someone to count toward your verified invitee total — i.e. someone whose Ignites generate your 10% bonus — they need to complete the whole flow:

1. Click your surge.twin3.ai/i/<token> link
2. Sign in with Discord (the OAuth step that creates the attribution row)
3. Vote for twin3 on Surge.xyz
4. Verify their X (Twitter) on their surge.twin3.ai profile (Q29) — this is what links them to a real Surge API record so the system can credit you

If you shared your link with 6 friends and only 2 show on your dashboard with non-zero Ignites, the most common reasons (in order of frequency):

• Several clicked the link but never signed in with Discord — we don't even know they exist yet
• They signed in but haven't verified X on their profile — they show as "attributed but unverified" with 0 Ignites
• They verified X but their Surge X handle isn't bound to a real Surge account
• They ran /claim_inviter @someone-else to attribute themselves to a different inviter
• Their Discord account got flagged as a bot during a cleanup pass

If a friend SHOULD have you as their inviter but it didn't auto-attribute (e.g. they came in by accident through someone else's link first), they can self-claim you: on their own dashboard, open your profile page → click "Claim me as inviter" on YOUR profile, not theirs.

Open your own profile → Social Activity tab to see the exact event timeline for every join, claim, release. If a click never produced a join, there's nothing to show — by design we only record completed attributions, not browser clicks.

Surge.xyz and Twin3 are two separate systems with two separate referral ledgers. If you invited 3 friends on Surge.xyz and they all voted for twin3, that gives YOU credit on Surge's side, but it doesn't tell our Discord-side dashboard anything — the inviter chain we pay 10% on is the one tracked here, by Discord user ID.

For your Surge-side referrals to count on the Twin3 dashboard:

• Your friend signs in via your surge.twin3.ai/i/<token> link (this creates the Discord-side attribution), OR
• Your friend runs /claim_inviter @you in Discord while still a free agent (no other inviter attributed yet)

Then, for the 10% to actually pay out at season-end, your friend also needs to verify X on their surge.twin3.ai profile (Q29) — that's what links them to a real Surge API record.

What to do right now: message your Surge-side referrals, share your surge.twin3.ai/i/<token> link with them, ask them to sign in via that link (or run /claim_inviter @you), and remind them to click Connect X on their profile when they're there.

(If the friend has already been attributed to someone else on the Twin3 side and wants to switch to you, see Q21 for the amnesty window and Q17 for the normal release flow.)

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.

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 Twin3 dashboard's verified binding (Q29) shows one Surge account at a time — whichever one is linked via the X handle you bound. If you have multiple Surge accounts:

• Each Surge account is paid based on its own verified vote record on Surge.xyz
• The Twin3 dashboard's displayed Ignite total reflects the currently-bound account only — to see a different account, you'd need to unbind and re-connect with the X handle linked to that other Surge account (Q31)
• Inviter bonus is computed against each invitee's currently-verified Surge account

Surge.xyz pays out per Surge account regardless of Discord identity, so you don't lose anything by being bound to only one at a time on Twin3 — it's purely about which one the dashboard shows you and which one is used in our inviter-bonus math.

Note on invite credit: only invitations recorded in our system count for the 10% inviter bonus — your personal invite link (/i/<your-token>) 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 attribution 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, or routed everyone through the canonical "Open Discord" button on profile pages. Both paths are fixed now, but old attributions still need cleanup.

To make that cleanup painless, we've opened a one-time attribution amnesty window.

📣 Amnesty fast-path — open until 2026-05-31 23:59 UTC

While the window is open, anyone in the server can correct their inviter immediately with no need to coordinate with the wrong inviter:

1. Run /claim_inviter @the_real_inviter in any Discord channel.
2. The switch takes effect right away — no mutual-confirm, no need for the wrong inviter to release you first.

The only check we still enforce is physical impossibility: someone who joined the server after you can't be claimed as your inviter.

After the amnesty window closes, the normal flow returns: the existing inviter must release you first (their profile → FRIENDS YOU'VE BROUGHT IN → Manage → ✕), then you can run /claim_inviter. So if you spot a wrong attribution, fix it now while the fast-path is open.

Two ways to confirm whether your current attribution looks right:

• Profile → Social Activity tab — full timeline of who-attributed-you-when. If it doesn't match your memory, you're likely mis-attributed.
• The "Invited by" card on your profile shows the method:
  discord_invite_tracking — auto-detected via Discord's invite log
  amnesty_self_claim — you corrected it during the amnesty window
  mutual_approval — you self-claimed via the Manage UI
  self_claim — legacy /claim_inviter

The dashboard total is driven by the Surge API now, not by screenshots. Lucy still verifies your screenshot (Self-Report) but the number you see on your profile comes from your verified Surge.xyz active_amount, looked up via the X handle you bound (Q29).

To actually move your displayed total:

1. Make sure you've verified X on surge.twin3.ai. If you haven't, your total is 0 regardless of screenshots.
2. Vote / re-allocate on surge.xyz/discovery/twin3.
3. Wait up to an hour for the next API sync, then refresh your profile.

If you're verified, you've voted on Surge, and your dashboard total still doesn't match what Surge.xyz shows — see Q23.

If you've verified X on surge.twin3.ai, the dashboard number IS the Surge API number for the surge_user_id linked to your X handle. If the two disagree, it's almost always one of:

• Cache delay. We re-read the Surge API roughly once an hour. If you just voted, give it up to an hour to sync.
• Wrong Surge account bound. Multiple X handles → multiple Surge accounts → you may have bound the X handle linked to a different Surge account than the one you're comparing against. Unbind and re-connect with the right X handle (Q31).
• Surge bot-sweep. If Surge cleans up bot activity on their side, your active_amount can drop — we mirror what Surge says.

If you haven't verified X yet, the dashboard shows your Ignite total as 0 (Self-Report from screenshots is kept for your own visibility but doesn't enter the payout formula). Verify X to activate the API lookup — see Q29.

Cross-check anytime by opening surge.twin3.ai/api — that page reads directly from the latest Surge API snapshot.

The dashboard reflects your live Surge API active_amount, so a drop almost always traces back to one of:

1. You reallocated on Surge. If you moved Ignites from twin3 to another project, your active_amount for twin3 drops accordingly.
2. You unbound X. Without an active binding, your displayed total drops to 0 (Q31). Rebind and the number returns.
3. Surge bot-sweep. If Surge.xyz flagged some activity on your account as inauthentic and cleaned it, your active_amount drops. We mirror their state.
4. You re-bound to a different X handle (unbind then re-connect). Each X handle links to a different Surge account; the new one may have a different Ignite total.

Open surge.twin3.ai/api to verify what the live Surge API currently says for your account.

If Surge cleaned an account you believe was legitimate, raise it with Surge directly — Twin3 mirrors their state and has no control over their bot-cleanup decisions.

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.

The displayed number comes straight from the Surge API for the Surge account linked to your verified X handle. To get the dashboard to match your real Surge total:

1. Verify X on surge.twin3.ai if you haven't. Without verification your dashboard total is 0 — see Q29.
2. Check you bound the right X handle. If you have multiple Surge accounts (linked to different X handles), the dashboard reflects only the currently-bound one. Unbind and re-connect with the X handle associated with the Surge account whose number you're looking at (Q31).
3. Vote / re-allocate on surge.xyz/discovery/twin3 if your Surge.xyz total itself is the one that's wrong.
4. Wait up to an hour for the next API sync, then refresh.

Cross-check anytime at surge.twin3.ai/api — that page reads the latest Surge API snapshot directly.

Screenshots are still verified by Lucy as Self-Report data (visible on your profile under "Self-Report"), but Self-Report doesn't enter the payout formula. Verification + Surge API does.

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.

Surge.xyz stores an X handle for nearly every voter, so the X handle is the only reliable bridge between your Discord account and your Surge.xyz Ignite total.

When you sign in with X on surge.twin3.ai, we look up your X handle in Surge's records, find your Surge user_id, and from then on your dashboard score reflects your real Surge API active_amount — not what the OCR thinks it sees in your screenshot.

Without verification, your screenshot-based number is shown as Self-Report only and will not count toward final payout. Your invitees (and you, if your inviter wants to earn their 10%) must verify for invite credit to be paid.

We read your X handle only. We never post on your behalf.

No. Your Discord invite link (surge.twin3.ai/i/<your-token>) is permanent and unaffected by Twitter verification. Same goes for the invite chain — who invited whom is tracked entirely by Discord user IDs, and verifying X doesn't touch any of that.

The only thing that changes is the source of truth for your displayed Ignites total: before verification it's screenshot-OCR (with all the noise that implies); after, it's the Surge API number directly.

Yes — any time. Open your profile (/u/<your-token>) and on your own page you'll see a 🔓 Unbind button. Clicking it clears the current binding — your dashboard Ignites drop to 0 until you bind again. Your previous binding is kept in your record for audit; it just stops counting.

To switch to a different X account: unbind first, then click 🐦 Connect X again and sign in with the other handle. Two-step instead of one, but the outcome is the same.

One Surge identity can only be claimed by one Discord account at a time. If you try to bind an X handle that's already linked to someone else's Surge profile in our records, the binding is rejected with a clear error.