> For the complete documentation index, see [llms.txt](https://baasid.gitbook.io/baasid-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://baasid.gitbook.io/baasid-docs/whitepaper/baasid-commercialization/expansion-through-layer-2-construction.md).

# Expansion through Layer 2 Construction

## Expansion through Layer 2 Construction

BaaSid's fundamental goal of expanding to Layer 2 is to maximize the utility of BAAS tokens. This is a strategy that goes beyond a simple technical transition to drive user engagement, expand the token economy, and ensure that tokens have real utility in a variety of on-chain activities. To achieve this, we are expanding in the following directions:

·         On-chain data verification: Beyond the existing off-chain-on-chain mixed structure, we design voting/research results to be verified on-chain in real time through a lightweight smart contract. This ensures transparency and integrity of the system, while BAAS tokens are used as a means of verification fee or participation reward during the verification process.

·         Building a DApp ecosystem: We open APIs, SDKs, and token wallet linkage interfaces so that internal or external partners in various commercialization businesses can develop and operate independent DApps. These applications utilize BAAS tokens to perform functions such as data collection, voting, participation rewards, and digital asset management, ultimately creating a structure that increases the demand for BAAS tokens.

·         DAO-based operation: Rather than a DAO-based decision-making participation structure, we adopt a structure designed around rewards for users’ actual activities (e.g., responding to surveys, participating in voting, data verification, etc.). This structure provides incentives to users, improves the reliability and quality of data, and activates the actual circulation of BAAS tokens.

·         Securing and monetizing data for AI learning: By providing structured voting data collected based on blockchain to LLM learning, users who actually contributed will be directly rewarded with BAAS tokens. This model can be monetized through partnerships with AI and data companies, and BAAS tokens will be actively used as a medium of exchange in such data transactions.

<div align="left"><figure><img src="https://3707430118-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWgrxW4I2ANZX2P4332gB%2Fuploads%2Fk9wkNiewNLzOs5HymCz2%2Fg.png?alt=media&amp;token=343a9814-ba51-4677-9efc-c6e3640d1aa4" alt="" width="16"><figcaption></figcaption></figure></div>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://baasid.gitbook.io/baasid-docs/whitepaper/baasid-commercialization/expansion-through-layer-2-construction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.
