Question: timeline for the first economic pool (cLUNC / UST1)? #513

New issue

Closed

opened 2026-08-10 15:25:57 +00:00 by leonardocolucci · 5 comments

leonardocolucci commented

2026-08-10 15:25:57 +00:00

(Migrated from gitlab.com)

Question (no ask, just planning)

With the wrap-mapper live on mainnet (cLUNC for uluna, cUSTC for uusd — we've tested both wrap directions, see #512 for unwrap findings), the natural next step for the venue is its first economic pool.

Is a cLUNC or UST1 pair planned on the DEX, and if so on roughly what timeline? Also curious whether the first listing is intended to come from the team or whether you'd rather see a community member create the pair via the factory.

Context for asking: we run market-making and arbitrage tooling against the DEX (the bots that generated most of the soft-launch volume) and want inventory and quoting parameters positioned correctly on day one rather than scrambling after the fact. A rough "weeks vs months" answer is plenty.

## Question (no ask, just planning) With the wrap-mapper live on mainnet (cLUNC for `uluna`, cUSTC for `uusd` — we've tested both wrap directions, see #512 for unwrap findings), the natural next step for the venue is its first economic pool. Is a **cLUNC or UST1 pair** planned on the DEX, and if so on roughly what timeline? Also curious whether the first listing is intended to come from the team or whether you'd rather see a community member create the pair via the factory. Context for asking: we run market-making and arbitrage tooling against the DEX (the bots that generated most of the soft-launch volume) and want inventory and quoting parameters positioned correctly on day one rather than scrambling after the fact. A rough "weeks vs months" answer is plenty.

PlasticDigits commented

2026-08-11 00:28:12 +00:00

(Migrated from gitlab.com)

Currently anyone can add lp, however I strongly suggest waiting for the cl8y-ecosystem-clickwrap coming online in the next few days as it provides deep protections to community members and devs. Also, please feel free to open issues on there to help improve the contract to make sure its effective for protecting our community.

leonardocolucci commented

2026-08-11 09:50:52 +00:00

(Migrated from gitlab.com)

mentioned in issue #514

leonardocolucci commented

2026-08-11 09:57:45 +00:00

(Migrated from gitlab.com)

Perfect — that answers it, and count me in: I'll seed the cLUNC pool once the click-wrap is live and your UST1 pools are up.

Two practical points:

Pairing: I'd propose cLUNC/UST1, matching your hub-and-spoke (UST1/cUSTC, UST1/USTR) — that gives the router clean multi-hop paths (cLUNC → UST1 → anything) from day one. If you'd rather see cLUNC/cUSTC first, say so.
Sequencing: I'll seed after your UST1 pools are live, so the cLUNC pool opens at an externally consistent price. Any guidance on intended UST1 launch pricing helps me set the opening ratio correctly.

Per my note on #514, the pair will be continuously quoted from block one — sizing and service terms I'm happy to agree with you directly.

What's the rough ETA on the click-wrap?

Perfect — that answers it, and count me in: **I'll seed the cLUNC pool once the click-wrap is live and your UST1 pools are up.** Two practical points: 1. **Pairing:** I'd propose **cLUNC/UST1**, matching your hub-and-spoke (UST1/cUSTC, UST1/USTR) — that gives the router clean multi-hop paths (cLUNC → UST1 → anything) from day one. If you'd rather see cLUNC/cUSTC first, say so. 2. **Sequencing:** I'll seed after your UST1 pools are live, so the cLUNC pool opens at an externally consistent price. Any guidance on intended UST1 launch pricing helps me set the opening ratio correctly. Per my note on #514, the pair will be continuously quoted from block one — sizing and service terms I'm happy to agree with you directly. What's the rough ETA on the click-wrap?

PlasticDigits commented

2026-08-15 09:34:08 +00:00

(Migrated from gitlab.com)

Click wrap is currently live, however please avoid pool creation until #518 is resolved