MagicSea - the native DEX on the IotaEVM
MagicSea - the native DEX on the IotaEVMFinished
MagicSea is the top Decentralized Exchange on IOTA & Shimmer EVM. Securely trade, stake & farm tokens to earn rewards on the most trusted DEX & NFT Marketplace. The audit is focusing on our MasterChef, Rewarder, our Magic LUM staking pool and Voting & Bribing System.
Details
Scope
Contest Results
On what chains are the smart contracts going to be deployed?
IotaEVM only
If you are integrating tokens, are you allowing only whitelisted tokens to work with the codebase or any complying with the standard? Are they assumed to have certain properties, e.g. be non-reentrant? Are there any types of weird tokens you want to integrate?
Any type of ERC20 token. Pools are permissionless. So users can open pools even with weird tokens. Issues regarding any weird token will be valid if they have Med/High impact.
Are there any limitations on values set by admins (or other roles) in the codebase, including restrictions on array lengths?
No
Are there any limitations on values set by admins (or other roles) in protocols you integrate with, including restrictions on array lengths?
No
For permissioned functions, please list all checks and requirements that will be made before calling the function.
Only owner modifier
Is the codebase expected to comply with any EIPs? Can there be/are there any deviations from the specification?
N/A
Are there any off-chain mechanisms or off-chain procedures for the protocol (keeper bots, arbitrage bots, etc.)?
We have an keeper for the Voting Epochs
Are there any hardcoded values that you intend to change before (some) deployments?
No
If the codebase is to be deployed on an L2, what should be the behavior of the protocol in case of sequencer issues (if applicable)? Should Sherlock assume that the Sequencer won't misbehave, including going offline?
Yes we are deploying on L2 IOTA - Yes please assume wont misbehave
Should potential issues, like broken assumptions about function behavior, be reported if they could pose risks in future integrations, even if they might not be an issue in the context of the scope? If yes, can you elaborate on properties/invariants that should hold?
No
Please discuss any design choices you made.
N/A
Please list any known issues and explicitly state the acceptable risks for each known issue.
N/A
We will report issues where the core protocol functionality is inaccessible for at least 7 days. Would you like to override this value?
N/A
Please provide links to previous audits (if any).
First audit of this code still in progress
Please list any relevant protocol resources.
Additional audit information.
Could you please focus on the Voting & Bribing System
Total Rewards
45,750 USDC
Contest Pool
Lead Senior Watson
Judging Pool
Lead Judge
28,250 USDC
14,500 USDC
1,300 USDC
1,700 USDC
Status
Scope
Start Time
End Time
Judging Rules
