<username>{{ maskedUsername }}</username><space /><text>just voted for</text><space /><projectButton />

<username>{{ maskedUsername }}</username><space /><text>just voted for</text><space /><projectLogo /><space /><projectName>{{ projectName }}</projectName>

Bug Bounty rewards are grouped by severity and the impact of the vulnerability. Examples and descriptions of the type of vulnerabilities that correspond to each severity level can be found below. The payout amount has a 5 tier structure with separate scalesfor website/apps and smart contracts.

Description of vulnerability and your proof of concept or validation steps

Name

Please input a title

Short description of the vulnerability and the affected asset.

The core team is situated in country(ies) that received low aggregated ratings in terms of international judicial cooperation, criminal justice system, anti-money laundering, and corruption. This contextual data suggests an increased difficulty and complexity in preventing and mitigating fraud.

The core team is situated in country(ies) that received medium aggregated ratings in terms of international judicial cooperation, criminal justice system, anti-money laundering, and corruption. This contextual data suggests a medium level of geographic accountability, thus reducing and mitigating the risk of fraud.

The core team is situated in country(ies) that received the best aggregated ratings in terms of international judicial cooperation, criminal justice system, anti-money laundering, and corruption. This contextual data suggests the highest level of geographic accountability, thus maximizing the risk reduction and mitigation.

Vulnerability Title

All funds can be stolen via forged `op::transfer_notification` to `lp-minter`

`lp-minter` always rejects `op::transfer`

Argument order is incorrect in `save_data()`

`handle_provide_wallet_address()` returns incorrect address

`min_amount` storage field is shadowed and overwritten by incoming argument in `lp-minter::handle_transfer_notification()`

`lp-wallet` doesn't guarantee `pending_balance` consistency

Sending `op::init_pending_balance` to `lp-wallet` wipes the deposits

`jetton-minter::op::mint` allows to send invalid messages

`update_mining_index()` can ignore `next_mining_rate_cell`

Wrong `response_address` used for `op::burn` message in `lp-minter::handle_transfer()`

`msg_value` is not controlled at `lp-minter` on `op::claim`

`msg_value` is not controlled at `lp-minter` on `op::check_mintable_notification`

Pending jettons can be returned if `lp_minter` `is_stopped`

`lp-wallet`/`lp-minter` don't follow TEP-74 standard

`router::handle_change_lp_content()` is never executed

Wrong destination address used in case of rejected swap request

`router` doesn't validate the `sender_address` on `op::transfer_notification`

The swap payload from EOA is not properly validated in `router::handle_transfer_notification()`

Bounced `op::transfer` message from `governance_jetton_wallet_address` is ignored in `allocator::handle_claim()`

`end_parse()` Is Missing

Pull-Over-Push Pattern is not used in admin changing

Token data is not following TEP-64 standard

`msg_value` is not controlled at `jetton-minter` on `op::mint`

`parse_std_addr()` can be used to parse address

`msg_value` is not controlled at `router` on `op::create_pool`

`mined` and `current_index` calculation can be simplified

`lp-minter::handle_burn()` doesn't call `force_chain()`

`msg_value` is not controlled at `lp-minter` on `op::burn`

`lp-minter` sends `op::transfer` to `jettonA_wallet_address` in non-bounceable mode

Gas management in `lp-minter::handle_transfer()` is inconsistent

`to_jetton_address` is not checked in `lp-minter::handle_transfer_notification()`

`lp-minter` silently accepts incoming LP transfers

`op::claim` event emitted in `lp-minter::handle_change_lp_mining_rate()`

`min_amount` is not respected by `lp-minter::handle_mintable_notification()`

`lp-minter` accepts incoming transfers of unrecognized jettons

Wrong `fwd_count` calculation

`jetton_address` is not validated in `lp-wallet::check_mintable()`

`lp-wallet::on_bounce()` is redundant

`router` allows `op::pool_created` from `pool_creator_address`

`router::handle_change_lp_mining_rate()` gas consumption is inconsistent

`jettonA_address`/`jettonB_address` can be arbitrary, irrelevant to real jettons

`mined()` can be simplified

Constants can be used instead of `PUSHINT`

Misleading comments

Unused code

`update_mining_index()` can be refactored

Usage of Magic Numbers

`in_msg_body` is unused in `lp-minter::handle_claim()`

`op::change_router` can't be handled properly by `lp-minter`

Response messages `op` don't have high-order bit set

Argument names of `router::get_lp_address()` are misleading

`either_forward_payload` variable is unused

`calculate_jetton_wallet_address()` can be replaced with `calculate_contract_address()`

Long and complicated message building statements can be formatted

`calculate_jetton_minter_address()` is unused and dangerous

Megaton Finance - Audit 1

allocator.fc

lp-minter.fc

lp-wallet.fc

router.fc

constants.fc

discovery-params.fc

message_utils.fc

op-codes.fc

utils.fc

jetton-minter.fc

jetton-wallet.fc

CertiK KYC

Top 10% Watchlisted

Top 10% Fundamental Score

Megaton is a defi protocol that is built by Ozy which is a best in class blockchain development company that has built projects such as Orbit Bridge, Klayswap, Belt Finance and Meshswap

Megaton Finance

Leaderboards

Due Diligence Tools

Resources

Bug Bounty Program