use newest contracts

.editorconfig

@@ -0,0 +1,10 @@
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+
+[*.{js,json,yml}]
+charset = utf-8
+indent_style = space
+indent_size = 2

.env.dist

@@ -0,0 +1,5 @@
+SUPABASE_KEY=
+SUPABASE_PLUGIN_REWARDS_TABLE_NAME=plugin-rewards-development
+SUPABASE_PLUGIN_TABLE_NAME=apy-plugin-development
+SUPABASE_VAULT_APY_TABLE_NAME=vault-apy-development
+SUPABASE_ASSET_PRICE_TABLE_NAME=asset-price-development

.eslintrc.json

@@ -0,0 +1,21 @@
+{
+  "rules": {
+    "import/no-unresolved": [
+      "error",
+      {
+        "ignore": ["aws-lambda"]
+      }
+    ],
+    "import/order": [
+      "error",
+      {
+        "alphabetize": { "order": "asc", "caseInsensitive": true },
+        "newlines-between": "always"
+      }
+    ],
+    "@typescript-eslint/ban-ts-comment": "off",
+    "@typescript-eslint/no-explicit-any": "error",
+    "@typescript-eslint/no-unused-vars": "error",
+    "no-console": ["error", { "allow": ["warn", "error"] }]
+  }
+}

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,38 @@
+---
+name: Bug Report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<ins>**Describe the bug**</ins>
+A clear and concise description of what the bug is.
+
+<ins>**To Reproduce**</ins>
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+<ins>**Expected behavior**</ins>
+A clear and concise description of what you expected to happen.
+
+<ins>**Screenshots**</ins>
+If applicable, add screenshots to help explain your problem.
+
+<ins>**Desktop (please complete the following information):**</ins>
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+<ins>**Smartphone (please complete the following information):**</ins>
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+<ins>**Additional context**</ins>
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/custom-asset-support.md

@@ -0,0 +1,54 @@
+---
+name: Custom Asset Support
+about: Add support for specific asset in a specific chain
+title: Support Asset $XXX
+labels: ''
+assignees: ''
+
+---
+
+<h3> Custom Asset Information: </h3> <br>
+
+*Use the reference below for Asset Information.  If not found in the table, please notify Nik via Discord* <br>
+[Link to Notion Custom Asset Table](https://www.notion.so/4627d911ce3c4589aef9f7592650e7b2?v=4b3abb4ebfd44018bcf47496d512b778) <br>
+
+**Symbol**: *<ins> ETH </ins>* <br>
+**Block Explorer URL**:  *https://etherscan.io/address/0x0000000000000000000000000000000000000000* <br>
+**Chain**: *<ins> Ethereum </ins>*
+
+*Please mark the tasks below, as appropriate.  Then link supporting Github items together in the Comments section either using # or the button in the screenshot below:* <br>
+   ![Screenshot of Github Link Button](https://user-images.githubusercontent.com/103433798/169572470-b7e31053-afab-4225-9816-6403193b86b3.png) <br>
+
+ **<ins>Link To Matching Chain Deployment Ticket</ins>:** #*Insert Link Here* <br>
+
+- [ ] **ChainLink / DIA / Flux Supported** _*OR*_
+- [ ] **Requires Custom Oracle** <br>
+&nbsp;&nbsp;&nbsp;- [Link to Custom Oracle Template](https://github.com/Midas-Protocol/contracts/issues/new?assignees=&labels=&template=custom-oracle.md&title=Custom+Oracle+for+%24XXX)
+- [ ] **Requires Custom Liquidator** <br>
+&nbsp;&nbsp;&nbsp;- [Link to Custom Liquidator Template](https://github.com/Midas-Protocol/contracts/issues/new?assignees=&labels=&template=custom-liquidation-strategy.md&title=Custom+Liquidation+Strategy+for+%24XXX)
+- [ ] **ERC-4626 Support** <br>
+&nbsp;&nbsp;&nbsp;&nbsp;- [Link to ERC-4626 Template](https://github.com/Midas-Protocol/contracts/issues/new?assignees=&labels=&template=erc-4626-strategy.md&title=ERC-4626+Strategy+for+%24XXX)
+
+<h3> Tasks: </h3>
+
+- [ ] Edit the supported assets:  https://github.com/Midas-Protocol/monorepo/tree/development/packages/sdk/src/chainConfig/assets and add the asset to the respective chain
+
+- [ ] Edit deployment script to set up and deploy oracle and liquidator
+
+*IF it is a uniswap-twap oracle supported asset*
+- [ ] For Uniswap-supported assets, redeploy the fuse-twap-bot after adding editing the `supported_pairs` variable in the [ops directory](https://github.com/Midas-Protocol/monorepo/blob/development/ops/main.tf#L28)
+
+*IF requires custom liquidation strategy*
+- [ ] Edit the redemption strategies: https://github.com/Midas-Protocol/monorepo/blob/development/packages/sdk/src/chainConfig/redemptionStrategies.ts
+- [ ] Edit the redemption strategy data encoding: https://github.com/Midas-Protocol/monorepo/blob/development/packages/sdk/src/modules/liquidation/redemptionStrategy.ts#L23
+- [ ] Edit the `chainDeploy/<chain>.ts` deploy script to deploy the liquidation strategy, if not already there
+
+*IF it needs/could use a plugin and/or flywheel*
+- [ ] Edit the `chainDeploy/<chain>.ts` deploy script to deploy the plugin & their flywheel(s)
+
+### Deployment
+
+After all the items above are complete, proceed with the deployment of the contracts and changes to the deployment script. 
+
+If a plugin and/or Flywheel were deployed with this, then, you also need to:
+- [ ] Edit the plugin config: https://github.com/Midas-Protocol/monorepo/blob/development/packages/sdk/src/chainConfig/plugin.ts so that the information about it is made available to the SDK users/FE

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: Feature Request
+about: For any new feature requests (resolves an issue, UX improvement or addition)
+  etc)
+title: 'FEATURE: '
+labels: ":sparkles: [Feature]"
+assignees: ''
+
+---
+
+<ins>**Please describe the reasoning for this feature?**</ins> _Please mark one of the the checkboxes below, then put the description below that, screenshots preferred._ <br>
+- [ ] _Is this to resolve a process problem, bug. defect, error or glitch?_ <br>
+- [ ] _Is this for a new feature or improvement?_ <br>
+***
+
+<ins>**Describe the solution or new feature you'd like.**</ins>  _How can we improve our product?  What will bring more users to our protocol?_ <br>
+
+
+<ins>**Describe alternatives that would satisfy requirements.**</ins> _What's an alternative that could satisfy the same requirements I was looking for?  Will it be harder?  Will it require more resources?._ <br>
+
+<ins>**Additional context.**</ins> <br> _Any information that's relevant that doesn't fit in the categories above?_ <br>

.github/ISSUE_TEMPLATE/user-submitted-bug.md

@@ -0,0 +1,43 @@
+---
+name: User Submitted Bug
+about: Please use this form to submit your issue
+title: "[USER SUBMITTED BUG] Title of Issue"
+labels: "[USER SUBMITTED BUG]"
+assignees: ''
+
+---
+
+**Describe The Outcome:** (A clear and concise description of what the incorrect behavior is)
+
+
+**Expected behavior:** (A clear and concise description of what you expected to happen)
+
+
+**Steps To Reproduce:** (Steps to reproduce the behavior)
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Screenshots:** (Add screenshots to help explain your problem)
+
+**Transaction Info:**
+- Wallet Address:
+- Chain: 
+- Pool Id: 
+- Transaction Hash: 
+- Error logs (screenshot): 
+
+**Browser/App/Platform Info**
+- Wallet (ex. MetaMask, Trust Wallet, etc): 
+- Was this on a desktop browser? If so:
+  - Browser:
+  - Operating System:
+- Was this on a mobile device?  If so:
+  - Operating system:
+
+**Contact Info:**
+- Discord Handle:
+
+**Additional Context:**
+Add any other context about the problem here.

.github/issue_template.md

@@ -0,0 +1,18 @@
+## Background
+
+Any information that gives more context as to why this task exists, and why it matters. This might include: links to discussions, documentation, or other Jira issues / tasks
+
+### Linked Issues & Documentation
+
+- List of linked issues, external links, etc
+
+## Definition Of Done
+
+Describes in 1-2 sentences what the output of the Task is, so that it can be verified by another team member easily. “Feature X is implemented as described and can be verified by using it”
+
+## Tasks
+
+- [ ] Task 1
+- [ ] Task 2
+- [ ] Task 3
+

.github/pull_request_template.md

@@ -0,0 +1,29 @@
+## Description
+
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Type of change
+
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+
+- [ ] Docs change / dependency upgrade
+- [ ] Configuration / tooling changes
+- [ ] Refactoring
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+- [ ] Requires changes in customer code
+
+## High-level change(s) description - from the user's perspective
+
+<!--- Describe your changes in more detail -->
+
+## Related Issue(s)
+
+Fixes <!--- Please link to the issue here: -->
+
+## Related pull request(s)
+
+<!--- Please link to the PRs here: -->
+
+<!--- adapted from https://github.com/inversify/inversify-basic-example/blob/master/PULL_REQUEST_TEMPLATE.md -->