> For the complete documentation index, see [llms.txt](https://wiki.shellprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.shellprotocol.io/getting-started/integrations/shell-native-primitives/volatile-token-amms.md).

# Volatile Token AMMs

## Overview

Despite their popularity, many tokens like ETH and BTC can fluctuate wildly in value. Since they are so unpredictable, these 'volatile' tokens make it a bit trickier to design an AMM perfectly tuned to their ups and downs. Nevertheless, it is possible to create a better AMM than the simplistic constant product AMM by using historical price data and fitting that information to a curve with concentrated liquidity.

Shell's initial volatile-to-stable pools are designed so that when the pool's liquidity is split 50-50 across both tokens, the swap rate uses the median dollar value of the volatile token over the last year.

Interested to read more about how these pools were designed? [Learn how to construct an AMM using Proteus.](https://docs.shellprotocol.io/tutorials/build-an-amm-with-proteus)

## Primitives

## `ETH+USD`

* `Pool Address:` [`0xa2dB39e781A5Eee0EAA625dace6F097c17dfF7Ea`](https://arbiscan.io/address/0xa2dB39e781A5Eee0EAA625dace6F097c17dfF7Ea)
* `LP Token ID: 0x3d39f7c71b4be4b2b39924b0aefbe172194c1a8b11ff4e31a74896edead80b02`
* `Component assets:` 
  * `ETH`
  * `DAI`
  * `USDC`
  * `USDT`
* `Fee: 0.25%`

## `WBTC+USD`

* `Pool Address:` [`0x3402D87DF0817b2A96b210b8873d33dD979C8D19`](https://arbiscan.io/address/0x3402D87DF0817b2A96b210b8873d33dD979C8D19)
* `LP Token ID: 0x0e53d22e36f0a0403bacf365d574a97253953118fb462cb766f6a1a34791d493`
* `Component assets:` 
  * `WBTC`
  * `DAI`
  * `USDC`
  * `USDT`
* `Fee: 0.25%`

## `ARB+ETH`

* `Pool Address:` [`0xA16F40437213020A167c230E4667ff8f13640f75`](https://arbiscan.io/address/0xA16F40437213020A167c230E4667ff8f13640f75)
* `LP token ID: 0x977a1e4c16998d4b94d59494909c9503f5bc50642326bc8fa61f2e22761e7a3a`
* `Component assets:` 
  * `ARB`
  * `ETH`
* `Fee: 0.25%`

## `MAGIC+ETH`

* `Pool Address:`[`0x0699645f2fd448398272ae07f82eee8d0388de1c`](https://arbiscan.io/address/0x0699645f2fd448398272ae07f82eee8d0388de1c)
* `LP token: 0xf00fbe5928cf77453911087439475eba4c4ddedd3f3664589eaa91c00e803377`
* `Component assets:` 
  * `MAGIC`
  * `ETH`
* `Fee: 0.25%`

## `REUNI+ETH`

* `Pool Address:`[`0x3917c74FDeC42071E29461c849bceB81cBC3059c`](https://arbiscan.io/address/0x3917c74FDeC42071E29461c849bceB81cBC3059c) 
* `LP token: 0x107a8aad95f88121f288baa229d82a6979de4158e6e0762a53e9ab24b4881c25`
* `Component assets:` 
  * `REUNI`
  * `ETH`
* `Fee: 0.25%`

## `STG+ETH`

* `Pool Address:`[`0xe043EB17Cc12C3fD4f5EaC765D0f1b965975F470`](https://arbiscan.io/address/0xe043EB17Cc12C3fD4f5EaC765D0f1b965975F470)
* `LP token: 0x395b21a145e98bc33138d4bc87a25e7ca0839b05bd16c1ed06476c5ceb5c0bfe`
* `Component assets:` 
  * `STG`
  * `ETH`
* `Fee: 0.25%`


---

# 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 dynamically by asking a question.

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

```
GET https://wiki.shellprotocol.io/getting-started/integrations/shell-native-primitives/volatile-token-amms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.