# MVTX Contract Description

This contract inherits and extends [**OpenZeppelin**](https://openzeppelin.com/) ERC721 token. We implement an updatable BaseURI in order to (eventually) migrate URI. The token implements also function useful for Ownership management and when the sale will be closed we will call the renounceOwnership() function in order to seal the contract and fully decentralize it.

**Core**

* IERC721
* IERC721 Metadata
* IERC721 Enumerable

**Extensions**

[<mark style="background-color:blue;">**BEP-721**</mark>](https://academy.binance.com/en/glossary/bep-721)

**Custom made**

* Capped
* Override BaseURI
* Mint in batch (up to 10 tokens per transaction)

Minting will be role-based and only one crowdsale contract at a time is allowed to act as minter. It will store logic about the allocation of resources as well as pricing and timing ones (eventually). The owner has a minter role too.

**This smart contract interacts also with another smart contract who manages the commissions going to the Rewards Pool and distributed as reflections.**&#x20;

**More info in the next page.**


---

# 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://mavatrix-doc-repository.gitbook.io/mavatrix-litepaper/reward-based-nfts-the-mvtx-collection/mvtx-contract-description.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.