> For the complete documentation index, see [llms.txt](https://docs.flaunch.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flaunch.gg/updates/12-december-solana-imports-custom-token-supply-and-smarter-liquidity-sdk-upgrades.md).

# 12 December: Solana Imports, Custom Token Supply, and Smarter Liquidity SDK Upgrades

## What’s New

* **Cross-Chain Import: Solana Support**\
  Added Solana verifier integration for token imports. You can now verify Solana-based tokens via `Verifier.SOLANA` with support on Base mainnet and Sepolia.
* **Token ID Lookup for Memecoins**\
  Use `getFlaunchTokenIdForMemecoin()` to fetch the Flaunch NFT token ID and contract for any memecoin address.
* **Custom Token Supply for Imports**\
  All import and liquidity methods now support a `tokenSupply` param. Useful for tokens with non-standard decimals or fixed supply configs. Passed through to `getInitializeParams()` and used in tick and liquidity math.
* **Pool Event Parsing**\
  `getPoolCreatedFromTx()` extracts memecoin address, token ID, and config from a transaction hash by decoding the `PoolCreated` event.
* **Optional Slippage Control**\
  Added `slippagePercent` (default: 0.05%) across all liquidity types and methods. Customize the slippage buffer used during liquidity operations for finer execution control.

## Fixes & Improvements

* **ClankerWorld Support**:\
  Updated `ClankerWorldVerifierAddress` to support multiple token deployments.
* **Token Importer Contract Upgrade**:\
  New `TokenImporterAddress` deployed on Base mainnet with updated ABI and support for custom `_totalSupply` via a 5-parameter `initialize()` overload.


---

# 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.flaunch.gg/updates/12-december-solana-imports-custom-token-supply-and-smarter-liquidity-sdk-upgrades.md?ask=<question>&goal=<user_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.
