Troubleshooting

Common issues and solutions when using the Seesaw Protocol.

Transaction Failures

Insufficient Funds

Error: InsufficientCollateral (0x3002)

Cause: Not enough USDC in your wallet for the order.

Solution:

1. Check your USDC balance
2. Ensure you have enough for: price × quantity + fees
3. Account for any existing open orders that lock collateral

Required = (price_bps × quantity / 10000) + taker_fee
Example: 5000 bps × 100 shares = 50 USDC + 0.15 USDC fee

Insufficient Shares

Error: InsufficientShares (0x3003)

Cause: Trying to sell more shares than you own.

Solution:

1. Check your position in the Portfolio tab
2. Account for shares locked in existing sell orders
3. Reduce your sell quantity

Order Would Cross

Error: WouldCross (0x3006)

Cause: Your PostOnly order would immediately match with an existing order.

Solution:

• Adjust your price to not cross the spread
• Use a regular Limit order instead of PostOnly
• Check the current best bid/ask before submitting

Order Book Full

Error: OrderbookFull (0x3004)

Cause: The order book has reached its 64 order per side limit.

Solution:

1. Wait for existing orders to fill or be cancelled
2. Try again in a few seconds
3. Use a price that will match immediately

Trading Ended

Error: TradingEnded (0x1005)

Cause: The market's trading period has closed.

Solution:

• Wait for the next market to open
• Markets open on their configured cadence
• Check the countdown timer before submitting orders

Transaction Timeout

Symptom: Transaction submitted but never confirms.

Possible Causes:

• Network congestion
• Insufficient priority fee
• RPC node issues

Solutions:

1. Retry with higher priority fee
2. Switch to a different RPC endpoint
3. Wait and check if the transaction eventually confirms

Wallet Connection Issues

Wallet Not Detected

Symptom: "Connect Wallet" doesn't show your wallet.

Solutions:

1. Ensure your wallet extension is installed and enabled
2. Refresh the page
3. Check if the wallet is unlocked
4. Try a different browser
5. Disable other wallet extensions that might conflict

Connection Rejected

Symptom: Wallet popup appears but connection fails.

Solutions:

1. Make sure to click "Approve" in the wallet popup
2. Check if you're on the correct network (mainnet vs devnet)
3. Clear browser cache and try again
4. Reinstall the wallet extension

Wrong Network

Symptom: Connected but transactions fail or show wrong balances.

Solutions:

1. Open your wallet settings
2. Switch to the correct network:
   • Mainnet: mainnet-beta
   • Devnet: devnet
3. Refresh the page after switching

Session Expired

Symptom: Was connected, now shows "Connect Wallet".

Solutions:

1. Reconnect your wallet
2. Check if wallet auto-lock timer triggered
3. Browser may have cleared the connection state

Oracle Price Issues

Stale Oracle Price

Error: StaleOracle (0x2004)

Cause: The Pyth price feed hasn't updated recently.

Solutions:

1. Wait a few seconds and retry
2. This is usually temporary during network issues
3. Check Pyth status page for feed status

Confidence Too Wide

Error: ConfidenceTooWide (0x2006)

Cause: The oracle price confidence interval is too large.

Why This Happens:

• High market volatility
• Low liquidity on exchanges
• Exchange data feed issues

Solutions:

1. Wait for market conditions to stabilize
2. This protects you from trading on uncertain prices
3. Usually resolves within seconds

Oracle Not Trading

Error: OracleNotTrading (0x2007)

Cause: The Pyth price feed is in a non-trading state.

Solutions:

1. Wait for the feed to resume
2. Check Pyth Network status
3. This can happen during exchange maintenance windows

Network and RPC Issues

RPC Rate Limited

Symptom: Requests failing with rate limit errors.

Solutions:

1. Use a dedicated RPC endpoint (Helius, QuickNode, Triton)
2. Reduce request frequency
3. Implement exponential backoff

Connection Dropped

Symptom: WebSocket disconnects or data stops updating.

Solutions:

1. Check your internet connection
2. Refresh the page
3. The app should auto-reconnect
4. Try a different RPC provider

Transaction Simulation Failed

Symptom: Transaction fails before even being sent.

Possible Causes:

• Stale account data
• Invalid instruction parameters
• Account doesn't exist

Solutions:

1. Refresh market data
2. Verify all account addresses
3. Check if the market is in the correct state

Blockhash Expired

Symptom: Transaction fails with "blockhash not found".

Cause: Too much time passed between creating and submitting the transaction.

Solutions:

1. Retry immediately with fresh blockhash
2. Use faster RPC endpoint
3. Sign and submit transactions more quickly

Position and Settlement Issues

Cannot Claim Winnings

Symptom: Claim button doesn't work or transaction fails.

Possible Causes:

• Market not yet resolved
• Position already claimed
• Insufficient SOL for fees

Solutions:

1. Wait for market resolution (check market state)
2. Verify you haven't already claimed
3. Ensure you have SOL for transaction fees

Position Not Showing

Symptom: Made a trade but position doesn't appear.

Possible Causes:

• Transaction didn't confirm
• UI needs refresh
• Looking at wrong market

Solutions:

1. Check transaction status in your wallet
2. Refresh the Portfolio page
3. Verify you're viewing the correct market

Wrong Payout Amount

Symptom: Received less than expected.

Explanation:

• Winning shares pay 1 USDC each
• Losing shares pay 0 USDC
• Fees are deducted on trade, not settlement
• Check if you had partial fills

Performance Issues

Slow Page Load

Solutions:

1. Check internet connection speed
2. Try a different browser
3. Clear browser cache
4. Disable browser extensions

Real-Time Updates Delayed

Solutions:

1. WebSocket might be reconnecting
2. Refresh the page
3. Check RPC endpoint status
4. Try a different RPC provider

Getting Help

If you've tried the above solutions and still have issues:

1. Check Documentation: Review relevant docs for your issue
2. Search Discord: Many issues have been discussed before
3. Ask in Discord: Post in #support with:
   • Error message or code
   • Transaction signature (if applicable)
   • Steps to reproduce
   • Wallet type and browser
4. Open GitHub Issue: For bugs or feature requests

Useful Information to Include

When reporting issues, provide:

- Wallet: [Phantom/Solflare/Backpack]
- Browser: [Chrome/Firefox/Safari]
- Network: [Mainnet/Devnet]
- Error Code: [e.g., 0x3002]
- Transaction Signature: [if applicable]
- Steps to Reproduce: [what you did]
- Expected Result: [what should happen]
- Actual Result: [what happened]

Error Code Quick Reference

See Error Codes for the complete list.