> For the complete documentation index, see [llms.txt](https://docs.cindereth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cindereth.com/faq.md). # FAQ ## Is Cinder affiliated with Robinhood? No. Cinder is an independent tool built on the public, permissionless Robinhood Chain. Robinhood Markets is not involved, has not endorsed it, and is not responsible for it. ## Why does my token say "no market"? Because no trading pool for it exists on Uniswap v2, v3, or v4, which covers the liquidity on this chain. Most airdropped tokens never got a pool. "No liquidity" is different: a pool exists but was drained, so the token is worth effectively nothing. Either way, burning is the way to clear it. ## Why does it say "sell loses money"? The tokens have a price, but gas for the approval and swap costs more than the sale returns. Burning is one cheap transaction. Unsolicited airdrops are sometimes bait for malicious sites; burning is a plain transfer out of your wallet and safe. ## Why do I sign once per token? Wallets sign one transaction at a time. Cinder requests atomic batching (EIP-5792) on every run and uses one confirmation the day your wallet supports it on this chain. MetaMask does not yet. ## Is it really non-custodial? Yes. Cinder holds nothing, has no withdraw function, and deploys no contracts of its own. Burns go straight from your wallet to the dead address; swaps route through public Uniswap contracts back to you in the same transaction. ## What does it cost? Nothing from Cinder. You pay network gas, and sells pay the normal Uniswap pool fee, which goes to the pool's liquidity providers. ## Which wallets work? MetaMask fully; Rabby and other injected EVM wallets work; Phantom is limited because it does not carry Robinhood Chain yet. --- # 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://docs.cindereth.com/faq.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.