Block reorganisation (reorg)

A network replacing its most recent blocks with a different, longer chain, so transactions in the replaced blocks may disappear or land in another block.

#How it works in CryptoLike

Recent blocks can be replaced, which is why CryptoLike credits a payment only after the asset's number of confirmations: the deeper a block, the less likely it is to be replaced. While a transfer is below the threshold, the payment stays pending.

CryptoLike checks every new block against the chain it has already seen. When a block is replaced, transfers from the dropped blocks are marked as orphaned and the new branch is read again; a transfer that reappears in the new branch is counted anew. If a replaced block held an already confirmed transfer, CryptoLike reverses the credit and sends invoice.reverted for a payment or deposit.reverted for a static address; if that amount has already been paid out, nothing is reversed automatically and CryptoLike's team reviews the case. Stop fulfilment on reverted and wait for a new invoice.paid. A transfer dropped before the threshold was never credited, so an invoice gets no webhook for it; the full walk-through of both cases is in why "detected" is not "paid".

Reorganisations deeper than the platform handles automatically stop processing on that network until an operator checks it, so no credit is made from a branch that cannot be verified. Details: how many confirmations a payment needs.