Pull the leash yourself.

Choose how many holders leave and what the dev does. The same engine that decides real coins replays 7 days of a simulated coin and shows each verdict.

—

    Simulated coin · decided by lib/leash.mjs, the same file the server runs

    The rules, in order.

    1. At launch, the dev reserves part of the dev buy.

      0% to 100% of it. At 0% there is no leash, and the coin page says so. Otherwise it is cut in 8 slices weighted 1 to 8, and the dev pre-signs one burn per slice with a durable nonce, in their own wallet.

    2. Eight checks: 30 min, 1 h, 2 h, 4 h, 8 h, 24 h, 3 days, 7 days.

      Each check looks at the cohort: wallets holding at least 0.01% of supply at the previous check (for the first one, at creation plus 3 blocks, snipers included).

    3. A wallet stays if it still holds at least half of its balance.

      Retention is weighted by balance, each wallet capped at 0.5% of supply. The dev, pools and program accounts are never holders.

    4. 70% or more stayed: released. Under 70%: burned.

      A released slice's burn is dropped and the slice joins the dev's free bag. A burned slice's pre-signed transaction is sent, and the log links to it.

    5. The dev rule.

      Selling into the reserved bag at any time, or more than 25% of the free bag before the 24 h check, condemns every slice left. Slices the bag still covers burn; the rest show as void, in red.

    6. Same history, same state.

      The engine is a pure function of the trades. Anyone can replay a coin and get the same verdicts.