# Introduction

{% hint style="info" %}
**Disclaimer:** CastleDAO aims to bring entertainment for Arbitrum players and anything here is not an investment / financial advice. 
{% endhint %}

## Overview

**What is Slayers of Moloch?** 

Slayers of Moloch (SoM) is a decentralized play-to-earn game that allows players to stake NFTs and earn RUBY tokens. Every warrior in SoM has their own unique abilities and strengths that can be used to defeat other players in battle. Players can earn RUBY tokens by staking NFTs, winning battles, and achieving certain milestones in the game. RUBY tokens can be used to purchase booster packs containing random Castledao warriors to add to your deck. The RUBY token is partially burned and partially sent to stakers, and RUBY stakers can earn additional rewards from game fees.

**What is Castle Protocol?**

Castle protocol is a set of smart contracts on the Arbitrum blockchain that dictate the emissions / rules of RUBY token, NFT staking, NFTs, items and more.

#### What is the CastleVerse?

The CastleVerse is the universe where the Lore of Slayers of Moloch takes place. To learn more about our Lore, go to [lore](https://castledao.gitbook.io/castles/overview/slayers-of-moloch-how-to-play/lore "mention"). 

**When did all of this get started?**

[CastlesArbiGenOne ](https://arbiscan.io/token/0x71f5c328241fc3e03a8c79edcd510037802d369c)(Castles) was the first NFT launched on Arbitrum, back in September 2021. Inspired by [Loot Project](https://www.lootproject.com/), Card Collecting Games (CCG) like Magic the Gathering and auto-battle systems like TFT. 

Since then, CastleDAO has been focused on building a game that integrated different collections from Arbitrum and Ethereum Mainnet into the game, and rewarded players with additional NFTs or $MAGIC tokens. \
\
The initial game, called also CastleDAO, has been an off-chain game that focused on free gameplay with on-chain rewards. \
\
On 2023 the focus moved to different goals, like the launch of the CastleDAO protocol and moving the game to be more on-chain. To know more, check our [roadmap](https://castledao.gitbook.io/castles/roadmap "mention") page.

## Quick links

{% content-ref url="overview/slayers-of-moloch-how-to-play" %}
[slayers-of-moloch-how-to-play](https://castledao.gitbook.io/castles/overview/slayers-of-moloch-how-to-play)
{% endcontent-ref %}

{% content-ref url="overview/partnerships-and-collaborations" %}
[partnerships-and-collaborations](https://castledao.gitbook.io/castles/overview/partnerships-and-collaborations)
{% endcontent-ref %}

## Tokenomics & Contracts

{% content-ref url="castle-protocol-v1/contracts" %}
[contracts](https://castledao.gitbook.io/castles/castle-protocol-v1/contracts)
{% endcontent-ref %}

{% content-ref url="castle-protocol-v1/tokenomics" %}
[tokenomics](https://castledao.gitbook.io/castles/castle-protocol-v1/tokenomics)
{% endcontent-ref %}

## Roadmap

{% content-ref url="roadmap/castle-protocol-phased-launch" %}
[castle-protocol-phased-launch](https://castledao.gitbook.io/castles/roadmap/castle-protocol-phased-launch)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://castledao.gitbook.io/castles/introduction.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.

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.