A zkRollup based AMM DEX w/ limit orders, farming platform, and Bond platform - built on zkSync.
Platform: Code4rena
Start Date: 28/03/2023
End Date: 03/04/2023
Period: 6 days
Status: Completed
Pot Size: $23,500 USDC
Participants: 5
Reporter: liveactionllama
Judge: Picodes
Id: 227
League: ETH
HollaDieWaldfee | 1/5 | $0.00 | 11 | 4 | 0 | 7 | 1 | Grade A | 0 | 0 |
0xA5DF | 2/5 | $0.00 | 4 | 2 | 0 | 2 | 1 | Grade B | Grade A | 0 |
hansfriese | 3/5 | $0.00 | 5 | 1 | 0 | 4 | 0 | Grade B | 0 | 0 |
chaduke | 4/5 | $0.00 | 6 | 4 | 0 | 2 | 0 | Grade A | Grade A | 0 |
evan | 5/5 | $0.00 | 7 | 1 | 0 | 6 | 1 | Grade B | Grade B | 0 |
Auditor per page
This contest repo and the contest's Discord channel are accessible to participating certified wardens only. Participation in Classified audits is bound by:
All discussions regarding Classified contests and audits should be considered private and confidential, unless otherwise indicated.
Automated findings output for the contest can be found here within an hour of contest opening.
Note for C4 wardens: Anything included in the automated findings output is considered a publicly known issue and is ineligible for awards.
Mute is a native DeFi platform built on zkSync. The platform includes an AMM w/ stable and normal pools, bond platform, and amplifier platform.
The primary focus of this audit is to identify any areas of concern within the bond & amplifier contracts - specifically for loss of funds.
The Mute Docs has detailed information on the platform, how the systems are integrated, and specific calculations made inside certain contracts.
| Contract | SLOC | Purpose |
|---|---|---|
| contracts/amplifier/MuteAmplifier.sol | 305 | This contract drips Mute tokens as reward for depositing LP tokens over the course of startTime and endTime. The ratio of rewards is depends on a users weight and their dMute holding balance in relation to the overall contract rewards. The higher their dMute underlying holdings are, the more Mute tokens they receive. |
| contracts/bonds/MuteBond.sol | 146 | This contract allows users to bond their LP tokens in return for native Mute tokens. The contract continuously creates new bond epochs as long as it is funded with Mute tokens. Mute payout are received in dMute and timelocked for 7 days |
| contracts/dao/dMute.sol | 84 | This contract allows users to lock up their mute tokens to receive a soul-bound ERC20 dMute token. This is used as a governance token for Mute. Locking up mute for dMute requires a min 7 day vest with max 365 day period. Users can redeem their mute after the timelock is expired. |
| Contracts |
|---|
| contracts/interfaces/* |
| contracts/libraries/* |
| contracts/dynamic/* |
| contracts/test/* |
| contracts/bonds/BondTreasury.sol |
| contracts/dao/dSoulBound.sol |
- If you have a public code repo, please share it here: N/A - How many contracts are in scope?: 3 - Total SLoC for these contracts?: 535 - How many external imports are there?: 8 - How many separate interfaces and struct definitions are there for the contracts within scope?: 8 - Does most of your code generally use composition or inheritance?: Composition - How many external calls?: 0 - What is the overall line coverage percentage provided by your tests?: 75 - Is there a need to understand a separate part of the codebase / get context in order to audit this part of the protocol?: false - Please describe required context: n/a - Does it use an oracle?: no - Does the token conform to the ERC20 standard?: Yes - Are there any novel or unique curve logic or mathematical models?: Yes - Does it use a timelock function?: Yes - Is it an NFT?: No - Does it have an AMM?: Yes - Is it a fork of a popular project?: Yes - the AMM is; We use the Velodrome Stable Curve which is a fork of uniV2 with modifications. We have applied LP governance & a dynamic fee model. This is outside the scope of the contracts being audited. - Does it use rollups?: Yes (zkSync) - Is it multi-chain?: No - Does it use a side-chain?: Yes; EVM-compatible side-chain - Specific areas to be addressed: We want to find any exploits that result in loss of funds for our bond contract and amplifier contract. We are not concerned heavily with our AMM as it uses battle tested code, however is in the scope still as our bond / amplifier contracts utilize it.
Using Node v12.18.3 and npm 8.3.0
# Install project dependencies npm install # Compile using hardhat npx hardhat compile
Run unit tests
# Run Amplifier unit tests npm run test-amplifier # Run Bond unit tests npm run test-bond # Run dmute unit tests npm run test-dao