GuideCreate3 min read
The launchpad: from work to release
Your launchpad connects the artwork, your collection, mint rules, and collector page. Follow one release from draft to read-back.
Select an underlined word to see what it means.
In this guide
One token. One original.
One collector holds the one token for this work. A direct mint, campaign, or suitable auction can determine how it reaches them.
Early supporters and the public can use ordered stages with a shared allocation.
1. Say what you want to make.
Imagine Tidal Study as a one-of-one, 100 distinct works, or an edition that friends can collect together. Choose that shape first. Then choose your collection and the way people receive it.
The launchpad brings those decisions into a release plan: artwork, storage, presentation, supply, price, access, timing, and destination. A practice release on a test network has separate tokens and records.
2. Build and open a local preview.
Import the original files and identify the exact 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 → they use. Build the real composition and try it. If an image is optimized or a script is changed, review the new version while keeping the original.
The SDK is the code toolkit. MCP exposes tools to an assistant. OnKeel Studio and the desktop editor provide interfaces. They help prepare the same work.
3. Read the plan before approving.
The plan should show the new files, 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 →, chosen storage, presentation, destination contracts, and costs. It should also explain any permission your account needs.
You should be able to answer: “What am I adding, what am I reusing, and what will this wallet action change?”
4. Publish with a recovery record.
The wallet review binds the action to a particular network, account, destination, and amount. A large upload can take several transactions.
KEEL’s publication workflow records progress so an interrupted session can reconcile completed work and continue. Keep that record; a timeout is a reason to inspect the existing job before starting another.
5. Check the published result.
A transaction receipt says an operation was included on the chain. Read-back means asking the chain for the result and checking the actual bytes and bindings.
Open the resulting presentation, inspect its checks, and confirm that discovery points to the intended release. This lets you see the work as a collector will receive it.
Three different costs
Publishing bytes, deploying or configuring shared infrastructure, and reading a complete token presentation are different costs. A cheap upload can still produce an expensive contract read. A local estimate is not a live wallet quote.
The mint is one part of the launch.
Minting creates the collectible in a wallet. Before that, the work needs files that open, a collection that can issue the token, and a sale or claim with permission to use its allocation.
You might reserve ten tokens for collaborators, then offer ninety through a staged drop. The launch needs to account for both. A beautiful mint page cannot increase the contract’s remaining supply.
Give the release somewhere to belong.
A collector page explains the work and how to receive it. Your artist page helps people find the wider practice behind it. A marketplace listing is a later sale of an existing token.
Connect those pages to the same collection and work records so people can follow the story in either direction. Public access depends on OnKeel Studio and whether the release is available.