# Page Not Found

The URL `files/d8XvHzS1UtRSXU8qMLf9` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [7.4 Smart Contracts and Automation:](https://ibox-bsc.gitbook.io/whitepaper/7-market-advantages-of-ibox/7.4-smart-contracts-and-automation.md)
- [3.3 Community Development](https://ibox-bsc.gitbook.io/whitepaper/3-ecosystems-and-partnerships/3.3-community-development.md)
- [2.3 Consensus Algorithm:](https://ibox-bsc.gitbook.io/whitepaper/2-technical-overview-of-ibox/2.3-consensus-algorithm.md)
- [7.8 Continuous Innovation:](https://ibox-bsc.gitbook.io/whitepaper/7-market-advantages-of-ibox/7.8-continuous-innovation.md)
- [3.2 Partnerships](https://ibox-bsc.gitbook.io/whitepaper/3-ecosystems-and-partnerships/3.2-partnerships.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://ibox-bsc.gitbook.io/whitepaper/7-market-advantages-of-ibox/7.4-smart-contracts-and-automation.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://ibox-bsc.gitbook.io/whitepaper/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://ibox-bsc.gitbook.io/whitepaper/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., `/whitepaper/7-market-advantages-of-ibox/7.4-smart-contracts-and-automation.md`).

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