Publishing through the studio
How a submission reaches the marketplace: the wallet confirmation, the four states, and what approving does.
The studio is for confirmed artists
A curator confirms your wallet against your artist profile before the studio can do anything for you. Until then it says so — "your wallet is not bound to an artist profile yet" — and the step is not one you can take from here: it is a confirmation, not a form.
Once your wallet is confirmed, the studio is where you manage the parameter definitions of your own collections and release new work.
What a submission goes through
A submission carries one of four states, and the studio prints the meaning of each beside it:
- Pending — waiting for a curator to review it. Nobody else can see it yet.
- In the queue — approved, and the deploy is queued on the timelock; it goes live when that executes.
- Live — approved and public, so collectors can reach it now.
- Rejected — not approved, and the curator's note below it is the reason.
Approving is deploying
Approve and reject are not a moderation queue in front of a later technical step: approving puts the sale on chain. The platform signs that deployment with the key a factory names as its admin, which is why the state between the two is its own — the deploy is queued on the timelock and becomes public when it executes.
Nothing is on chain until then. A rejection leaves the submission unsigned for and costs you nothing, which is what the queue says when you look at it.
Parameters and previews
For a drop with parameters, the studio is where the axes and their choices are defined — what values a token can carry. The values themselves are bound when a token is minted, and what a preview shows is produced from those values through the mapping the drop records.