Burn to queue

Hold 1,000,000 $QCRACK (0.1% of supply) to queue your own named attack. You pick the rung, the backend and an optional handle (up to 24 characters, filtered).

Prove the wallet first

A quote reserves QPU seconds that nobody else can use for 120 s, so asking for one needs a signed message from the wallet (signMessage, no transaction, no fee) with a single-use server nonce, the rung, the backend and the handle. One open quote per wallet; once its transaction has been built, it cannot be replaced until it expires, and a burn against a replaced quote is refused.

A burn is final, so we reserve first

A quote is issued only if the attack's QPU seconds fit the current budget, the named cap (120 s per 28 days) and the day cap (6 per day). Otherwise you see "named queue full until " and nothing is burned. A quote holds its seconds for 120 s.

The transaction

The server builds an unsigned v0 transaction with exactly: a compute budget instruction, one Token-2022/SPL burnChecked of $QCRACK from your token account, and a memo qcrack:q:<quote id>. The page decodes every instruction in plain words and simulates it before your wallet asks you anything. Your wallet signs and sends it. We never sign or send for you.

Verification

After you send it, the server reads the transaction at finalized commitment and checks: it succeeded; exactly one burn of $QCRACK; from a token account owned by the quoting wallet; amount at least the quote; the memo matches; it landed before the quote expired; the signature was never used before. Then the attack joins the named queue (first in, first out) with your handle and the burn tx on its receipt. A named attack can of course end NO EDGE.