CW-SVG
Documentation
What are cwSVGs?
cwSVGs are on-chain SVGs with parameterized variables. Rather than storing a static image, the contract holds an SVG template with variable slots — colors, shapes, patterns, positions — that are generated on-chain during minting.
Each token receives a unique combination of these variables, derived from on-chain entropy at the time of mint. The result: every token renders a one-of-a-kind SVG, fully client-side, with no off-chain metadata or IPFS dependency.
Because the SVG template and all parameters live on-chain, the art is permanent and self-verifying. Any client can reconstruct the exact visual from the contract state alone.
Payment via Shitstraps
Collections may price mints in a specific denom (e.g. uterp). If your wallet holds a different asset, the mint flow can use a shitstrap — an automated swap path that converts your available tokens into the required denom at mint time.
When you connect your wallet, the payment section shows all available options:
- → Direct payment if you already hold the required denom
- → Shitstrap swap paths from other assets you hold
- → Insufficient balance warnings if no path covers the cost
The swap is executed as part of the mint transaction — you don't need to manually swap beforehand. Select your preferred payment method and confirm.
IBC-aware shitstraps: you can source slop from counterparty chains via IBC transfer memos (ADR-8 style callbacks) so mints complete without pre-swapping on Terp. Cap participation to remaining strap capacity (to_shit) to avoid lockout from over-sending past the cutoff.
Minting Process
- 1. Browse collections and select one
- 2. Set your quantity and review the total cost
- 3. Choose a payment method (direct or shitstrap)
- 4. Confirm the transaction preview and sign
- 5. Your unique SVG is generated on-chain — refresh to see it
Funding is capped to remaining capacity so you cannot overshoot the cutoff and lock funds. IBC memos can source slop from counterparty chains before mint.
Loading tokens...