Bitcoin does not
have an undo button.

What you never type into a website

Never enter a seed phrase, a private key, a backup word, or a wallet export file into any website, including this one. Send the mint to an Ordinals-safe destination, and pay from coins you have checked for inscriptions, runes, rare sats, and other indexed assets. A wallet that does not understand Ordinals can spend an inscription as change without warning you.

Orders expire, and miner fees do not come back

The amount you are quoted depends on the fee rate chosen when the order is created, so an unpaid order expires and may be replaced with a fresh quote. Miner fees already broadcast cannot be refunded by anyone. Send less than the amount shown and nothing is minted; the payment is returned to your refund address. Send more and the difference comes back as change in the same transaction. A payment so small that returning it would cost more in miner fees than it is worth cannot be refunded at all, which is why the checkout names that floor and asks you not to send a test amount.

Send the exact amount, from a wallet you control

One address and one figure. If the fee market rises between the quote and your payment confirming, the inscription is still broadcast at the rate you funded and simply waits; nothing is taken from your artwork, your change or the price to raise a fee. The moment your payment confirms, the inscription is built and broadcast to the address you gave. You do not sign anything else and you are not charged again. Fee changes, dropped transactions, node disagreement, and indexer lag can affect delivery checks; safe operations are retried and every transition is audited.

One confirmation is not finality

Mempool acceptance is not a confirmation, and a first confirmation is not permanent finality. A reorganisation can temporarily reverse a confirmation and the ownership that came with it. Token assignment follows the configured confirmation threshold, and a mint can return to a reconciling state after a reorg. The dashboard says so in words when it happens, and it tells you not to act on the previous result.

Relay policy and consensus can change

Node relay policy, miner behaviour, consensus deployments, wallet support, explorer rendering, and indexer behaviour all change over time. Minting stops when compatibility cannot be proved against the configured infrastructure.

Someone will contact you pretending to help

Minting publishes a Bitcoin address on a public ledger, and unsolicited contact follows. The patterns barely vary:

• A “support agent” who messages you first, right after a failed or slow transaction.
• A lookalike domain one character away from an official one, arriving as a link rather than something you typed.
• A “wallet sync”, “validation”, “migration” or “claim” page that wants your recovery phrase.
• A surprise airdrop, refund, or compensation that needs you to sign something you were never shown.

KNOT HEADS will never contact you first, never ask for a seed phrase or private key, and never need a signed PSBT emailed or messaged to a person. There is no official KNOT HEADS chat, group or social account either, so there is no real one for an impersonator to hide among: treat every approach as fake. If you are unsure, close the message and come back to the site by typing the address yourself.

What to send when you need help

The mint screen is the first and best diagnostic. It keeps every fact separate, so “stuck in mempool” and “never sent” are never confused with each other. If you do escalate, the private order ID and a public transaction ID are enough. Never send the order token, a wallet secret, or anything else. Nobody legitimate will ask for it.