Ping
Launch

How it works

Every rule, in the order it applies. The same rules run in the code that sends the burns, so the page and the chain never disagree. Watch a simulated coin live its 30 days in 2 minutes.

1. One account, locked at launch

When the dev launches in the studio, they write the @handle of one public X account. It is stored on the coin page and can never change. The account is not involved: every coin page says Not affiliated with @account and links to its posts without copying them. If the dev picks their own account, the page says the dev's own account.

2. Twelve slices, pre-signed

The dev reserves part of their dev buy for the slices: at least 25%, 50% by default. That part is cut into 12 slices by weight:

SlicesWeightShare of the reserved part
1 to 41 each4.17% each
5 to 82 each8.33% each
9 to 123 each12.5% each

Each slice is a burn transaction that the dev signs in their own wallet before the launch. It uses a durable nonce, so it stays valid for weeks. Ping keeps the signed burn and sends it when its time comes; it can never change it, and it holds no key.

3. A new post burns the next slice

Anyone pastes the link of a post on the coin page. Ping checks it through X's free public preview, with no paid API and no key:

  • the author is the locked account (two public previews must agree);
  • it is an original post: replies and reposts are refused; a quote counts;
  • it was posted after the coin was created (the date is read from the post's ID);
  • it was never used before.

A post pasted late never rewrites the past: it counts from the moment it was proven.

4. The brake and the floor

  • Brake: at most one slice every 10 minutes.
  • First hour: at most 4 slices.
  • Extra posts wait in a public queue and burn in order.
  • Floor: if nothing has burned 30 minutes after the launch, the first slice burns anyway.

5. Nothing stays behind

  • The dev sells the reserved part: every remaining slice is due at once. The slices still covered by the dev's bag burn; the others are marked cancelled, in red, with the reason. The sale stays on the coin page with its time.
  • Day 30 after the launch: every slice still armed burns.

6. What the coin page shows

The dev bag, live, in % of supply: what the dev bought, what is still armed for burns, what is free, what burned, and every dev sale with its time. The next event with a countdown. What leaves with a sale now: the next slice and everything still armed.

7. The launch

A full launch on Stonks (Raydium LaunchLab), in one transaction signed by the dev: creation and dev buy together. No treasury, no vault, no site wallet, no fee. Trading costs 1% StonkFun and 0.25% Raydium per trade, 0% creator. The image is 512 × 512 under 100 KB, and the coin's public file is read back before anything is signed.

8. Same history, same state

The state of a coin depends only on its creation time, its proven posts and the dev's sale. Anyone who replays that history gets the same burns at the same minutes. The engine is public: lib/ping.mjs.

A burn lowers the supply. It does not set a price and promises nothing. Nothing on Ping is financial advice.