Disclaimers

Before you treat anything here as gospel, read this page.

This is not financial advice

None of the tokens discussed here (LAU, YUE, H2O, VITUS, MAI, DYSNOMIA, QING, GWAT, CROWS, …) are recommended investments. They are gameplay mechanics. Nothing on this site is a prediction of price, a projection of yield, or a suggestion that you should buy, sell, or hold any asset.

Two classes of claim

Pages here contain two kinds of statement. Treat them differently.

Hash-verified facts

Any numeric constant, cap, TTL, divisor, prime, or formula we cite has a link next to it pointing into ../../technical/docs/.... The technical docs each carry a keccak256 hash of the Solidity source they describe, so those facts are hash-verified against a specific point-in-time snapshot of the flattened source at github.com/busytoby/atropa_pulsechain.

Example: the "25 CROWS" VIP threshold, the "1 day" cover-charge duration, "10 days" ENCRYPT TTL, "90 meridians", "776 / 777 rate floor", "MotzkinPrime = 476,733,977,057,179" — these are all in this class.

Inferred strategies

Anything tactical — "hold YUE instead of wallet to max Yuan", "rotate QINGs to amortize chat-MAI cap", "don't re-Code immediately after" — is reasoned from the mechanism, not quoted from the doc. These are marked (inferred) where it matters. Treat them as hypotheses you're about to test. If a claim here makes a pin-point prediction that turns out wrong in play, the mechanism is probably what we miscounted, not the contract.

Contracts evolve

The Dysnomia contracts have a V1 and a V2 for DYSNOMIA / DYSNOMIA_V2, and the inheritance tree evolves. Cross-check a strategy against the current hash in the technical doc before you bet meaningful gas on it. The technical/scripts/verify_hashes.py script is the canonical check.

Soft edges

Some numbers are softer than they look.

• "BouncerDivisor" — settable by any bouncer per-QING (QING). Any strategy that cites a specific divisor is QING-specific; don't generalize.
• "CoverCharge" — same: bouncer-mutable per QING.
• "Yeo" — output of META.Beat(), which reads RING.Eta(). Yeo depends on your own Pang/RING state. Two players standing next to each other can have different legal Code ranges.

Game state > documentation

If you see something in-game behave differently from what a strategy page says, trust the game. Open an issue and flag the discrepancy.

Tone

This site is opinionated. It tells you what we think the edge is. You are not obligated to agree. The contract source is in the technical docs — read it and decide for yourself.