Hydra adds a guard against deposits that could wedge incremental commits

What happened

Hydra merged PR #2807, adding a check that rejects a deposit when the transaction claiming its increment would breach layer-1 ledger limits. The source identifies maxValSize, stated as 5,000 bytes on mainnet, and maxTxSize as the relevant limits.

The prior path could allow a deposit to land on-chain and enter a signed snapshot even though the later increment transaction could not fit. In that case, the increment could fail forever, wedging further incremental commits and locking funds until deadline recovery.

Why it matters

For Hydra head builders, operators, and users committing funds incrementally, the change removes a documented self-wedging path. The supplied record gives deposits containing tokens under many distinct policy IDs as an example of how a value could become too large for the increment transaction.

The change also alters deposit-acceptance behavior. Builders and operators may want to test incremental-commit flows involving deposits across many policy IDs against the new rejection path.

What to watch next

The most useful next receipt would be confirmation that this merged change appears in a tagged Hydra release or is deployed for the relevant environment. The record supports neither point yet.