GuideStart here3 min read
One engine. A connected creative world.
Art, code, storage, ownership, and discovery belong in the same story. KEEL gives them a shared foundation.
Select an underlined word to see what it means.
In this guide
We kept seeing the same walls.
An artist makes something wonderful. The files live in one place. The mint happens somewhere else. A collector sees a thumbnail. A builder starts another renderer because the last one cannot use their tools. Every new project stitches the same pieces together again.
KEEL starts underneath those gaps. It is an engine for connecting the work, the tools that open it, the rules around it, and the people who care about it. The aim is a web you can build on together.
Give each piece a job. Let them work together.
The HoldKEEL's native onchain storage for the file bytes and the instructions for joining them back together.For exampleYour sketch and its shared drawing library are stored as separate objects in the Hold.Full glossary entry → keeps files. The IndexThe sealed inventory and presentation records that identify the work's pieces and their Marks. This protocol layer is different from the site's search indexer.For exampleThe inventory says this revision uses this sketch and this exact library version.Full glossary entry → names the pieces. The CrucibleThe verification layer. Its browser checks compare recovered files with the fingerprints and sizes the work declared.For exampleA changed script fails its check before the default shell opens it.Full glossary entry → checks what arrived. The HarnessThe composition that runs the work: its selected resources, runtime context, and isolated environment.For exampleThe Harness connects your sketch to its drawing library and runs it inside the Cage.Full glossary entry → opens the work. 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 → can make it collectible. Shared 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 → let your next idea use what already exists.
These are connected jobs. A new format should be able to join the system without rebuilding storage, ownership, or discovery from scratch.
Your idea comes first.
Artists need room to experiment. Collectors need a way to inspect what they own. Builders need tools they can reuse. And sometimes you just want to make something strange and see who joins in.
You can store a work without selling it. You can choose your own collection, prepare a drop, or explore an auction. KEEL’s shared foundation leaves those creative decisions with you.
- Store a work without launching an NFT.
- Use a dedicated collection, shared editions, or a compatible existing contract.
- Reuse a renderer or publish your own declared module.
- Plan for future preservation while keeping earlier versions identifiable.
We have laid the foundation. Bring your part.
This guide follows Tidal Study, a fictional artwork used only to explain the KEEL engine. Try the examples. Change the release shape. Follow a file. Inspect the contract map.
We finish in the editor, where files, agents, wallets, contract controls, and saved decisions meet. You can also use the same engine through the SDK and MCP in your own tools.
What are you making?
Tidal Study is a drawing made by a small script. You keep the editable source. The sketch also needs a particular version of its drawing library.
A project with your files and the Parts it needs.Technical detail: artifact, token, and content identity
An artifact has a logical identity and exact revisions. HoldKEEL's native onchain storage for the file bytes and the instructions for joining them back together.For exampleYour sketch and its shared drawing library are stored as separate objects in the Hold.Full glossary entry → objects identify stored content. A 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 → is identified by its network, collection contract, and token ID. These records can refer to each other, but they are not interchangeable identifiers.