# gushyUSH

`gushyUSH` represents tokenized `vdUSH`. As an Omnichain Fungible Token, `gushyUSH` tokens can live on and be easily bridged to multiple chains.

At launch, the supported blockchain will be Arbitrum. The contract addresses for `gushyUSH` can be found [here](/gusherdao/references/contract-addresses.md).

## Creating gushyUSH (gUSHing your USH)

`gushyUSH` is minted when a user stakes/converts one of the 2 following tokens into `vdUSH` (1 `gushyUSH` = 1 `vdUSH`):

* `USH`
* Camelot LP Token (Camelot CLP: 50% USH, 50% ETH)
* `80USH-20unshETH` (Balancer BPT: 80% USH, 20% unshETH) \*\*
* SushiSwap LP Token (Sushi SLP: 50% USH, 50% WETH) \*\*

The calling of createLock() determines a user’s averageVdUshShare based on which token was locked and their lock duration. Each token’s multiplier is setup according to the relevant parameter in the vdUSH contract.

The following table shows multipliers at the time of this writing (please refer to the vdUSH contract or responsive front-ends for timely multipliers, as they can change via governance):

| Token                   | USH Multipier |
| ----------------------- | ------------- |
| `USH`                   | 1x            |
| Camelot LP Token        | 5x            |
| `80USH-20unshETH` \*\*  | 4x            |
| SushiSwap LP Token \*\* | 5x            |

The staked assets are locked up by the gUSHer protocol for the maximum time where they will allow the gUSHer system to benefit from compounding / maximum voting power, rewards, and growth.

*\*\* Feature available after future launch onto relevant network*


---

# 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://gusher.gitbook.io/gusherdao/tokens/gushyush.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.