Devnet Bot af2fcac444 fix(focil): align should_extend_payload with spec for gloas/heze ...

The previous implementation unconditionally checked
is_payload_inclusion_list_satisfied at the top of should_extend_payload,
returning false when the root was not in the map. Since the map was only
populated for heze slots (FOCIL), this caused should_extend_payload to
always return false for gloas slots — making the tiebreaker favor Empty
over Full for every single slot.

Per spec:
- Gloas: should_extend_payload checks is_payload_verified (envelope
  received) then timeliness/proposer conditions. No IL check.
- Heze: adds is_payload_inclusion_list_satisfied as an additional gate.

Fix: check payload_received first (matching is_payload_verified), then
only gate on IL satisfaction if the root IS present in the map (heze
slots where it gets recorded). For gloas slots where no IL exists, the
check is skipped entirely.

2026-05-18 22:14:33 +00:00

..

src

fix(focil): align should_extend_payload with spec for gloas/heze

2026-05-18 22:14:33 +00:00

.gitignore

…

Cargo.toml

resolve merge conflicts

2026-04-30 01:51:26 +02:00