# deployments

### **Berachain**

* Token contract: 0x231A6BD8eB88Cfa42776B7Ac575CeCAf82bf1E21
* Brown hole: 0x330eE904Ab479F36FbdcAd0Dc821D43fE443D433
* Treasury: 0x09BB5eE4C5f5d1d5d958271361a075548e293809
* Tax collector: 0x3cB33deA03257cF3c60Df01cc3638f4d01181366
* RFA treasury: 0xFD0EfB7c5f89633BA23bbC047007E1C6E8D1fa94
* Incentivized $PLUG/$BERA LP: 0xac1D44f0284634EB04FFA56C76d47e839224b46F
* Incentivized $PLUG/$BM LP: 0x3179096a10bE2E8981438AE841408D3D20C9e7d7
* Incentivized $PLUG/$RAMEN LP: 0xBd5b742F9764419d91CE1dCf6Ef12aDaDe74FC14

### **Ethereum**

* Token contract: 0x231A6BD8eB88Cfa42776B7Ac575CeCAf82bf1E21
* Brown hole: 0x330eE904Ab479F36FbdcAd0Dc821D43fE443D433
* Treasury: 0x09BB5eE4C5f5d1d5d958271361a075548e293809
* Tax collector: 0xDe737ab7b9DfcB6B1A3b4bab5365517e3cf15e75
* Brown hole cron: 0x6d42e5E04cD0145efD8e056363131bCd40ea36D2
* Incentivized $PLUG/$ETH LP: 0x27F92729a42050c1d60FFd07b92782537F9A4E6B

### **Base**

* Token contract: 0xDe737ab7b9DfcB6B1A3b4bab5365517e3cf15e75
* Treasury: 0x79D08e5Aa6b0E61F56A7FE2c6B8a8d3326589E6C
* Tax collector: 0x1ebcA2b3AD6D5f5dff62a67CE5DaAC36b8Ab45eC

### **Optimism**

* Treasury: 0x09BB5eE4C5f5d1d5d958271361a075548e293809

### **Arbitrum**

* Treasury: 0x79D08e5Aa6b0E61F56A7FE2c6B8a8d3326589E6C

### Bridging

Legacy $PLUG tokens can migrate freely between Ethereum and Base, or to Berachain, but never off of Berachain. Protocol owned liquidity is now being pulled from Ethereum and Base and moved to Berachain permanently. 

To ensure liquidity on Berachain post-migration, initial liquidity on Ethereum and Base is not renounced. Instead, it has been divided between the Beraplug treasury and a trusted community partner, ApiologyDAO. After successful migration, liquidity will be permanently locked.


---

# 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://docs.plug.sucks/deployments.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.