> For the complete documentation index, see [llms.txt](https://aboutcryptotalks.gitbook.io/aboutcrypto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aboutcryptotalks.gitbook.io/aboutcrypto/spookyswap-choosing-between-swaps-pools-and-boo-farms.md). # SpookySwap: Choosing Between Swaps, Pools and BOO Farms SpookySwap is a decentralized exchange where you trade tokens against liquidity pools or deposit tokens to earn from trading activity. The deciding question is whether you want a different token now or are willing to hold a changing mix of two tokens in pursuit of fees and rewards. Check the chain first: Fantom and Sonic have separate assets, pools and network fees. * Swap when your goal is to receive a token and finish the transaction. * Provide liquidity when expected trading fees justify exposure to both tokens. * Farm only after checking what the BOO reward adds to a liquidity position. ### The Chain Determines Which Pool You Can Use Choose the chain where you hold the right tokens and where the pair has enough liquidity for your intended amount. When you are ready to exchange them, [SpookySwap](https://spookyswaps.app) trades your tokens against a pool in the Fantom or Sonic ecosystem. SpookySwap on Fantom and its Sonic pools have separate liquidity, so a familiar pair name does not guarantee the same price on both chains. Your wallet also needs the chain’s native token for network fees: FTM on Fantom or S on Sonic. Check the token’s contract address on the selected chain, especially when several tokens share a ticker; the name alone does not establish that they are the asset you intended. If your funds are on the other chain, moving the tokens is a separate step, with its own cost and risk. That distinction matters for an old Fantom liquidity position. It does not become a Sonic position when you switch your wallet’s network: you must withdraw it, move each asset by an available route and supply liquidity again on Sonic. Check the current route for each token before withdrawing, since a route for FTM does not necessarily cover other tokens. ### A Swap Fits a One-Token Goal Use a swap when you want to exchange one asset for another without maintaining a position afterward. An automated market maker prices the trade from tokens held in a pool; your trade changes their balance and therefore the price. Before signing, compare the quoted output with the amount you would receive elsewhere for the same token and chain. Look at the pool fee, price impact and slippage tolerance separately. SpookySwap V3 pool fees typically fall between 0.01% and 1% of the trade, depending on the pool; a 0.30% fee is $3 on a $1,000 swap. Price impact is the price change caused by the size of your trade, while slippage tolerance sets how far the execution price may move before the transaction fails. A shallow pool can make price impact cost more than the stated fee. I would reduce the trade size or wait for a deeper pool if the quoted output were materially below the market value I expected. At spookyswaps.app, I would carry out the swap only after checking the token address, network and amount to receive. ### Liquidity Makes Sense When Fees Cover the Exposure Provide liquidity when you are content to own either token in the pair and expect trading fees to compensate you for changes in their relative prices. A typical two-token deposit starts with equal market values, and traders then exchange against those assets. SpookySwap liquidity providers earn the fees assigned to their pool, but the number of each token they can withdraw changes as trading changes the pool’s balance. Consider a simplified pool deposit of $500 in a stablecoin and $500 in another token. If that token doubles in price, simply holding both would leave you with $1,500; a basic constant-product liquidity position would be worth about $1,414 before fees. The roughly $86 gap is *impermanent loss*: the position sold some of the rising token as its price climbed, and earned fees must exceed that gap for the pool to beat holding the two assets. For a V3 position, you can concentrate liquidity within a chosen price range. A narrower range may earn a larger share of fees while the price stays inside it, but the position stops earning trading fees when the price moves outside that range. For an occasional user, I would choose a range I am prepared to check and adjust, then judge results by fees earned *minus* network costs and the value of the tokens I could have held. ### BOO Farming Adds a Separate Reward Decision Farm only if an eligible liquidity position’s extra BOO rewards are worth the additional token and contract exposure. SpookySwap BOO farming can add an incentive to pool fees, but the advertised annual rate is an estimate: reward rates, the amount deposited by other farmers and BOO’s market price can change. Confirm that your specific pool and position qualify before supplying tokens solely for the incentive. Keep pool returns and BOO returns separate when comparing choices. A farm paying, say, $40 of BOO over a period does not repair a $90 shortfall against simply holding the two pool tokens. Claiming rewards or changing a position also takes transactions, so small deposits need enough expected return to cover those costs. If you already hold BOO, xBOO is a different route: it represents a claim on BOO deposited in a staking pool, rather than a two-token trading position. Check how much BOO one xBOO represents when entering and leaving; the ratio need not be one-to-one. It still leaves you exposed to BOO’s price, even though it avoids the changing token mix of a liquidity pair. For a straightforward trade, I would swap after checking the chain and output; for ongoing returns, I would supply liquidity only when the likely fees and any BOO reward justify holding both assets and monitoring the position. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://aboutcryptotalks.gitbook.io/aboutcrypto/spookyswap-choosing-between-swaps-pools-and-boo-farms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.