how it works
create a coin
@sporkyperps $ TICKER LONG
@sporkyperps $ TICKER SHORT
creator steps
1. Connect Phantom or Solflare and verify X with the generated code.
2. Save the coin details and chosen initial buy.
3. Post one exact command. Keep a space between $ and the ticker. The LONG or SHORT side is fixed once accepted.
4. Open the dashboard link in Sporky's reply. The tweet does not broadcast a coin.
5. Approve the one-time setup if needed, then separately approve the fresh direct Solana launch. The creator wallet pays the initial buy, rent and network fees.
6. After confirmation, the deployed reply includes the CA, token page and Pump link.
Valid commands from an unverified account receive a verification link. Verified creators without a saved setup receive a setup link.
operator reward rounds
100% of creator fees route to the project rewards wallet. The operator claims them manually on Pump, then Refresh records finalized per-coin claim receipts. Wallet deposits alone are not reward income.
A round locks only confirmed, unallocated rewards. Funding swaps its SOL to USDC. LONG backing is explicitly purchased as the configured SPCXx asset; SHORT backing remains USDC. Existing outside holdings are never attached automatically.
Start records a reliable current price and begins 15 minutes. New claims wait for the next round. End, or the timer, freezes a synthetic 2x directional target with loss capped at backing.
Settlement is separate and manual: sell tracked SPCXx, convert settled USDC to SOL, then pay each coin's recorded creator wallet. An optional operator USDC reserve can support settlement. If funds are short, payouts are prorated toward targets.
This is an operator-custodied synthetic calculation backed by tokens and USDC, not a perpetual or brokerage fill. The target is not guaranteed. SPCXx is the configured round asset, mint Xs3oZwbHvqis4NYcf4YKWmEia2eC84wSiVrcYcTqpH8; this site does not claim official SpaceX equity entitlement.
Round announcements describe recorded start, close and paid states only. Live readiness and reply status are shown from the backend.
