<aside> ℹ️ This document outlines several key points that are useful for developers funded by Tokamak Network.

</aside>

<aside> ❗ Edit access: unit leaders have edit access to this document. If you want to edit, please request edit access)

</aside>

Common tools and resources

<aside> 📌 The following tables list tools and resources commonly used during project development.

</aside>

1. Core basic tools

|

2. General resources

| | HR | • You or projects can face numerous HR issues while working in a remote company. Please contact our HR team as soon as you can so that we can help you. | [email protected] | | Urgent development related requests | • If your project is a facing critical issues that requires quick actions, do not panic, you can quickly reach out to our CEO and Partners. • First thing to do is contact one of us, and we will help you navigate to resolve the issue. • If you feel that the issue requires high discretion, you can contact our CEO directly. | <Chief Ecosystem-building Officer/ Partner: Kevin> [email protected]

<Partner: Jaden> [email protected]

<Partner: Suah> [email protected]

<Partner: Zena> [email protected]

<Partner: Ale> [email protected]

<Partner: Jake> [email protected]

<Partner: Suhyeon> [email protected] |

3. Media resources

Steps

1. Ask colleagues for review (including at least one PM) and provide key check points
2. Request for review on the tokamak-x-medium-announcement slack channel
3. After review, tag Kevin for final approval
4. Kevin will publish

Basic checks before requesting review • X has 250 character limit. • Make sure to not embed any links to your text. (correct = https://bit.ly/3Z9EvjU; incorrect = video) • You can use url shortner such as bitly to shorten any url links. | tokamak-x-medium-announcement slack channel | | Medium blog | • Posting official announcements, research, editorial blogs on Tokamak Network Medium. Request writer access on the slack channel to get submission access to the blog.

Steps 1. Ask colleagues for review (including at least one PM) and provide key check points 2. Request for review on the tokamak-x-medium-announcement slack channel 3. After review, tag Kevin for final approval 4. Publish | tokamak-x-medium-announcement slack channel | | Brand Kit | • Here you can find logos, icons, and other media assets for Tokamak Network and related services. | [email protected] | | Design request | • if you have any design related tasks, you can utilize our tokamak-internal-design slack channel. • This is offered for Tokamak Network team members only. | [email protected] | | Onther Communication Manager | • Tokamak Network hired Onther to communicate to community. They operate the official Discord and Telegram channels for the Tokamak Network. • They provide moderation and you can even schedule a call with the community to discuss your project. • They also provide bi-weekly report where projects share their outputs in email newsletter. | onther-cm slack channel [email protected] |

4. Internal resources

5. Development tools

Please note that we can only register NS (name server) records. A or CNAME use is not possible. | [email protected] | | Google Analytics | • This is our default traffic analyzer. You can see the current list here. • If you want to see the traffic report, please contact. | [email protected] | | Subgraph | • Ethereum subgraph deployment can be done using our Alchemy account (rate limiting to 10 requests per seconds) • L2 subgraph → refer to doc. | <Ethereum Subgraph> [email protected]

<L2 Subgraph> [email protected] | | Docker | • We are using the tokamaknetwork organization. If you want to push images. You can contact one of manager. | [email protected] | | NPM | We are using the tokamak-network organization. If you want to install packages. You can contact us | [email protected] | | Python | • If you want to register your python package to Pypi.org, you should follow this instruction | [email protected] |

6. QA and Audit related resources

• However, if your service directly relates to our core product (L2 infra, etc), please contact our Immunefi manager to setup a program on Immunefi. | [email protected] | | Loss of fund or hacking report | • If you or your project received any requests related to loss of fund or hacking report, please ask them to contact via our telegram channel: https://t.me/tokamak_network • Do not engage with them about the issue, and just direct them to our telegram channel. This is to ensure that we are fully protected | [email protected] | | Support request form | • Currently, each project is receiving support request forms using google forms created by themselves. • Eventually, we will move to one single support request form for better efficiency, until then, contact us to help with creating the support request form | [email protected] |

Project owner responsibilities

<aside> 📌 Project owners are the main contact point to Tokamak Network Foundation.

</aside>

• Grant related tasks
  1. Prepare and apply for grant:
     • Determine goals and roadmap for the current quarter and next quarter
     • Onboard new team members
       • Add recruitment information
         • Determine onboarding process
           • example
         • Determine exit process
           • example
       • If you have a question about new applicant’s skillsets, ask unit leaders or other project owners
     • Make a budget
       • Determine appropriate grant amount
       • Discuss with your members on what they need (bounty program, software, hardware, etc)
  2. Determine how to divide the grant to members
     • Distribute grant (TON) to members
     • We recommend booking keeping to keep the record straight.
  3. Reporting to Tokamak Network
     • Present outputs in scheduled monthly and quarterly calls
       • Must request a fixed time for the call with Tokamak Network Foundation
     • Submit quarterly reports to Tokamak Network Foundation
       • Report format → check out how other projects have written their report
       • OR final report if it is a small grant
• Project management tasks

  1. Decide on a project code name

     • Each project requires a unique code name
       • example: OS X Lion, project Manhattan, etc
     • Code name does not have to be related to the project’s goal
     • Discuss with your teammates about creating a code name

  2. Create a project page under Dev (internal) notion

     1. Check out other project page for what to include here

        

     2. You need to have a public overview page → use publication feature (top right, “Share” button / “Publish” tab)

     

  3. Add information about your project in Tokamak Network Onboarding page

     

  4. Create a slack channel for your project

     1. Set channel name format: project-{project_code_name}

        1. example: project-opal

        

     2. Add new members to the project slack channel (Always invite Kevin to the channel)

  5. Schedule & Host weekly calls with your project members

  • Host a recurring weekly calendar event on “Tokamak Network call” calendar

    • calendar event name:
      • Project codename: weekly call*_names*
        • ex: Project Opal: weekly call_Ryan,Dylan,Suah

    

  • During the weekly call, each member is expected to share 1. What they worked on since the last meeting + 2. What they will work on until next meeting.

    • Make sure everyone filled out their output in weekly reporting sheet

  • Make sure the calls are recorded!