WAGER documentation
Your call. Their challenge.
Create a challenge, commit equal stakes and agree on the result.
Your account and wallet
Sign in with X through Privy. WAGER links your account to your permanent X user ID, so changing your handle does not transfer your wagers. Your account receives a Solana deposit wallet when wallet provisioning is available. Public profiles show wager history, not private balances or deposit addresses.
The Wallet page shows available funds, funds committed to wagers and pending withdrawals separately. Only supported assets sent to the displayed network and address can be credited. A transaction must finalize successfully before a deposit becomes available.
Create a pending wager
Choose an opponent, asset, equal stake amount, condition, evidence source, acceptance deadline and resolution time. The creator backs Yes: the condition is true. The opponent backs No: the condition is false. Write an objective condition that both people can verify.
You can publish a pending challenge without funding it first, and the opponent can join WAGER later. A pending challenge is not a funded pot. Both participants must sign in and commit the required equal stakes before it becomes active. Published terms and the fee rule are fixed.
Challenge someone on X
Enable X wagering in your Wallet settings and choose per-wager and daily spending limits before using the bot. The bot only responds to accounts registered with WAGER. It identifies authors by their X account ID, not their display name.
Mention @usewagerfun using: wager @opponent 25 USDC, followed by a quoted condition, accept-by:YYYY-MM-DDTHH:mmZ, resolve:YYYY-MM-DDTHH:mmZ and source: followed by a public URL. Use future UTC times, with acceptance before resolution. Include every field so the bot can record unambiguous terms.
The opponent replies accept directly to the challenge or its bot receipt, or uses accept followed by the wager ID. Only the named opponent can accept. WAGER validates the post author, reply reference, deadline, limits and available funds. USDC is currently supported for X commands; WAGER commands require a verified price feed.
Mentions and replies are polled automatically. A pending wager can appear on the site before the bot reply arrives. X rate limits, outages and post visibility can delay processing. Protected or inaccessible posts should use website actions instead.
Funding and activation
Funding reserves your stake so it cannot also be spent on another wager or withdrawal. The wager becomes active when both sides have committed their stakes. A repeated request cannot reserve or spend the same funds twice.
The creator can cancel before activation and the opponent can decline. Challenges that expire before activation release any committed stakes without a fee. Once active, neither participant can change the terms or cancel unilaterally.
Results and disputes
At the resolution time, both participants have 48 hours to submit the winner or a void result through the wager page. Matching decisions settle the wager. Both participants can also agree to void an active wager.
Conflicting decisions or non-response enter dispute review. Silence does not award a win. Review has a seven-day deadline; unresolved cases refund both stakes. Keep the agreed evidence source available and use precise terms that can be checked at the resolution time.
Payouts and the platform fee
The winner receives the combined stakes minus 2% of the total pot, credited in the original wager asset. For two 100 USDC stakes, the pot is 200 USDC, the fee is 4 USDC and the winner receives 196 USDC. Fees round down to whole base units.
Refunds have no platform fee. Settled results and money movements are recorded once, even if a request is retried. Payouts credit your platform balance; withdrawing to another wallet is a separate action.
Deposits and withdrawals
Use the Wallet page for the current deposit address, supported assets and network. Funds are held in platform custody. An X login is not a seed phrase and does not make a platform deposit wallet an independently controlled wallet.
Withdrawals require recent authentication and a second factor. The requested amount is reserved first, then sent and checked against finalized chain evidence. An uncertain broadcast remains pending while reconciliation checks it; a timeout alone does not mean the transfer failed.
Deposit crediting, funding, acceptance and withdrawals depend on operational availability. If financial operations are paused, creating pending challenges does not imply that deposits or payments are enabled.
WAGER token and holder rewards
The token page checks the configured platform mint on Solana mainnet and refreshes market statistics automatically. Supply comes from verified mint data. Price and holder statistics depend on the market-data provider. Unavailable or not-yet-launched values are shown as unavailable, not estimates.
Collected platform fees are allocated to holder rewards. Reward epochs require complete holder indexing and verified acquired tokens before allocation. Missing indexing or unconverted fees pause an epoch. The reward page shows published epoch status and your claimable allocations; unpublished rewards are not claimable.
Token market data becoming available does not itself enable token deposits, wagering, buybacks or distributions. Those depend on the supported mint configuration, custody and reward infrastructure.
Live discovery and rankings
Pending challenges are listed separately from live wagers. Use status and category filters to find wagers, open the detail page to read the immutable terms, or browse profiles to challenge a user directly.
Volume counts both stakes once a wager becomes active. Rankings use settled results and profit after fees; pending wagers do not count as wins. Native-asset amounts remain available when a reliable dollar price is missing.