# Changelog

## <mark style="color:purple;">August 7, 2025</mark>

@clanker on Farcaster now deploys tokens with Clanker's Recommended configuration for fees and initial pool liquidity. UI deployments via clanker.world/deploy now also default to the Recommended configuration. Read more about the fee and pool setups in [Clanker.world Deployments](/documentation/general/token-deployments/clanker.world-deployments.md).

## <mark style="color:purple;">August 6, 2025</mark>

Clanker v4.0.0 is now live on Unichain. Deployments are supported through [SDK](/documentation/sdk/quick-start.md) and [Clanker.world Deployments](/documentation/general/token-deployments/clanker.world-deployments.md).

Contract addresses: [Deployed Contracts](/documentation/references/deployed-contracts.md#unichain-130).

## <mark style="color:purple;">July 14, 2025</mark>

### gArbitrum

Clanker v4.0.0 is now live on Arbitrum One. Deployments are supported through [SDK](/documentation/sdk/quick-start.md), [Farcaster Bot Deployments](/documentation/general/token-deployments/farcaster-bot-deployments.md), and [Clanker.world Deployments](/documentation/general/token-deployments/clanker.world-deployments.md).

Contract addresses: [Deployed Contracts](/documentation/references/deployed-contracts.md#arbitrum-one-42161).

## <mark style="color:purple;">July 8, 2025</mark>

### Auctions

Clanker v4.0.0 introduces MEV modules, opt-in contracts that affect the behavior of the early lifecycle of a Clanker token's pool. The first MEV module we are trying auctions off the first few swaps of freshly deployed pools, giving the auction proceeds to creators. This auction will only ever be deployed on Priority ordered L2s.

The auction MEV module will be enabled for tokens created through clanker.world, @clanker on Farcaster, API deployments, and SDK deployments. SDK users may opt out of using MEV modules.

How it works:

* When a new token is created, there's a brief "auction period" before normal trading opens to everyone. This auction is designed to capture value from MEV bots (sophisticated trading bots that try to profit from new token launches) and redirect some of the value back to the token's creator.
  * Normal trading starts after 5 rounds of the auction have completed (roughly 22 seconds post token deployment) or immediately after a round of the auction that has no bidders. The maximum delay before normal trading can start is at block *n+11*.
  * For additional detail, please refer to the [ClankerSniperAuctionV0](/documentation/references/core-contracts/v4/mev-modules/clankersniperauctionv0.md) documentation.

### Clanker.world

As you might have noticed, clanker.world has gotten a visual update over the past couple of weeks.

The token creation page at [clanker.world/deploy](https://www.clanker.world/deploy) will be updated to deploy v4.0.0 tokens on July 9.

### @clanker on Farcaster

@clanker on Farcaster will be updated to deploy v4.0.0 tokens on July 9.

### SDK

The Clanker SDK is available to deploying tokens on v4.0.0 contracts. Please see the [v4.0.0](/documentation/sdk/v4.0.0.md) SDK documentation for more detail.

### API

#### New Endpoints

* [Deploy Token (v4.0.0)](/documentation/authenticated/deploy-token-v4.0.0.md) - Deploy tokens on Clanker's v4.0.0 contracts starting on July 9.

#### Planned EOL&#x20;

* [Get Tokens by Creator](/documentation/public/get-tokens-by-creator.md) - EOL July 31, 2025. Migrate to [Get Paginated List of Tokens](/documentation/public/get-paginated-list-of-tokens.md).
* [Broken mention](broken://pages/wa4V8VXKnSgE4hKSq1bz) - EOL July 31, 2025. Migrate to [Deploy Token (v4.0.0)](/documentation/authenticated/deploy-token-v4.0.0.md).
* [Broken mention](broken://pages/4kyR1eUlG9QCANa4wyjv) - EOL July 31, 2025 Migrate to [Deploy Token (v4.0.0)](/documentation/authenticated/deploy-token-v4.0.0.md).

## <mark style="color:purple;">May 9, 2025</mark>

### gmonad

@clanker on Farcaster can now deploy tokens on Monad Testnet. Tag @clanker on Farcaster and include the phrase "gmonad" or "monad" to create your own Clanker on Monad Testnet.

> *gmonad @clanker, deploy BROOKLYNCRYPTO*

{% hint style="danger" %}
Only casts containing `gmonad` or `monad` will deploy tokens on Monad Testnet. All other requests to @clanker will deploy tokens on Base Mainnet.
{% endhint %}

## <mark style="color:purple;">April 21, 2025</mark>

### Configurable Starting Market Caps

Deployments are now more flexible with configurable starting market caps for WETH-paired tokens.

#### API Deployments

API users using the [Broken mention](broken://pages/wa4V8VXKnSgE4hKSq1bz) endpoint may optionally pass in the `initialMarketCap` parameter when creating WETH-paired tokens. This defaults to 10, which creates a \~10 ETH starting market cap token. The minimum value accepted is 1, which creates a \~1 ETH starting market cap token. There is no maximum value / limit on this parameter.

#### clanker.world

Users deploying tokens via [clanker.world](https://www.clanker.world/deploy) can now choose between 1, 5, and 10 ETH for their the starting market cap of their token.

### <mark style="color:purple;">April 17, 2025</mark>

### Indexing All Clanker Tokens

Today, clanker.world and the Clanker API will surface and return info for *almost* all tokens deployed through the Clanker contracts ([Deployed Contracts](/documentation/references/deployed-contracts.md)). This means that tokens deployed directly to the Clanker contracts with a variety of starting market caps and quote tokens will be included.

To help users interpret this data, we're surfacing additional info on clanker.world and adding net new response fields to the API endpoints.

Currently, clanker.world and API endpoints will return all tokens deployed on Clanker contracts EXCEPT those with `warnings` flags (see [#frontend-updates-clanker.world](#frontend-updates-clanker.world "mention") for more info). Tokens with `warnings` flags are rare at the moment, but developers using the API should implement their own filtering logic depending on what they would like to surface to their users.

{% hint style="warning" %}
These guardrails on clanker.world and API are set to be removed on **Friday, April 25**, at which point all tokens deployed on Clanker contracts will be available through clanker.world and the API - regardless of the launch setup of the token. Tokens pages on clanker.world will display a banner with the relevant `warnings` flag, while the API will return the flag in the response.
{% endhint %}

### Frontend updates (clanker.world)

Token pages will now show the starting market cap, referenced in the quote token that new token was deployed against. For now, all WETH-paired tokens with a starting mcap of at least 1 ETH will be shown, in addition to tokens paired against the [Supported Quote Tokens](/documentation/references/supported-quote-tokens.md) at the ticks specified in the table.

Soon, (once the aforementioned guardrails are removed), clanker.world will show all tokens, irrespective of the quote token or starting market cap. Token pages will then surface warning tags for tokens deployed with atypical pool configurations. See below for a list of the current tags:

* Unusual Tick
  * WETH-denominated tokens with a starting market cap of < 1 ETH (WETH)
  * Non-WETH tokens listed in [Supported Quote Tokens](/documentation/references/supported-quote-tokens.md) with pools that do not match the initial tick listed in that table
* Unusual Pair Address
  * Tokens paired with a quote token not listed in [Supported Quote Tokens](/documentation/references/supported-quote-tokens.md)
* Missing Pool Config
  * Tokens with incomplete or missing pool configuration info. These are primary legacy tokens that were deployed with a standard configuration

### API updates

{% hint style="warning" %}
API endpoints will return all tokens deployed on Clanker contracts **EXCEPT** those with `warnings` flags. The exception is to provide API users with a period of time to implement their own filtering logic based on the `warnings` and `pool_config` data. These guardrails are set to be removed on **Friday, April 25**, at which point all tokens deployed on Clanker contracts will be available through the API - regardless of the launch setup of the token.

Please thoroughly review the new response fields below (most importantly the `warnings`, `pool_config`, and `starting_market_cap` fields)
{% endhint %}

New response fields will be added for the following endpoints: `/tokens`, `/tokens/search`, `/tokens/fetch-deployed-by-address`, and `/get-clanker-by-address`&#x20;

**New response fields:**

* warnings: Any warning flags associated with the token
  * `UNUSUAL_TICK`
    * WETH-denominated tokens with a starting market cap of < 1 ETH (WETH)
    * Non-WETH tokens listed in [Supported Quote Tokens](/documentation/references/supported-quote-tokens.md) with pools that do not match the initial tick listed in that table
  * `UNUSUAL_PAIR_ADDRESS`
    * Tokens paired with a quote token not listed in [Supported Quote Tokens](/documentation/references/supported-quote-tokens.md)
  * `MISSING_POOL_CONFIG`
    * Tokens with incomplete or missing pool configuration info. These are primary legacy tokens that were deployed with a standard configuration
* pool\_config: Configuration for the token's liquidity pool
* starting\_market\_cap: Initial market capitalization, denominated in the quote token
  * The quote token is returned as `pairedToken` within `pool_config`
* chain\_id: Parsed as integer from database value
* metadata: Token metadata from database
* deploy\_config: JSON stringified deployment configuration
* social\_context: JSON stringified social context (when creator info is available)
* deployed\_at: Deployment timestamp
* msg\_sender: Address that sent the transaction to deploy the token
* factory\_address: Address of the factory contract
* locker\_address: Address of the locker contract

## <mark style="color:purple;">March 18, 2025</mark>

### New v0.3.1 Contracts

#### ***Permissionless deployments***

Anyone can interact with the v0.3.1 Clanker factory contract to create clankers. Creators may deploy directly from the contract, while new interfaces can be built on top of the contracts permissionlessly.

#### ***Social context & mutable metadata***

Creators and interfaces may pass in social context (e.g. references to Farcaster casts or X posts) during their deployments, which is immutable and can serve as a link to the origin of the deployment.

Metadata such as references to the websites or social media profiles for tokens may be added as well. The metadata for tokens is mutable and can be updated by the token's admin (typically the creator).

#### ***Creator vaults***

Creators may optionally allocate up to 30% of the token supply to the creator vault at time of deployment. Creators can set the unlock time on the vault, but there is a hard minimum of 30 days. After such time has passed, creators can claim the vaulted tokens from the vault.

Deployments with creator vaults are supported through the Clanker API.

#### ***Creator buys***

Creators may optionally send ETH during the token deployment transaction to purchase the token they are creating. This occurs after the the optional creator vault allocation is sent to the vault.

Deployments with creator buys are not yet supported through the Clanker API.

### Deprecations

This upgrade marks the change from v0.3.0 to v0.3.1 contracts. Please refer to [Deployed Contracts](/documentation/references/deployed-contracts.md) for the list of contracts. At this transition period, deployments through the v0.3.0 token factory will be deprecated. Presales will be deprecated and are not supported in v0.3.1.

The following endpoints will be deprecated:

* [Broken mention](broken://pages/4kyR1eUlG9QCANa4wyjv)
  * If you are currently using this endpoint, please contact our team for alternative deployment solutions using the [Broken mention](broken://pages/wa4V8VXKnSgE4hKSq1bz) endpoint.&#x20;
* [Broken mention](broken://pages/RWNeXVzN5ZL3QmXmVXoB)
* [Broken mention](broken://pages/72B405vnZLtb885LM7Cl)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://clanker.gitbook.io/documentation/changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.