How to claim Pyth airdrop rewards? (Wallet connection)

Wallet Connection Requirements

1. Pyth Network airdrop eligibility depends on verified on-chain activity across supported chains including Solana, Ethereum, and Arbitrum.

2. Users must connect a wallet that has interacted with Pyth price feeds or participated in designated ecosystem protocols before the snapshot date.

3. Wallets must be non-custodial — exchanges or hosted wallets like Binance or Coinbase are not eligible for direct claim.

4. The connected wallet must hold a minimum balance of native gas tokens: 0.01 SOL on Solana, 0.005 ETH on Ethereum, or 0.01 ARB on Arbitrum at the time of connection.

5. Multi-signature wallets require all signers to approve the connection request through the official Pyth dApp interface.

Supported Wallet Types

1. Phantom, Backpack, and Slope are fully supported for Solana-based claims.

2. MetaMask, Trust Wallet, and Rabby are verified for Ethereum and EVM-compatible chains.

3. Keplr is not supported despite its Cosmos integration — Pyth’s current airdrop infrastructure excludes IBC-connected wallets.

4. Ledger hardware wallets must be accessed via Ledger Live browser extension or compatible interface; direct USB connection without approved signing layer will fail validation.

5. Wallets using custom RPC endpoints may encounter signature mismatches unless they match Pyth’s officially listed node providers.

Connection Flow Steps

1. Navigate to the official Pyth airdrop portal at airdrop.pyth.network — no third-party domains are authorized.

2. Click “Connect Wallet” and select the wallet extension matching your browser environment.

3. Approve two sequential signatures: first for wallet address verification, second for message authentication using EIP-191 standard.

4. After confirmation, the interface displays real-time eligibility status and estimated reward amount in PYTH tokens.

5. If the wallet shows “Pending Validation”, users must wait up to 90 seconds for on-chain reconciliation before proceeding to claim.

Common Signature Failures

1. Browser extensions blocking script injection cause silent rejection — disabling ad-blockers and privacy tools during connection resolves 73% of cases.

2. Time skew exceeding 30 seconds between device clock and NTP servers invalidates EIP-1271 verification payloads.

3. Reusing the same wallet across multiple browsers triggers session conflict — only one active connection per wallet is permitted.

4. Attempting connection from incognito mode without re-enabling required wallet extensions results in “Provider Not Found” error.

5. Mobile Safari users must enable “Desktop Site” toggle before initiating connection; mobile rendering breaks signature encoding logic.

Frequently Asked Questions

Q: Can I connect more than one wallet to check eligibility?A: Yes, but each wallet must be connected separately and independently — batch checking is not supported.

Q: What happens if my wallet was compromised before the snapshot?A: Compromised wallets with unauthorized transactions during the eligibility window are flagged and excluded from distribution after forensic review.

Q: Does connecting a wallet automatically initiate the claim?A: No — connection only verifies eligibility; users must manually click “Claim Now” after validation completes.

Q: Are wrapped tokens counted toward eligibility criteria?A: Wrapped assets such as wETH or wsol are recognized only if the wrapping contract is whitelisted by Pyth governance — unofficial wrappers are ignored.