# Page Not Found

The URL `dione-blockchain-evm-fork-specs/gHUXcid6ag1yQhK2sO3j` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Guide For Existing Projects/Tokens (on another EVM-blockchain)](https://dione-protocol.gitbook.io/technical-documentation/guide-for-projects-deploying-on-odyssey-chain/guide-for-existing-projects-tokens-on-another-evm-blockchain.md)
- [DiamondSwap](https://dione-protocol.gitbook.io/technical-documentation/testnet-guide/diamondswap.md)
- [Bridge](https://dione-protocol.gitbook.io/technical-documentation/dapps/bridge.md)
- [Guide For New Projects](https://dione-protocol.gitbook.io/technical-documentation/guide-for-projects-deploying-on-odyssey-chain/guide-for-new-projects.md)
- [Odyssey Chain Testnet](https://dione-protocol.gitbook.io/technical-documentation/networks/odyssey-chain-testnet.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://dione-protocol.gitbook.io/technical-documentation/guide-for-projects-deploying-on-odyssey-chain/guide-for-existing-projects-tokens-on-another-evm-blockchain.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://dione-protocol.gitbook.io/technical-documentation/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://dione-protocol.gitbook.io/technical-documentation/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., `/technical-documentation/guide-for-projects-deploying-on-odyssey-chain/guide-for-existing-projects-tokens-on-another-evm-blockchain.md`).

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