> For the complete documentation index, see [llms.txt](https://zeebit.gitbook.io/zeebit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zeebit.gitbook.io/zeebit.io/technical-overview/smart-contract-structures.md).

# Smart Contract Structures

The Zeebit protocol consists of a number of constituent smart contracts, each servicing a key function. Solana’s cross program invocations (CPI) enable these contracts to speak to one another in a secure way and request that they carry out their respective roles in a modular way.

The module approach enables a number of key benefits:

* Separation of functionality makes the programs easier to maintain and develop
* New games and features can be developed and easily integrated into existing contracts which handle core functionality like providing verifiable randomness, player settlement, updating statistics and distributing revenue share

***

## Smart Contract Types

* [Game Contracts](/zeebit.io/technical-overview/smart-contract-structures/game-contracts.md)
* [Randomness Contract](/zeebit.io/technical-overview/smart-contract-structures/randomness-contract.md)
* [Settlement, Profiles & Revenue Share Contract](/zeebit.io/technical-overview/smart-contract-structures/settlement-profiles-and-revenue-share-contract.md)


---

# 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://zeebit.gitbook.io/zeebit.io/technical-overview/smart-contract-structures.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.