> For the complete documentation index, see [llms.txt](https://thxnet.gitbook.io/white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thxnet.gitbook.io/white-paper/layered-dao/leafchain-box.md).

# Leafchain Box

### Leafchain Box Structure

A Leafchain Box serves as a specialized container within the Rootchain ecosystem, comprising multi-signature accounts and a dedicated smart contract. This structure facilitates a comprehensive multi-stage voting process that determines the configuration parameters for new Leafchain deployments.

### Deployment Process

The Leafchain deployment procedure follows a structured governance workflow:

1. **Initialization Phase**: \
   Founders create a Leafchain Box containing a formal proposal that defines essential Leafchain parameters:
   * Network name
   * Native token symbol
   * Native token name
   * Native token total issuance
   * Native token pre-allocation distribution
   * Master wallet address designation
2. **Resource Commitment**: \
   Founding members transfer the required THX tokens as an initiation fee into the Leafchain Box. These tokens are subsequently locked upon successful Leafchain deployment.
3. **Continuation Determination**: \
   Founders conduct a formal vote to determine whether to proceed with or terminate the initialization process. In the event of process termination, all THX tokens within the Leafchain Box are returned to their original contributors.
4. **Technical Configuration**: \
   An off-chain worker compiles and generates the chain specification (chain-spec) document for the new Leafchain.
5. **Specification Approval**: \
   Founders conduct a formal vote to either accept the generated chain specification or terminate the process. If terminated at this stage, all THX tokens within the Leafchain Box are returned to their original contributors.
6. **Implementation Execution**: \
   An off-chain worker deploys the Leafchain based on the approved specification, or alternatively, founders may manually deploy the Leafchain using the generated chain specification.
7. **Deployment Verification**: \
   Founders conduct a final verification vote to confirm successful deployment and operation of the new Leafchain. Upon positive confirmation, the THX tokens within the Leafchain Box are permanently locked. If verification is not confirmed within the designated timeframe, all THX tokens are returned to their original contributors and the process is terminated.

This governance-driven deployment framework ensures that new Leafchains are established through transparent consensus mechanisms while maintaining appropriate resource commitments from founding entities.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://thxnet.gitbook.io/white-paper/layered-dao/leafchain-box.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.