RELICS Launchpad · documentation
How this works.
Everything below is served by this deployment, or by the public repository that produces the file it imports. Nothing here is a roadmap or a promise — where a surface reads chain state, it says so, and where a contract is not deployed, it is reported as not deployed.
Start here
A creator launchpad for market-responsive generative art powered by Uniswap v4.
- Launchpad overview
What the platform does and the three chains it targets.
- Create a collection
Three ways into the studio: start from a template, import a .relics project, or continue a saved draft.
- Discover projects
Collections already launched, read live from each chain.
Making a .relics bundle
A .relics bundle is one deterministic ZIP carrying a project's generator, its trait schema, its market mappings and its collection metadata, with hashes over its own contents. It is what the import path on /create reads. You build one locally with the creator kit — a public, dependency-free CLI that signs nothing, broadcasts nothing and contacts no network. Authoring, previewing, validating and exporting all happen on your own machine, and this app first sees the project when you upload the file.
- Scaffold a project from a starter template, then write the generator.
- Render it — any seed, any market state — until the rules are the ones you meant.
- Sweep a wide seed range for failures, blanks and duplicate trait sets.
- Validate. The kit runs the same schema this importer runs, so a clean local run is not a guess about what happens here.
- Export one .relics file, and import it at /create. The importer re-derives every hash from your bytes.
- The creator kit repository (opens on GitHub)
The CLI, five starter templates, the bundle format and the schema — public, MIT, and the source of truth for all of it.
- Getting started, step by step (opens on GitHub)
The commands, in order, with what each one writes. Run them and compare — do not take a number on trust.
- Import a .relics project
Already have a bundle? It is inspected and validated before anything is created, and never executed in this page.
How a launch works
A launch is one atomic Uniswap v4 transaction. The app never holds a key and never broadcasts: every write is a transaction the connected wallet signs itself, and every platform address is reported as not-yet-deployed until it actually is.
- Revenue dashboard
Per-project revenue read from chain.
- Fee detail
How a project's fee split is reported.
The RELICS artwork
The launchpad grew out of RELICS itself — a fully on-chain generative collection whose condition is written by the real market history of a Uniswap v4 pool. Its thesis is published in full.
- RELICS: The Market as Medium
The canonical artistic whitepaper.
- Technical reference
Contracts, ABI surface, and integrator notes.
- How RELICS works
Acquisition and awakening in plain language.
Security
Responsible disclosure is wired to a published contact and an RFC 9116 record served by this app.
- Security policy
Scope, expectations, and how to report.
- security.txt
The machine-readable disclosure record.