Collections, mint, members
Launch
List a Doginals collection, mint LAUNCHPAD_MINT inscriptions through the DogeSoft inscriber, gate members on holders.
launch.dogesoft.io is the DogeSoft collection launchpad — list a Doginals collection, mint through the shared inscriber, show a live X / Y minted counter, and gate a members area on holders of that collection.
It is not a generic “any wallet, any tagging scheme” mint site. Mints are
LAUNCHPAD_MINT inscriptions as defined on the
inscription standard. The wallet provider is
window.dogesoft. Confirmation is the
Explorer API.
Why a catalog exists
Dogecoin has no on-chain collection object — the chain only sees individual inscriptions. Launch's
Postgres tables (collections / collection_items)
are the directory and the counter. Once a mint confirms, membership can be checked from the indexer
alone; the database is a cache, not a second ledger.
Mint path
- User connects with
window.dogesoft.connect(). POST /api/collections/:slug/claimreserves the next index (about 10 minutes).- If the collection is priced, the wallet sends DOGE to the creator with protocol
dogesoft-launch-mint(mobile allow-list, same idea as shop checkout). - Launch verifies that payment on Explorer, then calls the inscriber
(
project: "launchpad"). - A worker polls the inscriber job, records
mint_txid/inscription_id, and bumps the counter.
There is no window.dogesoft.inscribe(). If another README told you
to call that, ignore it — it's a guess from outside the stack. Sign with the provider; inscribe with
the inscriber.
Members
GET /api/collections/:slug/membership?address= returns
{ member } from minted rows for that address plus indexer UTXOs whose
collection_id / action match the slug. Use it to lock a page, a Discord
role bot, or a download. The drop-in helper is
DogeSoftLaunch.requireMember(slug) —
builder kit.
API
All routes are relative to https://launch.dogesoft.io/api.
| Endpoint | Auth | Job |
|---|---|---|
GET /collections | — | Directory |
GET /collections/:slug | — | Detail + example mint JSON |
POST /collections | Bearer | List a collection |
POST /collections/:slug/claim | Bearer | Reserve next index |
POST /collections/:slug/mint | Bearer | Attach payment; queue inscription |
GET /collections/:slug/membership | — | Holders gate |
Bearer tokens come from POST /api/session after connect — same pattern
as shop.dogesoft.io.