> For the complete documentation index, see [llms.txt](https://guide.dot.fan/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.dot.fan/painting/publish.md). # Publish {% hint style="info" %} View every Dot card published at {% endhint %} ## Publish Dot Card After you have completed your painting, it's time to publish! Publishing your card is completely free and does not cost any gas. Once you publish a Dot card, it is available for other players to discover and collect in packs for 7 days. Players can get your card randomly when they buy a pack of cards. When your card is minted, you receive the .00002 ETH Artist Reward. You can retrieve your earnings any time on the Settings page. ## cc0 License Published Dot cards are licensed as Creative Commons 0 (CC0) so that the community can create and learn together. You are welcome to download, build upon, and reuse Dot cards without restriction. ## Onchain Art Every time a Dot card is collected, it is given a digital heartbeat -- each pixel is encoded and stored permanently on the blockchain. Learn more on the [Onchain Art](/cards/onchain-art.md) page. --- # 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://guide.dot.fan/painting/publish.md?ask=&goal= ``` `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.