Recover from a rejection
A transaction that has not confirmed is still recoverable. Here is how to work out which situation you are in.
Protocol behavior Verified 2026-08-31
Describes the Atomicals protocol itself at the pinned reference revision. It does not promise that any product exposes it.
- Page ID
-
guides/recover-from-a-rejection - Normative authority
- Atomicals reference implementation
- Networks
- mainnet
- Documentation version
- 2026.08
- Audience
- everyone, holder
- Owner
- bitcoin-universe-docs
- Sources
-
- Atomicals ElectrumX
at
v1.5.2.0
- Atomicals ElectrumX
at
Это содержимое пока не доступно на вашем языке.
First, find out which situation you are in
Section titled “First, find out which situation you are in”| Situation | Recoverable |
|---|---|
| Built, not signed | Yes. Discard and rebuild |
| Signed, not broadcast | Yes. Discard and rebuild |
| Broadcast, rejected by the node | Yes. Nothing happened |
| Broadcast, in a mempool, unconfirmed | Sometimes. Replacement may be possible |
| Confirmed, Atomicals result wrong | No. The allocation is final |
| Commit broadcast, reveal never sent | Yes. Rebuild the reveal |
Rejected before broadcast
Section titled “Rejected before broadcast”Nothing happened on chain. Read the rejection reason and rebuild.
| Reason | Fix |
|---|---|
| Fee too low | Raise the fee rate |
| Dust output | Raise the output value above the relay threshold |
| Missing input information | The builder did not supply previous output data |
| Signature invalid | Wrong key, wrong flag, or a modified transaction |
| Non-standard script | Use a standard output type |
Unconfirmed in a mempool
Section titled “Unconfirmed in a mempool”If the transaction signalled replaceability, a replacement may be possible. Do not build one casually: a replacement is a different transaction with a different allocation.
- Model the replacement’s allocation before building it.
- Confirm the burn figure is zero.
- Confirm no input was pulled in that you did not intend.
- Raise the fee enough to actually replace.
If it did not signal replaceability, you wait.
Commit sent, reveal missing
Section titled “Commit sent, reveal missing”The value sits in a Taproot output that only your key material can spend. Rebuild the reveal with the same key material and the same envelope, and broadcast it. Do not build a different envelope: the commit committed to that exact script.
If the commit did not carry enough to cover the reveal fee, you may need to fund the reveal from an additional cardinal input, if your builder supports that.
Confirmed with a wrong result
Section titled “Confirmed with a wrong result”The allocation is final. Record what happened, work out which step of avoid burns was skipped, and change the procedure.
Never do this while recovering
Section titled “Never do this while recovering”- Never paste a seed phrase or private key into a recovery tool.
- Never accept help from someone who asks for one.
- Never rebroadcast a transaction you have not re-modelled.