Product reference

Docs & risks

How the controlled swap beta and direct user-owned liquidity boundary work, what is disabled, and what every user should verify.

Robinhood Chain mainnet reference · No wallet network required
Direct liquidity remains NO_GO and disabled. No mainnet liquidity approval, deposit, or canary is authorized.

Product scope

The root trade terminal is a live controlled mainnet swap beta for server-resolved tokens on Robinhood Chain. Pools and Portfolio describe a separate direct, user-owned Robinhood mainnet liquidity boundary. Its transaction path remains NO_GO and disabled; visible pages and prepared-plan code are not approval to transact. Rewards, incentives, analytics, the historical gauge indexer, and fixture campaign data remain deferred or explicitly labeled showcase evidence.

Both mainnet boundaries are non-custodial: Feather Fi cannot move assets without exact transactions signed by the connected wallet.

Mainnet swap

Feather Fi requests routes from 0x. The You receive field shows a non-executable estimate as the amount, token pair, or slippage changes, including before a wallet is connected. Estimates contain no transaction payload and cannot authorize a wallet action. Select Review swap to inspect the exact sell amount, expected output, minimum received, separate token-denominated fees, estimated network cost, and expiry. Opening or refreshing review never opens a wallet transaction prompt.

Native ETH sells and ERC-20 sells with an already exact allowance receive a fresh executable quote for review. Other ERC-20 sells first receive a non-executable review with an explicit token-approval action. Any nonzero mismatched allowance is reset to zero before approving the exact sell amount. Each required approval is a separate wallet-signed transaction with its own gas cost. After all approvals confirm, a fresh executable quote is shown for a separate Confirm swap action.

Executable quotes are bound to Robinhood Chain mainnet (4663), the connected taker address, server-resolved token descriptors, sell amount, and selected slippage. The verified starter registry includes ETH, USDG, and WETH; a custom ERC-20 can be imported by contract address only after Feather Fi resolves its current code and canonical metadata. Verified-list membership is not a safety or audit endorsement.

Slippage defaults to 1%, with presets of 0.1%, 0.5%, and 1%, and custom values from 0.01% to 1% in 0.01% steps. The 1% maximum is unchanged. Editing the amount, tokens, slippage, account, or chain invalidates the current review. Executable quotes expire after 15 seconds and are not automatically refreshed; expiry blocks confirmation until Refresh quote returns a new quote that is reviewed again. Confirm swap revalidates the current review and requests the exact validated transaction in the wallet. If submission produces a hash but confirmation is unavailable, use Check transaction in the current session and retain the hash for explorer verification.

Direct user-owned liquidity

LP v1 is fixed to the existing WETH/USDG Uniswap v4 pool on Robinhood Chain mainnet (4663), zero hooks, the 0.30% nominal pool fee tier, and an aligned full range. If enabled after every release gate, the externally owned wallet would supply both WETH and USDG, own the PositionManager NFT, and retain the position's Uniswap fees. Safe and ERC-4337 smart accounts are not supported in v1. Feather Fi deploys no AMM, vault, gauge, hook, strategy, share token, or custody contract and currently charges no Feather Fi liquidity-action fee.

Create, collect, and full close must ship as one reviewed lifecycle. Exact ERC-20 and Permit2 approvals, post-action cleanup, fresh simulation, receipt verification, replacement recovery, and finality reconciliation are mandatory. Full range does not prevent impermanent loss, preserve principal, or guarantee fees.

Prepared plans, data, and recovery

Liquidity preparation is unauthenticated and does not prove wallet control. Before a transaction prompt, the wallet signs a domain-separated authorization for one intent, step, and pending nonce; Feather Fi verifies it, stores the public nonce reservation, and does not retain the raw signature. The prepared intent contains intended amounts, allowance state, exact targets and calldata, transaction order, limits, and expiry; Feather Fi treats the full plan as private offchain data. Neon stores the plan, bounded evidence, transaction lineage, receipts, and provisional, finalized, or orphaned state. The initiating browser stores a local pending journal and random capability; only one full pending journal is retained per wallet. The server stores only the capability hash. The capability cannot sign or move assets, but it authorizes private recovery access and should not be shared. A finalized approval stage keeps that capability until a fresh mint plan or authenticated cleanup atomically replaces it, so cleanup remains available after a tab close or release pause. Completed handoffs retain only bounded local pointers that expire on the next app use after 30 days, and the panel provides recovery export and pointer deletion controls.

Once a hash exists, Feather Fi follows that hash and any wallet replacement rather than blindly resubmitting. If the page closes before the hash is saved, the nonce barrier remains and the panel can server-verify a hash copied from the wallet or explorer. The server classifies an exact replacement, a self-cancellation, or unrelated activity from the same wallet at the reserved nonce. Unrelated activity is never labeled as the LP action; it remains review evidence and permits authenticated allowance cleanup only after finality. A zero-value self-cancellation is available only when both the wallet transport and canonical RPC report that exact reserved nonce as unused; every cancellation is user-signed, gas-paying, receipt-verified, and marked for review. The browser journal is a recovery copy, and Neon history is an operational record; neither overrides canonical Robinhood Chain receipts, block hashes, NFT ownership, or position state. Broadcast wallet addresses, calldata, approvals, NFT transfers, receipts, and logs are public. See the Privacy Notice for retention, access, and deletion limits.

Validation before submission

For swaps, the browser and server validate the resolved pair, chain, authoritative minimum and technical bounds, taker, selected slippage, fees, allowance target, transaction target, value, calldata semantics, route, complete provider simulation result, and expiry. For liquidity, the accepted configuration fixes the chain, pool, tokens, managers, zero-hook policy, full range, recipient, step order, amount bounds, and deadlines. Swap confirmation submits the exact validated 0x transaction after rechecking the current review, wallet, expiry, and readiness. Approval and liquidity steps retain their own exact simulation checks.

A final readiness check runs before wallet submission. If the relevant kill switch is off, the accepted configuration is missing or stale, or readiness cannot be verified, the action fails closed. LP v1 remains disabled regardless of read-only page availability.

Fees & limits

  • ETH/WETH minimum swap sell amount: 0.00001.
  • USDG minimum swap sell amount: 0.01 USDG.
  • Custom ERC-20 swap minimum: one-millionth token, or one base unit below six decimals.
  • There is no product-level swap maximum. Wallet balance, native gas reserve, available route liquidity, the displayed minimum output and other transaction bounds, provider acceptance, simulation, and the EVM range determine what can execute.
  • Swap slippage: 0.01%–1%, default 1%. The selected tolerance applies to estimates and executable quotes and is shown with minimum received.
  • Feather Fi swap integrator fee: 15 bps, disclosed in the quote. The independently disclosed 0x routing fee may use another pair token and is not collected by Feather Fi.
  • LP v1 currently has no Feather Fi liquidity-action fee. Its accepted plan uses 50 bps amount protection and rejects policy above 100 bps; Uniswap pool fees and network gas remain separate.
  • Network gas is paid by the wallet for every approval and action. Fees and network cost are displayed separately in their own token units; amounts in different tokens are never added into a combined total.

Feather Fi may pause execution or tighten policy during an incident. No displayed balance, preview, route, amount, fee, or position is a promise that a transaction will execute or preserve value.

Deferred and showcase surfaces

Rewards, incentives, analytics, the historical chain-46630 gauge path, and deterministic campaign fixtures are not the current LP release. Fixture metrics, APRs, balances, volumes, transactions, and rewards are not live mainnet claims. Pools and Portfolio describe the mainnet user-owned boundary, but their write path remains disabled until the machine-readable LP release state changes from NO_GO through an explicitly authorized release.

Risk disclosures

Smart contractsThird-party token, router, allowance, and chain contracts can contain defects or change behavior.
Routing0x route availability, pricing, liquidity, and simulation can fail or become stale before submission.
LiquidityWETH/USDG positions can lose value through price movement, impermanent loss, token risk, upstream changes, or transaction failure.
WalletsA compromised wallet, malicious extension, or incorrect signature can cause irreversible loss.
MarketPrice impact, volatile assets, thin liquidity, MEV, and failed transactions can change outcomes.
Data and recoveryA local journal or Neon record can be unavailable or stale; canonical chain state and receipt finality take priority.
InfrastructureRobinhood Chain RPC, explorers, Vercel, Reown, or 0x may become unavailable.
Beta softwareValidation reduces execution risk; it does not make beta software risk-free.

No quoted output, minimum received amount, APR, incentive, reward, or route is a promise of profit or successful execution.

Independence and third parties

Feather Fi is an independent product. It is not affiliated with, sponsored by, or endorsed by Robinhood. Robinhood names and chain references identify the supported network only. 0x, Reown, Vercel, Neon, Uniswap, Permit2, RPCs, and explorers are third-party systems with their own availability, privacy, and security characteristics.

Terms → Privacy → API reference →