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

# Contracts & Size Constraints

## Why there are two renderers

Ethereum-compatible networks enforce a deployed contract-code size limit commonly associated with EIP-170. Combining every Common trait and every bespoke 1/1 animation in one renderer exceeded the practical limit.

GOKIBURI therefore splits rendering responsibility:

* **Common renderer:** reusable geometry, traits, palettes, and motion systems.
* **Rare renderer:** token-specific 1/1 artwork and effects.

The ERC-721 collection routes by a fixed list of Rare token IDs.

## Size is a design constraint

Every added pixel path, palette value, animation rule, and metadata string consumes bytecode. Visual ideas are evaluated against both artistic impact and deployed size.

Typical optimization strategies include:

* reusing shared SVG fragments;
* generating repeated structures procedurally;
* keeping Common and Rare concerns separate;
* using short deterministic trait tables;
* avoiding redundant strings and transforms;
* validating with `forge build --sizes` before deployment.

## Mint controls

The collection contract currently supports:

* owner-controlled public mint opening;
* owner-controlled mint price;
* owner minting of a quantity, range, or specific token ID;
* withdrawal to an owner-selected payable address.

The per-wallet mint allowance has not been decided. Final limits will be announced with the official mint details. The deployed contract state—not this documentation—is authoritative for price, availability, supply, and renderer addresses.


---

# 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://gokiburi.gitbook.io/gokiburi-docs/contracts-and-size.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.