<aside> đź’ˇ Request contract code review and anyone can review via Github Issues features. This is a one member project, but everyone is welcomed to contribute to contract review.

</aside>

Project FBI Overview

Code Review Requests

<aside> âť— Please do not modify this table. This table can be modified only by project owner (Harvey).

</aside>

Project Repository Request info Review result Review completion deadline Reward
TMS multisender_shivansh
link MultiSender result (24.05.31~24.06.05) June 5th, 2024 X
TMS multisend_bayram link MultiSender result (24.05.31~24.06.05) June 5th, 2024 X
BEE crossTrade link CrossTrade Result (24.06.21~24.06.27) Jun 27, 2024 X
ECO ton-staking-v2 link TONStakingV2 Result (24.06.27~24.07.17) July 17, 2024 X
BEE L2-Assets-Migration link L2-Assets-Migration result (24.07.19~24.07.26) July 26, 2024 300 TON
TOP tokamak-thanos link Native Token (Thanos Bridge) Result (24.08.23~24.08.29) Aug 29, 2024 0 TON
Opal gem-nft-contract link NA yet Oct 08, 2024 2000 TON
ECO ton-staking-v2 link Oct 08, 2024 300 TON

1. Contract review request

<aside> ℹ️ Anyone working on the Tokamak Network project can request a code review.

Please be aware that the requester is responsible for making any necessary changes to the code based on the review and answering any questions that may arise from it.

</aside>

  1. The requester creates a notion document (must be accessible by public).

    Contract review request form (copy this to your project Notion page)

  2. Submit the request via Google Form (https://forms.gle/znwDS2Bmx5u3mAZ36)

  3. Contract review will start (Harvey will share the request with everyone)

  4. Requester has to either make a new commit based on the review or explain the issue with the review (ex: duplicated issue, not an issue, etc)

  5. The issue can be closed only by the person who submitted the review

2. Contract review process

<aside> ℹ️ Anyone can participate in code reviews and audits. It is reviewer’s responsibility to make sure that the code is fixed correctly, and only then the reviewer can close the issue.

</aside>

Submit review using “Issue” on Github

  1. Press “New Issue” under Issues tab.

    Untitled

  2. Set Issue title as “issue description”

    1. ex: Reentrancy vulnerability
  3. Copy paste the following markdown code to the description box.

    **Describe the bug**
    A clear and concise description of what the bug is.
    
    **Configuration**
    - Severity:
    
    **Impact**
    A clear and concise description of what you expected to happen.
    
    **Recommendation**
    If applicable, add screenshots to help explain your Recommendation.
    
    **Exploit Scenario**
    
    **Demo**