https://github.com/conssslab/official-limit-time-event
Official limit time events, built with Walrus, preventing the team from arbitrarily changing the rules and ensuring absolute fairness for players
https://github.com/conssslab/official-limit-time-event
sui tatum walrus
Last synced: 5 days ago
JSON representation
Official limit time events, built with Walrus, preventing the team from arbitrarily changing the rules and ensuring absolute fairness for players
- Host: GitHub
- URL: https://github.com/conssslab/official-limit-time-event
- Owner: ConsssLab
- Created: 2026-05-29T23:49:13.000Z (about 1 month ago)
- Default Branch: main
- Last Pushed: 2026-06-05T16:35:20.000Z (24 days ago)
- Last Synced: 2026-06-05T18:39:41.182Z (24 days ago)
- Topics: sui, tatum, walrus
- Language: CSS
- Homepage: https://consss.wal.app
- Size: 31.1 MB
- Stars: 2
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# ConSSS Wars — Official Limited-Time Events
> This repository **is [consss.wal.app](https://consss.wal.app)** — the home for **all official
> limited-time event pages** of **ConSSS Wars: Echoes of Chainoa（鏈州英雄傳：鏈之迴響）**.
It is published as a [Walrus Site](https://docs.walrus.site/) (SuiNS name `consss`), so the
event pages are served from decentralized storage rather than a server we control.
## Why a Walrus Site (and not a normal server)
**Trustless hosting protects players.** Once an event page is published to Walrus, the game
team (ConSSS Lab) **cannot quietly change the event rules afterward**. The page — its eligibility
logic, the reward, the on-chain contract IDs it points at — is content-addressed and immutable
for the published version. Players can see exactly what they signed up for, and trust that the
rules they joined under won't be silently altered mid-event. That guarantee is the whole point
of hosting here instead of on a server where the team could swap the page at any time.
(The site object *can* be updated to point at a new version, but every update is an on-chain,
publicly visible action with a new content hash — there is no invisible "edit in place".)
## Current event
**Runs until 2026-06-30 23:59 UTC.**
During the event window, a player who:
1. plays **[play.conssswars.com](https://play.conssswars.com)** and
2. clears **Suiren's three battles** (battles 1, 2 and 3), minting the **3 clearance NFTs**
(Chronicles for battles 1, 2 and 3),
can then come to **[consss.wal.app](https://consss.wal.app)** and **claim the limited-time event
treasure chest** — minting a single **ConSSS Wars - 1st Gift** NFT on **Sui mainnet**.
Eligibility is verified **on-chain** at claim time, so possession of the three Chronicles
(earned by that wallet) is what unlocks the reward — not anything the front end says.
## Links
- Game: https://play.conssswars.com
- Site: https://conssswars.com/
- X: https://x.com/conssswars
- Discord: https://discord.com/invite/GyrfKEADaG
## Features
- **Eligibility-gated claim** — one mint per wallet, gated on-chain by ownership of the
Chronicles earned for battles 1, 2 and 3.
- **Two chests, one gift** — pick the Tatum or Walrus chest; both open the same reward and
reveal `consss_1st_gift.png`.
- **Bilingual (zh / en)** — top-right language toggle, persisted in `localStorage`.
- **Wallet Standard** — connects any Sui-compatible wallet (e.g. Slush), with auto-connect on
revisit and graceful no-wallet / cancel / out-of-gas handling.
- **Shared design system** — reuses the official conssswars.com look (Chainoa 9-slice panels and
buttons, Noto Sans TC + Source Serif 4).
- **No build step** — vanilla HTML/CSS/JS; SDK modules loaded as ESM from `esm.sh`.
This repository contains only the static front end. The Move contract (`event_01_gift`) lives in
the separate `contracts` repo.
## How it works
1. The visitor connects a Sui wallet.
2. The page queries the wallet's owned `Chronicle` objects and builds a 1 / 2 / 3 checklist,
keeping only Chronicles the wallet **earned itself** (`player == caller`) for each of battles
1, 2 and 3. It also calls `has_claimed` to detect a prior mint.
3. The claim chests are enabled only when all three Chronicles are present and the wallet has not
already claimed.
4. Opening a chest submits `event_01_gift::mint`, passing the three Chronicle objects. The
contract re-verifies eligibility and one-mint-per-wallet on-chain, assigns a sequential
edition, and transfers the Gift to the caller.
Eligibility is enforced by the contract; the front-end checks are only there to guide the user.
## On-chain (Sui mainnet)
| Item | Value |
|---|---|
| `event_01_gift` package | `0xd1ed457cb4f1bb209c09a094f772472db15c115a29eb5995b7cb2a2313227896` |
| `MintCounter` (shared) | `0x7c15f5391cd1baf53bc3280ac3f75331c5abe027a370eedb39ac9d7f301890a9` |
| `chronicle` package (eligibility lookup) | `0x5760b2685d41bd45e2991dedc242e866b1aca9ff3c3a5e193445751c2b8dfe4b` |
| Mint call | `event_01_gift::mint(counter, c1, c2, c3, clock)` |
| NFT name | `ConSSS Wars - 1st Gift` |
`c1 / c2 / c3` are the caller's own Chronicle objects for battles 1, 2 and 3; `clock` is the
system clock at `0x6`. Network IDs are configured at the top of `app.js` (`NETWORK = "mainnet"`).
## Project layout
```
index.html event page markup (Chainoa-themed)
styles.css gold / navy painterly styling, 9-slice panels & buttons
app.js wallet connect + on-chain eligibility check + mint (ESM)
ws-resources.json Walrus Sites routing (SPA fallback to /index.html)
build-dist.sh assembles the slim dist/ bundle for deployment
consss_1st_gift.png NFT reveal image shown on a successful claim
chests/Tatum.png chest / powered-by logo
chests/Walrus.png chest / powered-by logo
assets/ icon + shared Chainoa UI art (panels, buttons)
```
## Local development
No build or install step. Serve the repo root with any static server:
```bash
python3 -m http.server 8099 # then open http://localhost:8099
```
To complete a claim you need a Sui-compatible wallet on **mainnet** with a little gas, plus the
Chronicles earned for battles 1, 2 and 3.
## Deploy (Walrus Sites → consss.wal.app)
```bash
./build-dist.sh # → dist/
site-builder --context mainnet update --epochs ./dist
```
`` is the existing `consss.wal.app` site object. `build-dist.sh` copies only the
optimized web assets (HTML/CSS/JS, the reveal image, chest logos, and the shared UI art) into
`dist/`. Updating requires mainnet SUI (gas) and WAL (storage) on the deployer address.
Each `update` republishes the page as a new immutable Walrus version, so any change to the event
rules is an explicit, on-chain, publicly visible action — never a silent in-place edit.