How does Blockferry handle reorganizations?

Temporary forks (uncle blocks or slot dropouts) happen frequently across both EVM and Solana networks. Processing events immediately from unconfirmed block headers will corrupt database status records.

EVM Reorg Handling

For networks like Ethereum, Base, Arbitrum, and Polygon, Blockferry buffers event logs.

• **Depth Filters:** Workflows run only after a block reaches your configured safety depth (e.g. 1 block depth for low-value payments, 12 blocks for finality).
• **Automatic Discards:** If a block reorganization occurs, our indexes automatically identify the split fork and discard any events originating from the orphaned branch.

Solana Commitment Matching

Solana uses three commitment depths. Blockferry forwards events matching your choice:

1. Processed: Delivered under 400ms (fastest, slight reorg risk).

2. Confirmed: Voted on by 66%+ of active validators.

3. Finalized: 31+ slots confirmed (absolute finality).