[WOOF!] Development Updates

Protocol Development
31

Updates for the week of Oct 21 - Oct 27, 2024

Developed Oct 21 - Oct 27:

  1. [market] Mantle USDe - post audit fixes.
  2. [collateral] pufETH WETH Mainnet - developed and ready to push. pufETH under the audit.
  3. [collateral] wUSDM USDT Optimism - developed and ready to push. wUSDM under the audit.
  4. [collateral] wUSDM USDC Optimism - developed and ready to push. wUSDM under the audit.
  5. 4626 wrappers for all the markets - scripts for deployment.

Development plan Oct 28 - Nov 03:

  1. Update Compound docs.
  2. Update DefiLlama docs.
  3. Update wUSDM and sFRAX 4626 price feed wrapper to push proposals on-chain.
  4. Rewards V2.

To push on-chain Oct 28 - Nov 03:

  1. [market] Mantle USDe market.
  2. [collateral] ETHx on WETH Mainnet.
  3. [collateral] sFRAX USDT Mainnet.
  4. [collateral] wUSDM USDT Mainnet.
  5. [collateral] wUSDM USDC Mainnet.
  6. [collateral] wUSDM USDT Arbitrum.
  7. [collateral] wUSDM USDC Arbiturm.
  8. [collateral] wUSDM USDT Optimism.
  9. [collateral] wUSDM USDC Optimism.

Backlog

  1. eBTC
  2. OETH.
  3. sUSDe.
  4. sUSDS.
  5. Discover DSR for USDS market.

Rewards V2. Additional steps to make the new feature better.

  1. Fix issues. Resolve all the issues detected in the audit report.
  2. Scenarios. Create integration tests that will simulate on-chain launching and contract interactions.
  3. Testnet migration. Create migration, that will deploy Rewards on testnet.
  4. Documentation. Create documentation.
  5. [optional] As the contracts are deployed on-chain, create on-chain tests
  6. [optional] Create DUNE to verify the backend gathers all the addresses (one more layer of security).
  7. Update the backend, to make it a script inside the Comet repository.
  8. Code review of all the above parts

Backend.

  • Currently, the backend is a separate repository with a heavy file structure and database, where the whole work of the backend can be implemented in one script file.
  • We suggest generating the proof inside the GitHub flows. It will provide transparency. The JSON file will be stored in the Comet repository as the proof is generated.

Rewards deployment and hash set up.

  • As hash is generated, it takes 7 days to set it into the rewards contracts using DAO. We suggest making the owner of the reward contract compound multisig to fast launch and finish the campaign.

Flow:

  • The script generates a hash using the GitHub flow.
  • OZ audits the correctness of the generated proof.
  • Multisig sets the hash into the Rewards contract.
2 Likes