Due to time constraints, front-end support (UI to deploy network on target infra) will not be available until the testnet release. Instead, a Tree Diagram (SDK commands and inputs) will be provided as a substitute for user interaction and chain visualization during the testnet phase.

Updates on 1.10.25 (Video)

Kevin will deploy a lightweight Layer 2 (L2) chain to distribute grants to Tokamak Network team members. The chain should also enable him to deploy and test Dapps such as a zk-Dex. It must be cost-efficient, simple to deploy, and operable independently, with full documentation and support through the TRH interface.

1. Timeline

The timeline reflects Kevin’s desired schedule:

The testnet is tentatively planned to launch one month before the mainnet release, aiming for the end of February. The mainnet will follow after ensuring stable testnet operations. However, these dates are not yet finalized and may be adjusted based on progress and further discussions.

2. Priorities

1. Base Stack (Architecture)

   The foundation of the L2 chain must be designed with a minimal and simple architecture, ensuring flexibility and adaptability for diverse deployment environments. The architecture should natively include lightweight bridging functionality, enabling cross-chain operations seamlessly as a built-in feature. Additionally, the base stack must support deployment on both AWS and local environments, catering to diverse operational needs. (Kevin will provide further stack-related priorities as the project progresses.)

2. Add-ons

   One essential package is mandatory for the L2 chain:

   • Block Explorer: A critical add-on to provide comprehensive monitoring and visibility into chain activity. This tool will enable developers and stakeholders to track transaction data and chain performance effectively.

3. SDK & Packages

   Two essential SDK packages are necessary for the L2 chain:

   • Core SDK: This package should facilitate seamless interaction with the L2 chain for developers, including integration tools and APIs for dApps.

3. Additional Notes

• The chain will utilize TON as its native token, serving as the base currency for transactions and operations across the network.
• Front-end Support: Front-end development will not be prioritized until the testnet release. In the interim, a dialogue tree (SDK Documentation) will be implemented to substitute for user interaction and commands. Kevin will review and provide feedback before this solution is finalized and implemented.
• Ease of Use: All tools and documentation must be designed with simplicity in mind, enabling Kevin to deploy and operate the chain independently with minimal assistance.ㅊ
• Chain Shutdown Policy (Planned for Q2): Kevin intends to define a comprehensive policy for handling the chain shutdown process. While this is a lower priority for now, it will be addressed in Q2 to ensure clarity and readiness.