> For the complete documentation index, see [llms.txt](https://ccc-ltd.gitbook.io/crypto-connect-consulting/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ccc-ltd.gitbook.io/crypto-connect-consulting/projects/arcas.md).

# Arcas

Arcas rapidly grew from a small private investment group to a super active Telegram and Discord server with over 18K members. At its peak, during the NFT launch a team of 20+ CMs and Moderators were managing huge influxes of members across numerous channels and distributing information in multiple languages in the lead up to mint. Moderators were on hand for up to 18 hours continuously and the Mint was hugely successful - selling out in 12 hours!\
\
The BAS Telegram had a refreshingly low number of ‘Moon boys’ and ‘degens’ - those having been systematically converted to educated, helpful, active and engaged users. Bans under the CM team were negligible.

Spawned from the successes of BAS / Arcas, CCC assisted in crafting announcements and keeping a timeline of all things relevant to the community. We proof-read announcements, articles and websites in order to assist the core team in catching errors and offering community-centric approaches that better relayed the desired message - whether it be missing information or revisions designmed to avoid confusion. We worked with our team to translate information in multiple languages, all traditionally beneficial for web3 communities. We built out the community mod team with leads in all languages as the community scaled. We offered solutions and set up systems and protocols to keep good lines of comms, both internally and externally, in order to optimise efficiency and meet the demanding standards of the community while keeping the workload minimal on the core team. 

\
We successfully ran multiple competitions from typical crypto ‘Buy Comps’ in the early days to themed seasonal events that ran for up to a month with dedicated channels (Discord) for submissions and focused engagement. The community often selected winners based on simple engagement. 

We established solid gamification of the Server though the goal of tokenising it was never realised - due largely to compliance. Integrated Quest based challenges through Zealy that served not only to drive exposure of the project via socials, but also self-education surrounding the project as well as healthy community competition and camaraderie.

We built a repository of educational resources both about the project but also the greater web3 and defi space allowing new users to quickly become familiar with the project while keeping them within our own ecosystem when searching out information. We supplied info surrounding the use of wallets, token imports, safety and security and even use of blockchain scanners to name a few. \
\
We recently built 2 additional Discord servers with security and communication integrations and have migrated from the old server for clearer separation of project wide information dissemination. A dedicated project server (*now deprecated*) delivers multiple channels of targeted information on the broad remit of the company, while a dedicated gaming server allows focused attention on the first Web3 gaming product.

Arcas has evolved dramatically in the last 2 years with changes in personnel from Founder level down and with a shift in product offering. It is keenly positioned for the coming years, and while (like many projects that have persisted during the Bear market) engagement has dropped off, the CCC team remain in place and are on hand at all times, poised for the inevitable upturn in chat volumes.<br>


---

# 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://ccc-ltd.gitbook.io/crypto-connect-consulting/projects/arcas.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.