
A jam is measured in the source chain's own confirmations, never in time. The required depth per chain is fixed at deploy. The pending count and the last settlement are live from the machine's records.
| CHAIN | ASSET | DEPTH REQUIRED | PENDING INTENTS | LAST SETTLE |
|---|---|---|---|---|
| bitcoin | BTC | 6 blocks | ||
| zcash | ZEC | 10 blocks | ||
| monero | XMR | 10 blocks | ||
| ethereum | ETH | 32 slots | ||
| solana | SOL | 32 slots | ||
| near | NEAR | 1 block |
A timer would make the machine's behaviour depend on the clock of whoever runs it. A confirmation depth makes it depend only on the chain the asset came from. Ten Monero blocks is the same condition on every machine on earth; ten minutes is not.
Depths are chosen as the point past which a reorg on that chain is not a practical concern. They are conservative on purpose. A jam is rare and it is always the source chain's fault, never the machine's.