# Teku — EIP-7732 (Gloas)

**Review status: candidate identified from public issue evidence; the requested pinned-source line-by-line verification could not be completed from the accessible public pages in this run.** I do not claim the issue describes the current default-branch behavior.

- Client: Consensys Teku, https://github.com/Consensys/teku
- Client pin: **not established**. The newest default-branch commit hash could not be retrieved from available public pages. The latest visible release page showed 26.10.2 at `3369f5d`, which is a release commit and is not asserted to be the default-branch tip: https://github.com/Consensys-Incorporated/teku/releases
- Consensus-spec pin: **not established**. The `master` pages were read, but their page rendering did not expose the commit hash. The references below therefore identify the branch URLs, not a falsely claimed immutable pin.
- EIP/spec version: EIP-7732 page is marked Last Call, with last-call deadline 2026-11-01. The Gloas beacon spec describes itself as work in progress and lists EIP-7732 among the included changes. The exact release/version targeting this page is not stated in the pages read; consensus-spec release `v1.7.0-beta.0` is visible in release history, but I cannot establish that as the exact commit behind `master`.
- Mainnet gate: the Teku release page says Gloas was unscheduled on Hoodi again; no source read establishes that EIP-7732 logic is active on Ethereum mainnet. The live-code withholding rule therefore was not triggered by evidence available here.

## Candidate 1 — Gloas beacon-attestation gossip handling of FULL votes

1. **Spec text.** The publicly indexed Teku issue quotes the Gloas `beacon_attestation_{subnet_id}` rules as: “`[IGNORE] when index == 1, the execution payload for block has been seen` (MAY queue, SHOULD request by-root)” and “`[REJECT] if index == 1, the execution payload for block passes validation`.” Source: https://github.com/Consensys/teku/issues/10795 (spec file cited by the issue: https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/p2p-interface.md). This quotation is from the issue’s reproduction of the rule; it is not independently line-verified against a pinned spec revision here.
2. **Teku code.** No pinned file path, line range, or source quotation can be responsibly supplied: the source-code pages/search were not accessible in this review. Issue #10795 names `AttestationUtilGloas.validatePayloadStatus` and describes its then-current behavior, but that is issue text, not a verified current-code citation. Consequently this is a lead, not a confirmed current candidate.
3. **Divergence condition described by the issue.** For a Gloas attestation with `data.index == 1`, if the beacon block is known but its execution payload has not yet been seen, or if the seen payload is invalid, the issue says Teku accepted/propagated the vote rather than applying the respective ignore/reject gossip outcome. If still present on the reviewed tip, that would be a valid block/message rejected/accepted incorrectly at gossip handling; the issue does not establish consensus-state divergence by itself.
4. **Other client.** No second client source file, pinned commit, or line range was retrieved. This comparison remains unverified. The consensus-spec rule above is the reference; no claim is made about another client’s agreement.
5. **Confidence: low.** The behavior is reported in a detailed Teku issue, but current status cannot be established without examining the current implementation and its linked fix at the pinned tip.
6. **Severity:** valid block rejected / invalid message accepted (gossip validation). The issue concerns propagation verdicts and does not, on its own, establish a consensus split.

**Known check:** **known** — Teku issue #10795, https://github.com/Consensys/teku/issues/10795, says it was closed by #10804. That establishes historical recognition; it does not establish whether the current code still contains the behavior. Queries run: `site:github.com/Consensys/teku/issues "Gloas" "payload"`, `site:github.com/Consensys/teku "Gloas" "payload"`, and direct open of issue #10795. PR details for #10804 were not retrieved, so whether the repair fully covers both conditions was not independently confirmed. Hive and execution-spec-tests tracker searches for this exact gossip behavior were not found in the pages retrieved; this is not an exhaustive negative result.

## Rules checked and found correctly implemented

No rule can be marked verified-correct without the pinned Teku source and exact line references. This section is intentionally empty rather than infer correctness from issue summaries.

## Requested scope not verified

The following requested comparisons remain unverified because source files and immutable commit identifiers were not retrievable: bid balance boundaries (zero/equal-to-balance/pending withdrawals); PTC aggregation and committee size; envelope parent hash, block hash, slot and builder-index validation; missing/late payload empty-slot fork choice; `upgrade_to_gloas` defaults; SSZ field ordering; cross-client implementation; exhaustive open/closed Teku issue and PR search; Hive dashboard; and execution-spec-tests glamsterdam-devnet tracker.

## URLs read

- https://eips.ethereum.org/EIPS/eip-7732
- https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/beacon-chain.md
- https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/fork.md
- https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/fork-choice.md
- https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/p2p-interface.md
- https://github.com/Consensys/teku
- https://github.com/Consensys-Incorporated/teku/releases
- https://github.com/Consensys/teku/issues/10795
- https://github.com/Consensys/teku/issues/10682
- https://github.com/ethereum/consensus-specs/releases
- https://github.com/ethereum/execution-specs/issues/3001
- https://hive.ethpandaops.io
- https://github.com/sigp/lighthouse
- https://github.com/sigp/lighthouse/issues/8961