Searchers

⚠️

Status Message Error Decodings

HandleId	Status Message	Description
2	QUEUED	The default state when initially creating a transaction during the initial API call. This indicates that this transaction is waiting to be picked up by a background worker.
3	PROCESSING	A background worker has started to process this transaction.
4	FUNDING	An auxiliary funding transaction is being initiated (this only applies to non-Ether transactions).
5	FUNDED	An auxiliary funding transaction was successful (this only applies to non-Ether transactions).
6	BROADCASTING	The transaction is being announced to the blockchain network nodes.
7	BROADCASTED	The transaction was successfully announced to the blockchain network nodes.
8	PENDING	The transaction is "pending" / "in the mempool", i.e. known to (some) blockchain network nodes, and awaiting inclusion/mining into a block.
9	CONFIRMING	The transaction was mined into a block, but not enough subsequent blocks have yet been mined to consider that transaction "safe" / confirmed.
10	CONFIRMED	The transaction was mined into a block and enough subsequent blocks have been mined to consider that transaction "safe" / confirmed.
11	FAILED	The transaction was mined into a block, but the execution of its smart contract code failed. Several reasons are possible, most notably "out of gas". The transaction is still included in a block because its gas is still awarded to the miner who attempted to execute it.
12	REJECTED	The transaction was mined into a block but was rejected during the execution of its smart contract code. Several reasons are possible, most notably Solidity's require() assertions not being satisfied. The transaction is still included in a block because it's gas is still awarded to the miner who attempted to execute it.
13	UN-PROCESSABLE	An unrecoverable error occurred which prevents us from getting this transaction onto the blockchain. We have given up (or the customer requested us not to retry).
14	RETRYING	A temporary/recoverable error occurred, and this transaction was re-queued as to try getting this transaction onto the blockchain at a later time. This state is more or less equivalent to QUEUED, but its name is more telling.