> For the complete documentation index, see [llms.txt](https://destiny-world.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://destiny-world.gitbook.io/whitepaper/introduction.md).

# Introduction

Destiny World and Crytter, two entities at the forefront of blockchain innovation.

Destiny World, renowned for its contributions in GameFi, the Metaverse, and as an NFT builder, brings a unique blend of gaming, virtual reality, and digital asset creation to this partnership.

Meanwhile, Crytter, a leading social platform tailored for the crypto community, has established a significant presence in the metaverse.

This merger is not just a fusion of two platforms but a strategic alignment to create a comprehensive, all-in-one ecosystem in the crypto space.

It signifies a concerted effort to build a safe, scam-free environment for users, leveraging the strengths of both platforms to offer an unparalleled experience.

By combining Destiny World's gaming and NFT prowess with Crytter's social networking expertise and commitment to security, this partnership aims to redefine the landscape of crypto interaction, community building, and virtual experiences.


---

# 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://destiny-world.gitbook.io/whitepaper/introduction.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.
