dflow-phantom-connect

Files (24)

• SKILL.md
• browser-sdk.md · references/
• dflow-crypto-trading.md · references/
• dflow-prediction-markets.md · references/
• dflow-proof.md · references/
• dflow-websockets.md · references/
• nft-minting.md · references/
• payments.md · references/
• react-native-sdk.md · references/
• react-sdk.md · references/
• token-gating.md · references/
• transactions.md · references/
• SKILL.md · skill/
• browser-sdk.md · skill/references/
• dflow-crypto-trading.md · skill/references/
• dflow-prediction-markets.md · skill/references/
• dflow-proof.md · skill/references/
• dflow-websockets.md · skill/references/
• nft-minting.md · skill/references/
• payments.md · skill/references/
• react-native-sdk.md · skill/references/
• react-sdk.md · skill/references/
• token-gating.md · skill/references/
• transactions.md · skill/references/

SKILL.md (first lines)

# Phantom Connect + DFlow Skill

## Instructions

### Step 1: Identify What the User Wants to Build

Determine the domain, then route to the right references.

**Wallet connection and Solana interactions:**

- Connecting a Phantom wallet (React, React Native, vanilla JS)
- Signing messages or transactions
- Token-gated access
- NFT minting
- Crypto payments
- Solana transfers (SOL or SPL tokens)

**DFlow trading:**

- Spot token swaps (imperative or declarative)
- Prediction market discovery, trading, and redemption
- Proof KYC identity verification

Many tasks combine both (e.g., a swap UI needs wallet connection AND DFlow trading). Read all relevant references before writing code.

### Step 2: Read the Relevant References

**Phantom Connect SDKs** (wallet connection, signing, auth):

- `references/react-sdk.md` — React hooks, components, theming, PhantomProvider
- `references/react-native-sdk.md` — Expo config, polyfills, deep links, mobile auth
- `references/browser-sdk.md` — BrowserSDK init, events, wallet discovery, vanilla JS

**Solana patterns** (transactions, gating, minting, payments):

- `references/transactions.md` — SOL/SPL transfers, signing, fee estimation
- `references/token-gating.md` — client-side and server-side token-gated access
- `references/nft-minting.md` — mint pages, Metaplex Core, compressed NFTs
- `references/payments.md` — SOL/USDC payments, checkout with backend verification

**DFlow trading** (swaps, prediction markets, KYC):

- `references/dflow-crypto-trading.md` — spot token swaps, imperative vs declarative trades, slippage, priority fees, platform fees
- `references/dflow-prediction-markets.md` — market discovery, trading, redemption, maintenance windows, fee models
- `references/dflow-websockets.md` — real-time price, trade, and orderbook streaming via WebSocket
- `references/dflow-proof.md` — Proof KYC verification (required for prediction market trades, usable for any gated feature)

### Step 3: Ask the Right Questions

Before implementing, ask questions based on the domain:

**For Phantom Connect tasks:**

- Which platform? (React, React Native, vanilla JS)
- Do they need social login (Google/Apple) or extension only?

**For DFlow spot trades:**

- Imperative or declarative? If unsure, suggest starting with imperative.
- Dev or production endpoints? If production, remind them to apply for an API key at pond.dflow.net/build/api-key.
- Platform fees? If yes, what bps and what fee account?
- Client environment? (web, mobile, backend, CLI)

**For DFlow prediction markets:**

- Settlement mint? (USDC or CASH — these are the only two)
- Dev or production endpoints? If production, remind them to apply for an API key at pond.dflow.net/build/api-key.
- Platform fees? If yes, use `platformFeeScale` for dynamic fees.
- Client environment? (web, mobile, backend, CLI)

### Step 4: Implement

Follow the patterns in the reference files. Key rules by domain:

**Phantom Connect:**

- All SDK details (provider setup, hooks, components, auth providers) are in the SDK reference files. Read them before writing Phantom integration code.

**DFlow Trading:**

- Dev endpoints (`dev-quote-api.dflow.net`, `dev-prediction-markets-api.dflow.net`, `wss://dev-prediction-markets-api.dflow.net/api/v1/ws`) work without an API key but are rate-limited. Production requires a key from pond.dflow.net/build/api-key.
- Prediction market trades require Proof KYC before buying or selling outcome tokens. Browsing and discovery do not require KYC.
- Prediction markets also require geoblocking for restricted jurisdictions.

### Step 5: Handle Errors

Each reference file contains domain-specific error handling. Key cross-cutting concerns:

- User rejects a transaction or signature request
- Wallet not connected when a signed action is attempted
- DFlow API returns 429 (rate limited) — retry with backoff or get a production API key
- `route_not_found` from DFlow — check amount units (must be atomic), check liquidity, check mint addresses

## Examples

### Example 1: React wallet connection

User says: "Add Phantom wallet login to my Next.js app"

Actions:

1. Read `references/react-sdk.md`
2. Install `@phantom/react-sdk`
3. Wrap app in PhantomProvider with desired auth providers and appId
4. Use `useModal` hook for a connect button
5. Use `useAccounts` to display the connected wallet address

Result: Working wallet connection with social login and extension support

### Example 2: Token-gated page

User says: "Build a page that only BONK holders can see"

Actions:

1. Read `references/react-sdk.md` and `references/token-gating.md`
2. Set up wallet connection
3. Query the BONK token balance for the connected wallet
4. Conditionally render content based on balance threshold

From x402agent/solana-clawd, MIT.

More from x402agent/solana-clawd