community-data's Introduction

Arrakis Community Data

Arrakis static data for all community vaults

Adding a new vault

Add an entry to the `vaults` field of the `vaultsList.json` file in the following format:

{
  "name": "Arrakis Vault V1 WMATIC/WETH",
  "address": "0xdc0eca1d69ab51c2b2171c870a1506499081da5b",
  "chainId": 137,
  "gauge": {
    "address": "0xEdF8C3aD1186d6ecB8b8cd08230b9434768252A5",
    "rewardToken": "0x0d500B1d8E8eF31E21C99d1Db9A6444d3ADf1270",
    "rewardLength": 608000
  }
}

Note: if there is no liquidity gauge, simply put "gauge": null

If required add new tokens to the `tokens` field of the `tokenlist.json` file in the following format:

{
  "chainId": 1,
  "address": "0x15b7c0c907e4C6b9AdaAaabC300C08991D6CEA05",
  "decimals": 18,
  "name": "Gelato Network Token",
  "symbol": "GEL",
  "logoURI": "https://raw.githubusercontent.com/ArrakisFinance/arrakis-tokenlist/main/images/0x15b7c0c907e4C6b9AdaAaabC300C08991D6CEA05-1.svg"
}

Note: Use checksum address everywhere!

Open PR and make sure all checks passed ✨

community-data's People

Contributors

Stargazers

community-data's Issues

proposal: repository name change

Proposal to change name of the repository

`ArrakisFinance/vaults-whitelist` ->> `ArrakisFinance/community-data`

I propose to change name of this repository to community-data. When this repository was created it only consisted of vault-whitelist. Later we discoverd that we needed one more static list, token list. In future we might need more static JSON which will include various smart contract data from the community.

Advantage of having one repository for all JSON data could be great.

All community members can create pull requests and get approved/rejected. All data is public.
Development advantages for building frontends for Arrakis.