GalleryFRAYActivityLeaderboardStudio
GalleryArtistsFRAYActivityLeaderboardCode modulesHow it worksMy claimsStudio

Discover, collect and make digital art that lives onchain. Built on KEEL, so every work stays viewable without depending on any one website.

Creative toolsPreserveDocumentationHow we verifyCode modulesLook up a workYour profile
OnKeel Guide
⌕/
Browse documentation
Overview

Start here

One engine. A connected creative world.Your work, your choicesThe Shell & Harness

Create

Revisions, freezes & preservationKEEL collections & mintingThe launchpad: from work to releaseThe marketplace: after the mintYour artist page & creative identityCosts, reads & interrupted uploads

System

The Hold: storing a workThe Crucible: checks & permissionsParts, modules & shared codeInline, Hybrid & direct mediaEthereum, Tezos & AnchorsKEEL on Ethereum / EVMKEEL on Tezos / TEZThe Index & discoveryThe Rites: contract map

Tools

Images, code & worldsThe SDK: KEEL from codeChain data: let the work respondMCP: working with an assistantThe editor: bring it all together

Projects

FRAY: KEEL’s auction systemOnchaininator: preserving existing work

Reference

The design language: one word, one jobKEEL’s words, explainedWhen something does not open
Overview

Start here

One engine. A connected creative world.Your work, your choicesThe Shell & Harness

Create

Revisions, freezes & preservationKEEL collections & mintingThe launchpad: from work to releaseThe marketplace: after the mintYour artist page & creative identityCosts, reads & interrupted uploads

System

The Hold: storing a workThe Crucible: checks & permissionsParts, modules & shared codeInline, Hybrid & direct mediaEthereum, Tezos & AnchorsKEEL on Ethereum / EVMKEEL on Tezos / TEZThe Index & discoveryThe Rites: contract map

Tools

Images, code & worldsThe SDK: KEEL from codeChain data: let the work respondMCP: working with an assistantThe editor: bring it all together

Projects

FRAY: KEEL’s auction systemOnchaininator: preserving existing work

Reference

The design language: one word, one jobKEEL’s words, explainedWhen something does not open

Guide/Create·3 min read

Costs, reads & interrupted uploads

Understand what is being paid for, what a read limit means, and how to resume the existing publication.

Select an underlined word to see what it means.

In this guide
Separate setup, storage, and collecting.A free read can still be too heavy.Review the actual plan and quote.Continue the existing job after an interruption.Completion includes checking the result.

“Why am I paying again for a library someone already stored?”

Understand reuse, the actual quote, and how an interrupted upload can continue.
From an idea to a releaseSYSTEM MAP
  1. 01Make

    Choose your files and the Parts they need

    →
  2. 02Preview

    See how the complete work opens

    →
  3. 03Review

    Storage, costs, contracts, and wallet

    →
  4. 04Publish

    Keep the receipts and reopen the stored work

Each step carries the same project forward.

Separate setup, storage, and collecting.

A release may need shared infrastructure, new artwork bytes, collection setup, and minting. They are different operations. A Part already published on the selected chain can be reused without charging the artwork for another copy.

A quote should identify the network, the exact plan, which costs are one-time setup, which are new publication, and which belong to the collector.

ItemPlain meaning
Shared setupDeploy or register infrastructure that later works may reuse.
New publicationStore this work’s new files and required records.
Collection or mint actionCreate/configure a DieThe artist's token contract. It records the Slabs, their owners or balances, supply, and presentation bindings.For exampleA Die can issue a series of 100 individually identified works.Full glossary entry → or issue the intended SlabThe collectible token recorded in your wallet. It identifies an owned item and points to its work.For exampleYou collect Tidal Study #7. That token is your Slab; the artwork files have their own storage records.Full glossary entry →.
Read budgetHow much work and response size a reader can handle; not itself a mint price.

A free read can still be too heavy.

Asking a chain service to read data usually does not require your wallet to pay a transaction fee. The service still has to compute and return the result, and it can impose limits.

This is why a work that is cheap to store can still be difficult to return in one large presentation. Measure the whole response, including metadata and preview.

FOR EXAMPLE

A small sketch uses a large player

Your creator file is tiny, but the complete presentation includes its runtime and preview.

OnKeel measures the whole package before you publish. If it’s too large to load in one request, choose Hybrid, which loads the pieces one at a time.

What this means for you: An upload-size figure alone does not tell you whether a marketplace can open the work.

Technical detail: presentation budgets and provider limits

The SDK’s automatic asset threshold is 1,750,000 compressed bytes; the whole tokenURI ceiling is 2,000,000 bytes. Its EVM read gas ceiling is min(60,000,000, latest block gas limit), with actual provider behavior checked separately. These figures are not Tezos limits, universal file limits, current network prices, or measured publication fees.

Review the actual plan and quote.

Optimization can change the output file, so inspect the result and keep the original. Compare exact new bytes, reused PartsReusable components included in a work, with their own identities and permissions.For exampleSeveral artworks can share the same verified drawing library.Full glossary entry →, and any required decoder or setup cost.

Quotes depend on the chosen network and current conditions. Use measured plan data and the current quote rather than turning an illustrative number in a guide into a price.

Continue the existing job after an interruption.

If an upload stops responding, it may still be running. Don’t start over: open its saved progress, see which steps finished, and continue from there.

Resume the remaining work after that reconciliation. Starting a new collection, mint, or replacement upload before checking the existing job can duplicate actions.

Technical detail: durable recovery

Retain the exact account, network, plan digest, operation sequence, cursor, transaction/batch identifiers, and server-issued recovery envelope. Confirm receipt and state before retrying an uncertain submission. A client-side exception is not proof that a chain operation failed.

Completion includes checking the result.

The job finishing its transactions is one milestone. Recover the files, compare their MarkA file's computed fingerprint, also called a digest or hash. A reader recomputes it to check the bytes.For exampleChanging the sketch's background color changes its Mark. A filename alone would not reveal that change.Full glossary entry → and sizes, and inspect the resulting SlabThe collectible token recorded in your wallet. It identifies an owned item and points to its work.For exampleYou collect Tidal Study #7. That token is your Slab; the artwork files have their own storage records.Full glossary entry →’s metadata and presentation.

Only those later checks tell you what the collector can actually retrieve and open.

KEEP EXPLORING

The launchpad: from work to release→Inline, Hybrid & direct media→KEEL on Ethereum / EVM→When something does not open→
← PreviousYour artist page & creative identityNext →The Hold: storing a work

ON THIS PAGE

Separate setup, storage, and collecting.A free read can still be too heavy.Review the actual plan and quote.Continue the existing job after an interruption.Completion includes checking the result.