Skip to main content
Pixie is built specifically for Solana, leveraging its high-throughput architecture for sub-second transaction execution.

Wallet Connection

Pixie supports all major Solana wallets through the Wallet Adapter standard:

Phantom

Most popular Solana wallet

Solflare

Feature-rich mobile and browser wallet

Backpack

Multi-chain wallet with Solana support

Connection Flow

1

User Clicks Connect

Pixie triggers wallet adapter connection modal
2

Select Wallet

User chooses their preferred wallet provider
3

Approve Connection

Wallet prompts for read-only access approval
4

Connection Established

Pixie receives public key and can query balances

Transaction Signing

All transactions require explicit user approval in their wallet:
const transaction = await buildSwapTransaction({
  inputMint: SOL_MINT,
  outputMint: USDC_MINT,
  amount: 5_000_000_000
});

// User must approve in wallet
const signature = await wallet.signAndSendTransaction(transaction);
Pixie never has access to your private keys. All transaction signing happens in your wallet, not in Pixie’s code.

RPC Configuration

Pixie uses premium RPC providers for reliability and speed:
ProviderEndpointFeatures
Heliushttps://mainnet.helius-rpc.comPriority access, WebSockets
Tritonhttps://solana-mainnet.rpc.triton.oneHigh throughput
QuickNodehttps://solana-mainnet.quiknode.proGlobal CDN

Network Selection

Pixie supports multiple Solana networks:
  • Mainnet Beta: Production environment (default)
  • Devnet: Testing environment for developers
  • Localnet: Local validator for development

Token Standards

Pixie supports all Solana token standards:

SPL Tokens

Standard Solana Program Library tokens

Token-2022

New standard with transfer fees and extensions

Wrapped Assets

wSOL, wBTC, wETH bridged from other chains

NFTs

Metaplex NFT standard (view only)

Account Monitoring

Pixie monitors your wallet for:
  • Balance changes
  • New token accounts
  • Incoming transfers
  • Transaction confirmations
Update Frequency: Real-time via WebSocket subscriptions

Transaction Confirmation

Pixie tracks transactions through multiple commitment levels:
LevelDescriptionTime
ProcessedIncluded in a block~400ms
ConfirmedConfirmed by supermajority~13s
FinalizedCannot be rolled back~13s
Default: Confirmed (optimal balance of speed and security)

Compute Budget

Pixie automatically sets optimal compute units for transactions:
const computeUnitLimit = ComputeBudgetProgram.setComputeUnitLimit({
  units: 200_000
});

const computeUnitPrice = ComputeBudgetProgram.setComputeUnitPrice({
  microLamports: 1_000 // Priority fee
});

Error Handling

Common Solana errors and how Pixie handles them:
ErrorCausePixie Response
Insufficient SOLNot enough for feesPrompt to add SOL
Slippage ExceededPrice moved too muchRefresh quote and retry
Blockhash ExpiredTransaction took too longRebuild with new blockhash
Account Not FoundToken account doesn’t existCreate account automatically
Pixie automatically creates associated token accounts when needed. This adds ~0.002 SOL to transaction cost.

Performance Metrics

MetricValue
RPC Latency (p50)38ms
Transaction Broadcast4ms
WebSocket Latency15ms
Balance Query32ms

Solana Documentation

Learn more about Solana’s architecture