> For the complete documentation index, see [llms.txt](https://docs.bukprotocol.io/buk-protocol-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bukprotocol.io/buk-protocol-v2/buk-protocol-smart-contracts.md).

# BUK Protocol Smart Contracts

This section describes various template smart contracts within the BUK Protocol, their functions and their utilities. 

The contracts described here are factory contracts, which are used by asset owners (game developers, event organizers, hotel or airline operators etc.) for their own dAsset tokenization, minting, trading and proliferation on-chain. They cover the on-chain lifecycle of assets creating and unlocking value latent in these dynamic assets. There are multiple smart contracts available:

1. Tokenization
2. dNFT Contracts
3. Treasury Contracts
4. Marketplace Contracts
5. Interfaces

Any new dynamic asset shall deploy all or few of these smart contracts. For example, if a event organizer wants their tickets only to be minted as NFTs, but does not permit trading then they will only require Tokenization, NFT and Treasury contracts; if the event organizer wants ticket traded only within their dApp they will also deploy the marketplace contract.


---

# 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://docs.bukprotocol.io/buk-protocol-v2/buk-protocol-smart-contracts.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.