# Page Not Found

The URL `community-updates/pox-phase/l1x-multichain-balancer-pool/liquidity-bootstrap-phase` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [L1X Fungible Token Smart Contract](https://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/l1x-components-example-use-cases/l1x-fungible-token-smart-contract.md)
- [Ledger Tokenization](https://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/l1x-applications/ledger-tokenization.md)
- [Token Participant Distribution and Pricing](https://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/l1x-reward-mechanism/token-participant-distribution-and-pricing.md)
- [Validator LifeSPAN](https://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/validator-nodes/validator-lifespan.md)
- [Use Case: Advertise BSC NFT Sale in OpenSea Ethereum Marketplace](https://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/x-talk/use-case-advertise-bsc-nft-sale-in-opensea-ethereum-marketplace.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://l1x-sdk.gitbook.io/l1x-foundation/l1x-technology-explained/l1x-components-example-use-cases/l1x-fungible-token-smart-contract.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://l1x-sdk.gitbook.io/l1x-foundation/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://l1x-sdk.gitbook.io/l1x-foundation/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/l1x-foundation/l1x-technology-explained/l1x-components-example-use-cases/l1x-fungible-token-smart-contract.md`).

You may also use `Accept: text/markdown` header for content negotiation.