Skip to content

GWAT — Personal Derivative Venues

One-line pitch: A GWAT is your version of a venue — a personal fork of a QING with your name on it, marked with 骨 (bone).

What this is

GWAT lets you spawn a personal derivative of an existing QING. You take a venue you like and GWAT mints you a new one — still points at the same underlying asset, still has a spot on the map, but you own it. You set its rules. You earn from its activity.

You can have one GWAT per parent QING per YUE. So if your friend also wants a derivative of the same parent, they get their own — yours and theirs are independent.

Every GWAT is marked with the bone symbol (骨) in its token symbol. That's how other players can spot them in wallets and explorers.

If you've played a web3 game before

  • Closest analogy: a fork of a project — same upstream, your own deployment.
  • Or: a franchise — same brand, your own location.
  • Or: Uniswap v3 custom pools — same pair, your own fee tier / custom params.
Dysnomia term What it maps to
Parent QING The venue you're cloning
Your GWAT Your fork of it
_qings[parent][you] Lookup: "does you already have a GWAT of parent?"
骨 (bone) The symbol prefix marking it as a derivative

What you actually do with it

  • Spawn a GWAT — call GWAT's creation function referencing a parent QING. A new QING contract is deployed, flagged as a GWAT, and you're its owner.
  • Configure it — same bouncer / cover-charge / staff controls as a normal QING, but you set them.
  • Earn from chat — when people chat in your GWAT, normal MAI payouts apply, same as with a parent QING.

Rewards / costs

  • Cost: gas to deploy. No protocol fee.
  • Reward: a token mint to you on creation, and all the normal revenue streams of a venue you own.

Requirements & gating

  • You must have a YUE — GWAT tracks "one per YUE, per parent" to prevent spam-derivatives.
  • The parent QING's asset must not be on MAP's forbidden list — ForbiddenToken reverts otherwise.
  • If you already have a GWAT of that parent, you can't create another — YourGwatAlreadyExists.

Where it connects

GWAT uses WAR as its math root (construction takes WAR's address). Each GWAT is a real QING with its GWAT flag set true. Derived venues live in GWAT's internal coordinate registry, not MAP's — so they don't clash with originals.

Quick FAQ

Q: Is a GWAT as legitimate as an original QING? A: Functionally yes — same code, same chat, same cover-charge logic. The only difference is the GWAT = true flag and the 骨 symbol prefix. Players may or may not prefer originals for social/status reasons.

Q: Can I create a GWAT of a GWAT? A: The underlying asset is what matters. You're derivatizing a venue's asset, not the venue itself. In practice check the contract rules for your case.

Q: Does my GWAT show up on the MAP? A: Not on MAP's main registry. It lives in GWAT's own _waats / _map structures. This is intentional — GWATs don't pollute the canonical world.

Q: Why can I only have one per parent? A: To prevent spam and rent-seeking — otherwise someone could mint 10,000 derivatives of a hot venue and corner its namespace. One-per-player keeps it tidy.

Q: What's "Lin" in SpawningFailure? A: An internal counter during the spawn process. If the spawn can't find a clean slot for your GWAT (rare), it reverts with the counter value for debugging.

Want the Solidity? The contract reference lives at technical/docs/domain/soeng/GWAT.md.