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 fund it from UTXOs 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.

Mint preparations expire, and miner fees do not come back

A fee estimate depends on the exact transaction and on the mempool at that moment, so an unsigned mint preparation expires and may be refreshed before your single wallet signature. The review screen shows every allowed output and where change goes. Miner fees already broadcast cannot be refunded by anyone. Later automatic-reveal costs are included in the mint price and never create another wallet prompt.

The one wallet approval starts a multi-stage inscription

Ord inscriptions use commit and reveal transactions internally, but you approve only the reviewed mint payment once. The canonical inscription can confirm while its future delegate target remains absent. After activation finality, the protected worker signs and broadcasts that fixed target automatically. Fee changes, dropped transactions, node disagreement, and indexer lag can stretch either stage out; 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. BIP-110 status is never inferred from a calendar date. 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

Your private mint dashboard is the first and best diagnostic. It shows every stage separately, so “stuck in mempool” and “never broadcast” are never confused with each other. If you do escalate, the private mint ID and a public transaction ID are enough. Never send the order token, PSBT, wallet secret, or vault material. Nothing else should ever be shared, and nobody legitimate will ask for it.